Extract decisions, action items, owners, and due dates from meeting notes, Slack threads, design-review transcripts, or any unstructured discussion. Produces a clean structured log the user can paste into a doc, tracker, or ADR queue. Use when the user has notes/threads/transcripts and asks for a "decision log", "action items", "what did we agree", or "follow-ups".
Pack stakeholder-commsTier lightJob Explain it to decision makersv0.1.1
In Claude Code, with the stakeholder-comms plugin installed, invoke it as:
/stakeholder-comms:decision-log
Try it
A realistic prompt from the skill's acceptance evals:
Pull the decisions and action items out of this design-review transcript. [transcript: mixed opinions, a couple of agreed decisions, some unowned follow-ups, and relative dates like 'next Friday']
What a good result looks like
Don't invent ownership. If the source says "we should email the legal team", don't pick a name. Flag as unowned.
Don't promote opinions to decisions. "I think we should use Postgres" is not a decision unless the group acknowledged it.
Quote, don't paraphrase, the source column. A 5–10 word verbatim snippet is the audit trail.
Active voice in the action column. ✅ "Send PR for ADR-0007 to legal" — ❌ "ADR-0007 to be sent to legal".
Convert relative dates. Today's date is needed — ask if unclear.
How it's checked
Measured against plain Claude Code (2026-10-23): it met 57% of its checks, against 62% without it, and a blind judge preferred it. How skills are checked
18 assertions across 3 acceptance evals, and 8 trigger queries. Every skill's checks
What the output must do
Opinions are not promoted to decisions — only items the group acknowledged appear as decisions
Ownership is never invented; items with no named owner are flagged unowned rather than assigned
The source column quotes the discussion verbatim in a short snippet, not a paraphrase
Action items are written in active voice
Relative dates are converted to absolute dates, marked when inferred
The output is a structured table the user can paste into a doc or tracker
It records the fireworks supplier decision as Northern Lights Pyro at £4,250, because the Skyburst decision was reversed later in the same meeting; Skyburst is not shown as the final decision
It does not record 7 November as an agreed date: following the chair's correction in the thread, the date is shown as still open pending Wrenfield FC
The hog roast versus WI tea tent question is shown as undecided, not as a decision
The Church Lane road-closure call is logged as an action with no owner rather than assigned to someone, and the hi-vis vests are owned by Sam Okoro (per the thread), not Sam Patel or an unspecified 'Sam'
It flags that £1,200 plus £250 is £1,450, not the £1,500 stated in the notes
It does not invent owners or due dates; in particular the 'by next Friday' deadline for the cancelled Skyburst booking is not carried over to the Northern Lights booking as if it had been stated
The whole log fits on roughly one screen
The list gives Mark on bunting, Priya on the gazebo, Jo on music, Tom on the barbecue and Ama on cake
Priya's condition (she needs someone to help carry the gazebo) is kept
Asking the council about closing the road is shown as not taken by anyone (Tom declined), not assigned to someone
It does not invent a month for 'the 12th', deadlines or owners that are not in the chat
It is just a short list with no long preamble, and it delivers without asking questions first
When it should and shouldn't activate
Should activate:
Extract the decisions and action items from these meeting notes
Turn this Slack thread into a decision log with owners and due dates
What did we actually decide in this transcript, and who owns what?
Give me a structured log of decisions from this design review