brainstorming

Turn vague ideas into structured design plans through guided brainstorming that surfaces goals, constraints, and success criteria. The process uses one-question-at-a-time inquiry to refine intent before producing a design document.

A design-first workflow creates plans and design documents prior to any coding or scaffolding. It gathers context during project kickoff and scopes features through iterative clarifying questions to ensure design readiness.

Yes, you can scope project requirements through an iterative, one-question-at-a-time process. This enforces user approval at each step, ensuring goals and constraints are fully clarified before moving to implementation.

Transition from a design doc to implementation tasks by handing off the finalized design document to the writing-plans skill. This seamless handoff converts the approved design artifacts into concrete development tasks.

Yes, the brainstorming process explicitly requires user approval before moving to implementation. This gate ensures the design document accurately captures all scoped features and constraints before any coding starts.

The best way to facilitate a project design kickoff is through structured context gathering and guided inquiry. This coordinates collaboration by surfacing requirements and producing shared design artifacts for the team.