Tue 3 March 2026, 10:00–10:40, video call
Present: Priya (marketing), Tomás (product), Lena (support), Ade (ops). Jun sent apologies.
Purpose (from invite): agree launch plan for the Commuter 2 e-bike.
[10:02] Tomás: firmware 1.4 still fails the hill-start test on the 20 kg rear rack config. Vendor says fix by 13 March.
[10:06] Priya: we said launch 24 March. If firmware slips we lose the trade-show slot. Proposal: launch 24 March anyway, ship firmware as an over-the-air update.
[10:09] Lena: support can't take OTA questions without a help article. Needs to be live before launch.
[10:11] Ade: warehouse can only take the first 400 units on 18 March, rest a week later.
[10:15] Tomás: OK with OTA as long as hill-start is fixed in the first update. Agreed by everyone: launch date stays 24 March.
[10:18] Priya will write the press note, draft by 10 March.
[10:20] Someone should brief the retail partners. (no name)
[10:24] Lena to draft OTA help article. Ade: maybe Lena can also cover the warranty FAQ?
[10:27] Ade: pre-orders over 400 ship second wave — need to tell customers. Priya thinks the email goes out on the 16th, Ade says 20th.
[10:31] Decision: price stays at 2,190 EUR. Discount code idea parked for now.
[10:35] Tomás to confirm with vendor in writing that 13 March holds. By Friday.
[10:38] Open: do we pause pre-orders if firmware misses 13 March? Not decided.
Fictional sample. Fernway Bikes, its people and every figure are invented for this demonstration.
Date: Tue 3 March 2026, 10:00–10:40 (video call)
Participants: Priya (marketing), Tomás (product), Lena (support), Ade (ops). Jun absent.
Purpose: Agree the launch plan for the Commuter 2 e-bike.
Launch stays on 24 March even though firmware 1.4 may slip, with the hill-start fix shipped as the first over-the-air (OTA) update. Stock arrives in two waves. Who briefs retail partners, when the second-wave email goes out, and whether to pause pre-orders are still open.
| # | Decision | Source |
|---|---|---|
| D1 | Launch date stays 24 March (agreed by everyone). | 10:15 |
| D2 | Firmware ships as an OTA update; the first update must fix hill-start (Tomás's condition). | 10:06, 10:15 |
| D3 | Price stays at 2,190 EUR. | 10:31 |
Proposal, not decided: discount code (parked, 10:31).
| # | Action | Owner | Due | Source |
|---|---|---|---|---|
| A1 | Draft the press note | Priya | 10 March | 10:18 |
| A2 | Confirm in writing with the vendor that the 13 March firmware fix holds | Tomás | Friday (date not specified) | 10:35 |
| A3 | Draft the OTA help article; must be live before launch | Lena | Before 24 March | 10:09, 10:24 |
| A4 | Brief the retail partners | Unassigned | Not specified | 10:20 |
| A5 | Tell pre-order customers beyond the first 400 units that they ship in the second wave | Unassigned | 16 or 20 March (conflicting) | 10:27 |
Ade's suggestion that Lena also cover the warranty FAQ (10:24) was not accepted in the notes, so it is not listed as an action.
Produced by following meeting-to-action/SKILL.md on samples/input.md. Fictional data.
--- name: meeting-to-action description: "Shape messy meeting notes into decisions, owners, and clear next steps." --- # Meeting → Momentum ## When to use Use this skill to turn supplied meeting notes or a transcript into an accurate, concise action brief. ## Workflow 1. Identify the meeting date, participants, and stated purpose from the source. Mark missing context as unknown. 2. Extract explicit decisions separately from proposals, opinions, and unresolved questions. Preserve caveats. 3. List actions with the exact task, explicitly assigned owner, and stated deadline. If an owner or date is missing, say unassigned or not specified. Do not infer a commitment from a suggestion. 4. Group related actions and identify dependencies supported by the notes. Flag contradictions for clarification. 5. Produce a concise summary, decisions, action list, and open questions. Add source timestamps or sections when available. 6. Compare the final brief against the source. Remove unsupported details and unnecessary personal information. ## Definition of done Every action traces to source material. Ambiguity is visible. The brief does not send messages, create calendar events, or assign tasks without a separate user request.
npx skillbay install meeting-to-action --agent claude-codeOther agents and scopes: see Installation below.
Bring structure to meeting notes without losing nuance. This workflow separates decisions from ideas, identifies explicit owners and dates, and flags unresolved questions instead of filling in the blanks.
The package is instructions only: SKILL.md, a README and the sample run as Markdown, no scripts.
.claude/skills/meeting-to-action/Review the package, then place the complete skill folder here. Keep SKILL.md, scripts, references and assets together.
/meeting-to-actionnpx skillbay install meeting-to-action --agent claude-codeRun from your target workspace. Requires Node.js 22 or later. Sign in once with npx skillbay login; premium packages install with an active plan. CLI docs
Use the meeting-to-action skill. Read SKILL.md first. Ask me for anything it needs that I have not given you, follow its steps on my material, then report what you checked and anything you could not verify.
Turns a tidy CSV and a short brief into an offline, interactive data report whose KPIs, trends, anomalies and narrative are computed, never typed.
Claude Code
Codex
Gemini CLI