Leadership meeting decisions
Your recorder posts the transcript when the meeting ends. Claude separates what was decided from what was only discussed, lists every action item with an owner and a date, and calls out open questions. You correct anything it got wrong at the approval gate, then the summary goes to Slack and the action items to your task tool.
- Extract decisions Claude API · Sonnet 5
- Check the record You
- Post to Slack Shell
- Send action items Shell
What each step does
Extract decisions
Claude API · Sonnet 5Separates decisions from discussion and lists action items with owners and dates.
Check the record
YouShows you the record. Reject with corrections and it is redone.
Post to Slack
ShellPosts the record to the leadership channel.
Send action items
ShellSends the record to your task tool, if you set a webhook.
From copy to first run
- Copy the pipeline JSON with the button above.
- In Jimothy, open Pipelines → New pipeline, paste it under “Or import a pipeline JSON” and click Import.
- Fill in the variables below under Pipeline settings → Variables.
- Triggers → Add trigger → Webhook. Post the transcript from Zoom, Google Meet, Fathom or Plaud with title (meeting name) and description (transcript).
What to fill in
The prompts and commands read these as {{vars.<name>}}. The examples are placeholders: replace them with your own.
| Variable | What to put in it | Example |
|---|---|---|
attendees | Who usually attends and their roles, so owners are named correctly. | Maya (CEO), Tom (CFO), Priya (VP Product), Luis (VP Engineering), Ana (VP Sales) |
slackWebhookUrl | A Slack incoming webhook for the leadership channel. | — |
tasksWebhookUrl | Optional: where action items go, e.g. a Zapier hook into Asana, Linear or Notion. Leave empty to skip. | — |
Show the pipeline JSON
{
"jimothyPipeline": 1,
"name": "Leadership meeting decisions",
"description": "Pulls decisions, action items and open questions out of a meeting transcript and posts them after you check them.",
"icon": "workflow",
"color": "#6d28d9",
"repo": {
"mode": "scratch"
},
"concurrency": 2,
"variables": {
"attendees": "Maya (CEO), Tom (CFO), Priya (VP Product), Luis (VP Engineering), Ana (VP Sales)",
"slackWebhookUrl": "",
"tasksWebhookUrl": ""
},
"steps": [
{
"id": "extract",
"name": "Extract decisions",
"type": "agent",
"description": "Separates decisions from discussion and lists action items with owners and dates.",
"harnessId": "anthropic-api",
"model": "claude-sonnet-5",
"timeoutMinutes": 10,
"prompt": "Transcript of \"{{issue.title}}\". Attendees: {{vars.attendees}}.\n\n{{issue.description | truncate:80000}}\n\nWrite the meeting record for Slack (*bold* headings, - bullets):\n*Decisions*: only things explicitly agreed, each with who made the call\n*Action items*: \"<owner> — <action> — <due date or 'no date set'>\"\n*Open questions*: raised but not resolved, with who owns getting the answer\n*Parked*: topics deferred to a later meeting\n\nDon't record something as decided if people only discussed it. Use attendees' names.{{#if steps.approve.output}}\n\nYour previous record was rejected with these corrections. Apply them:\n{{steps.approve.output}}{{/if}}"
},
{
"id": "approve",
"name": "Check the record",
"type": "approval",
"description": "Shows you the record. Reject with corrections and it is redone.",
"dependsOn": [
"extract"
],
"loopBackTo": "extract",
"maxLoops": 3,
"approvalMessage": "Post this record of {{issue.title}}? Reject with corrections if anything is wrong.\n\n---\n\n{{steps.extract.output}}"
},
{
"id": "post",
"name": "Post to Slack",
"type": "shell",
"description": "Posts the record to the leadership channel.",
"dependsOn": [
"approve"
],
"timeoutMinutes": 2,
"command": "printf '{\"text\":%s}' {{steps.extract.output | json}} | curl -fsS -X POST -H 'Content-Type: application/json' --data @- {{vars.slackWebhookUrl}}"
},
{
"id": "tasks",
"name": "Send action items",
"type": "shell",
"description": "Sends the record to your task tool, if you set a webhook.",
"dependsOn": [
"approve"
],
"runIf": "{{vars.tasksWebhookUrl}}",
"timeoutMinutes": 2,
"command": "printf '{\"meeting\":%s,\"record\":%s}' {{issue.title | json}} {{steps.extract.output | json}} | curl -fsS -X POST -H 'Content-Type: application/json' --data @- {{vars.tasksWebhookUrl}}"
}
]
}More for executives, and beyond
Weekly executive briefing
Reads the week’s team updates and metrics from a shared folder and writes a one-page briefing: progress on priorities, risks and decisions needed.
ExecutivesDecision red team
Pressure-tests a proposal from three angles at once (financial, customer, execution) and writes a decision memo with a recommendation.
ExecutivesQuarterly investor update
Drafts the quarterly investor or board update from your metrics exports and weekly briefings, then has a skeptical board member read it first.