Stats
Actions
Tags
From forwward-teams
Transforms unstructured meeting transcripts, rough notes, or voice memos into clean summaries with decisions, action items (owner + deadline), and open questions. Use when you need to extract signal from any meeting type — standups, 1:1s, client calls, all-hands, retrospectives.
How this skill is triggered — by the user, by Claude, or both
Slash command
/forwward-teams:meetingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A meeting summary is not a transcript. It's a decision log and a task list. The person reading it wasn't there — or was there but needs to act on it. Every line either records a decision, assigns work, or flags a risk. Nothing else earns a line.
A meeting summary is not a transcript. It's a decision log and a task list. The person reading it wasn't there — or was there but needs to act on it. Every line either records a decision, assigns work, or flags a risk. Nothing else earns a line.
Assess the input before writing anything:
Ask if unclear: "Is this a transcript, notes, or raw thoughts?" Then proceed.
The output shape changes by type:
| Type | What matters most |
|---|---|
| Standup / sync | Blockers, status, handoffs |
| 1:1 | Decisions made, commitments, feedback |
| Client call | What was promised, open questions, next steps |
| Strategy / planning | Decisions with rationale, rejected options, open threads |
| Retrospective | What to change, who owns the change |
| All-hands / board | Key messages, decisions, follow-ups |
Pull from the input in this priority order. If a section is empty, omit it.
What was resolved. One line each. Past tense, specific.
- Approved Q3 hiring plan for 3 engineers and 1 designer.
- Agreed to delay the enterprise launch to September to hit the compliance milestone first.
- Dropped the white-label feature from v1 scope — revisit in Q4.
Who does what by when. Every item needs an owner. If no deadline was stated, leave it blank — don't invent one.
- @Sara — send revised contract to Acme by Friday
- @Jae — share onboarding doc draft with the team before next sync
- @Ian — follow up with legal on the data processing agreement (no deadline set)
Unresolved issues that need a decision or more information before work can proceed.
- Do we need SOC 2 Type II before enterprise can sign? (Owner: legal — Ian to confirm)
- What's the pricing model for the agency tier? (Still open — needs finance input)
Two to four sentences. The current state, what changed, and what's next. Enough for someone who wasn't there to understand the outcome without reading the sections above.
Slack / async message: Summary paragraph first, then a short bulleted list of action items. No headers. Under 120 words. Link to the full doc if it exists.
Written doc / Notion / Confluence: Full four-section structure with headers. Include date, meeting type, and attendees at the top.
Email follow-up:
Subject: [Meeting recap] <topic> — <date>
Body: summary paragraph + action items table. Under 200 words.
| Pattern | Fix |
|---|---|
| Transcribing instead of summarizing | Extract decisions and tasks, not dialogue |
| Action items without owners | Every item gets a name, even if it's "TBD" |
| Vague decisions: "we discussed X" | "We decided X" or "No decision reached on X" |
| Burying the decisions in narrative | Decisions section always comes first |
| Fabricating deadlines | If no deadline was stated, leave the field blank |
In:
Out:
/write for tone and structure/decknpx claudepluginhub iankiku/forwward-teamsConverts meeting notes, transcripts, or chat logs into structured minutes with decisions, action items, and open questions.
Summarizes meeting transcripts into structured Markdown notes with date, attendees, topics, key decisions, summary points, and action items. Use for processing transcripts, writing minutes, or organizing discussions.
Extracts key decisions, takeaways, action items with DRIs, and open questions from meeting transcripts, notes, or Slack threads. Handles single meetings or weekly batches.