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"