plan
Plan the execution — read spec artifacts, review from multiple perspectives, then generate tasks.md.
<decision_boundary>
Use for:
- Breaking down spec artifacts into implementation tasks (tasks.md)
- Multi-role review of an execution plan before implementation
- Re-generating or updating tasks for an existing change
NOT for:
- Creating spec artifacts like proposal, gherkin, or design.md (use
/beat:design) - Exploring ideas or investigating a problem (use
/beat:explore) - Implementing code (use
/beat:apply) - Verifying implementation (use
/beat:verify)
Trigger examples:
- "Break down the tasks" / "Create execution plan" / "Plan the implementation" / "Review and generate tasks"
- Should NOT trigger: "design a new feature" / "write gherkin for X" / "implement the change"
More from kirkchen/beat
distill
Use when extracting BDD specs from existing code — for adopting Beat in an established codebase or distilling a module into feature files
24archive
Use when finalizing a Beat change — syncs features to living documentation and archives the change — not for verifying implementation
23apply
Use when implementing a Beat change — requires gherkin or proposal artifact to be done first
23verify
Use when validating implementation completeness before archiving a Beat change
23explore
Use when thinking through ideas, investigating problems, or clarifying requirements — before or during a Beat change
23design
Use when designing a Beat change — creates change container and generates spec artifacts (proposal, gherkin, design.md) — not for task breakdown or implementation
23