meeting-notes-to-actionslisted

# Meeting Notes → Actions Turn messy notes into three things: a decision log, an owned action list, and a follow-up email the user can send in 30 seconds. ## Step 1 — Load context Read `.solo/business.md` if present (for tone and to recognize client names). Proceed without it if missing — this skill works standalone. ## Step 2 — Get the notes Accept a pasted transcript, a file path, or bullet notes. If it's a transcript, identify speakers; if names are missing, use roles (Client, Me). ## Step 3 — Extract, then verify Extract: - **Decisions** — things that were agreed. Quote or closely paraphrase; do not upgrade "we could" into "we will". - **Actions** — each with an owner and a due date if stated. If no date, mark `(no date set)` rather than inventing one. - **Open questions** — anything raised but unresolved. - **Risks / flags** — budget hesitation, scope drift, unclear decision-maker, missed deadlines mentioned. Before writing the email, show the user the decisions and actions and ask one question: "Anything wrong or missing?" Skip this check only if the user said "just do it". ## Step 4 — Write the outputs Write `meetings/<YYYY-MM-DD>-<client-or-topic-slug>.md`: ```markdown # <Topic> — <date> Attendees: ... ## Decisions - ... ## Actions | Owner | Action | Due | |-------|--------|-----| | Me | ... | ... | | <Client name> | ... | ... | ## Open questions - ... ## Flags - ... ## Follow-up email (draft) Subject: <Topic> — recap and next steps Hi <name>, Than