Meeting Notes Architect

Meeting Notes Architect takes the raw material from any meeting — a voice transcript, a hasty bullet dump, or a stream-of-consciousness summary you typed on your phone — and structures it into a professional, actionable document. The skill applies a consistent framework: it identifies decisions made, action items with owners, open questions, and key discussion points, then formats everything so the output is ready to send or drop into a project management tool without editing.

A typical input looks like: 'We talked for 45 minutes about the Q3 product roadmap. Sarah wants to push the API feature to Q4. Marcus is worried about capacity. We agreed to run a resourcing audit by Friday. No one could agree on the release date. Follow up needed with legal on the data terms.' That is enough for the skill to work with — messy, partial, and out of order.

The output excerpt it returns follows a fixed structure: a one-sentence meeting summary, a Decisions section (e.g., 'API feature deferred to Q4'), an Action Items table with owner and due date columns, an Open Questions list (e.g., 'Release date — pending legal input on data terms'), and a Next Steps note. Every section is labeled, every action item is attributed, and the document reads like something a chief of staff wrote.