| name | meeting-to-plan-integrator |
| description | Takes decisions from a meeting (sprint demo, retro, stakeholder call, team sync) and applies them to the release plan and related artifacts. The 'decisions become actions' bridge. Use when asked to: apply meeting decisions, update the plan from meeting notes, integrate feedback, or cascade changes from a meeting. |
Meeting-to-Plan Integrator — Entry Orchestrator
NON-NEGOTIABLE (read first)
- Save every artifact to file before presenting in chat. Chat is ephemeral.
- Never fabricate decisions. Every change must trace to a specific decision from the meeting. Unknown =
[TBD].
- Never skip checkpoints. Every CHECKPOINT requires user confirmation before proceeding.
- Graded provenance: every edit to a target document carries source attribution:
(Source: [meeting-name], [date]). Decisions are authoritative claims. Impact analysis is synthesized analysis. Cascade predictions are inference and must be confirmed before applying.
- One stage at a time. Complete and save before starting the next.
- Never apply changes the user hasn't confirmed. The change manifest is the contract.
Purpose
Take decisions from a meeting and apply them to the release plan and related artifacts. This is the "decisions become actions" bridge.
What you'll produce:
- Updated target documents with source-attributed edits
- Change-Manifest-[date].md — record of what changed, why, and where
When to invoke:
- After a sprint demo where stakeholders gave feedback
- After a retrospective with action items
- After a stakeholder call with scope or timeline changes
- After any meeting that produced decisions affecting the plan
Workflow Chain
[You are here]
SKILL.md (Intake)
↓ reads
workflows/01-intake.md → loads meeting decisions, identifies targets
↓ reads
workflows/02-extract-changes.md → classifies decisions, builds change manifest
↓ reads
workflows/03-apply-changes.md → applies confirmed changes to documents
↓ reads
workflows/04-cascade.md → checks for downstream effects
