brainstorming

Start by reviewing the current project state, then answer clarifying questions one at a time about purpose, constraints, and success criteria. The design is presented in 200-300 word sections for validation, then written to docs/plans/ and committed to git.

Brainstorm before any creative work: creating features, building components, adding functionality, or modifying behavior. Clarifying requirements and comparing approaches upfront prevents rework from misunderstood intent.

The process proposes 2-3 approaches with explicit trade-offs, leading with a recommended option and the reasoning behind it. You can discuss alternatives conversationally before settling on a direction.

The validated design is written to docs/plans/YYYY-MM-DD-<topic>-design.md and committed to git. If continuing to implementation, it suggests creating an isolated git worktree and writing a detailed implementation plan.

The process depends on iterative conversation, so it is slower than writing code directly and less suited to trivial changes. It also relies on related skills like writing-plans and git worktrees for the implementation phase.