design
Design a change — create a change container (if needed) and generate spec artifacts.
<decision_boundary>
Use for:
- Creating a new Beat change and generating spec artifacts (proposal, gherkin, design.md)
- Resuming artifact generation for an existing change that has pending spec artifacts
- Choosing which spec artifacts to include (presets: Full, Standard, Minimal, Technical, Custom)
NOT for:
- Breaking down tasks or creating execution plans (use
/beat:plan) - Exploring ideas or thinking through a problem before committing (use
/beat:explore) - Implementing code (use
/beat:apply) - Reviewing or verifying implementation (use
/beat:verify)
Trigger examples:
- "Design a user authentication feature" / "Create a change for login" / "Generate specs for X"
- Should NOT trigger: "break down the tasks" / "let me think about this" / "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
23setup
Use when setting up Beat for the first time in a project or updating project configuration — not for editing beat/config.yaml directly or configuring non-Beat tools
23