What problem does it solve?
Planning Beat changes requires reading spec artifacts, coordinating multi-role reviews, and producing a clear tasks.md to guide implementation.
This skill ensures artifacts are broken down into concrete tasks with guardrails before work begins.
Core Features & Use Cases
- Spec-driven planning: reads gherkin, proposal, and design to surface a concrete task breakdown.
- Multi-role review orchestration: suggests roles based on complexity; allows adjustment and confirmation.
- Plan generation with quality guardrails: outputs tasks.md including a Quality Principles section and testing focus.
- Prerequisite enforcement: ensures at least one spec artifact exists before planning; reads status.yaml to verify readiness.
Quick Start
Invoke /beat:plan after identifying a change to generate the initial tasks.md for beat/changes/<name>.