Meeting to decision memo
Skill nicholashidalgo/claude-skillforge/writing/meeting-to-decision-memo
npx -y skills add nicholashidalgo/claude-skillforge --skill meeting-to-decision-memoAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Converts raw meeting notes into a structured decision memo with owners and deadlines.
SKILL.md
3.0 KB, as published. Nobody here has run it
meeting-notes-to-decision-memo
Purpose: Turn messy meeting notes into a concise decision memo: decisions made, action items with owners and dates, open questions.
Input Schema
| Field | Type | Required |
|---|---|---|
meeting_title | string | yes |
date | string | yes |
attendees | string[] | yes |
raw_notes | string | yes |
preserve_facts | string[] | yes |
{
"meeting_title": "Checkout v2 Go/No-Go",
"date": "2024-03-18",
"attendees": ["Nick", "Sarah (PM)", "Dev (Eng Lead)"],
"raw_notes": "we talked about the launch. sarah said we should delay. nick pushed back. decided to do soft launch march 25 with 5% traffic. dev to set up flags by thursday. lots of debate about support readiness. open q: does support need more training?",
"preserve_facts": ["March 25", "5% traffic", "Thursday deadline for flags"]
}
Output Schema
{
"memo_title": "Decision Memo: Checkout v2 Go/No-Go (March 18)",
"decisions": [{"decision": "...", "rationale": "..."}],
"action_items": [{"item": "...", "owner": "...", "due": "..."}],
"open_questions": ["..."],
"next_meeting": "TBD"
}
Prompt Flow
Pass 1: Extract decisions, actions, open questions. Assign owners where named in notes. Remove: chatbot artifacts (P19), sycophancy (P21), filler (P22), generic conclusions (P24), AI vocab (P7), significance inflation (P1).
Pass 2: Verify every action item has an owner and due date (mark TBD if not stated - do not fabricate).
Examples
Short
Before notes: "We decided to go with option B. John will do the thing by next week." After:
- Decision: Option B selected.
- Action: John to complete implementation. Due: March 25.
Medium
Before notes: "big discussion about launch. ultimately decided soft launch. eng will set feature flags. pm will brief support. support training might be needed." After:
- Decision: Soft launch at 5% traffic on March 25.
- Actions: Dev - set feature flags by March 21. Sarah - brief support by March 22.
- Open question: Does support need additional training before full rollout?
Long
Unit Tests
# tests/skills/test_meeting_notes_to_decision_memo.py
from ai_pattern_scrubber import detect_patterns
DECISION = "Decision: Soft launch at 5% traffic on March 25."
ACTION = "Dev to set feature flags by March 21. Sarah to brief support by March 22."
def test_decision_no_filler():
assert not [h for h in detect_patterns(DECISION) if h.id == 22]
def test_action_no_high_severity():
assert not [h for h in detect_patterns(ACTION) if h.severity == "high"]
def test_decision_no_ai_vocab():
assert not [h for h in detect_patterns(DECISION) if h.id == 7]