brainstorming

To turn rough ideas into validated designs, you need structured requirement discovery. This process clarifies purpose and constraints one question at a time, compares 2-3 approaches with trade-offs, and secures staged design approval before writing specifications.

Structuring feature requirements requires reviewing project context first, then guiding clarification to define success criteria. This approach comparison method ensures component design fits the existing codebase before any specification writing begins.

Planning implementation for behavior changes requires slowing down to perform product discovery. By validating the design through staged approval and writing a self-reviewed spec, you ensure the changes are fully specified before coding begins.

Yes, this brainstorming approach is specifically designed for open-ended software tasks and product discovery. It applies to feature creation and behavior changes, requiring project-context review to ensure recommendations fit your existing environment.

Yes, the requirement discovery process works for existing codebases by starting with a project context review. This ensures that all design recommendations and generated specifications align with your current documentation and code structure.

After staged design approval and specification writing, the process concludes with a self-review and handoff. The finalized spec is passed directly to writing-plans to transition from validated design into actionable implementation steps.