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"

design