Meeting Action Closure Gate
Use this skill when meeting notes need to become trackable work instead of a summary that nobody owns.
Required flow
- 1. Read the transcript and attendee list. Extract decisions, action items, and open questions using
references/extraction-prompt.md and the exact schema in references/schema.md. - Save the transcript and extraction as UTF-8 JSON, then run
scripts/build_action_pack.py. - Show the generated release gate and approval queue to a human. Do not create external tasks until a human confirms the ready drafts.
Command
CODEBLOCK0
Non-negotiable rules
- - Every decision and action must cite one or more transcript segment IDs.
- Do not invent an owner or deadline. Missing values stay empty and become blockers.
- A named owner must match the attendee list unless
allow_external_owner is explicitly enabled. - All generated task objects are drafts with
approval_required: true. - Never write to Feishu, Notion, Jira, calendars, email, or chat without human approval.
- Do not include secrets, private recording URLs, or unnecessary transcript text in downstream task payloads.
Outputs
- -
meeting_digest.md: readable decisions, actions, blockers, and open questions. - INLINECODE6 : auditable task register.
- INLINECODE7 : every proposed action plus its blockers.
- INLINECODE8 : ready-to-map task drafts, still requiring approval.
- INLINECODE9 : metrics and PASS/BLOCK decision.
Recovery
- - Unknown evidence ID: correct the extraction; never silently remove the citation.
- Missing owner or due date: send the item to the approval queue for assignment.
- Duplicate task: keep the first item and merge evidence only after a human checks the wording.
- Invalid date: replace it with an ISO
YYYY-MM-DD date or leave it empty.
