brainstorming

To turn vague feature ideas into actionable design plans, the skill uses structured discovery to ask clarifying questions one at a time, exploring intent and constraints. It then proposes 2-3 alternative approaches with trade-offs and a recommended path before any implementation begins.

Documenting a software design proposal involves presenting incremental design sections for explicit user validation. Once approved, the design is persisted as a committed design document saved under docs/plans/YYYY-MM-DD-<topic>-design.md to ensure requirements are thoroughly examined.

Preventing premature implementation during feature planning requires a safety gate that prohibits any implementation actions or invocation of implementation skills. This enforces a hard stop until the design proposal is fully validated and explicitly approved by the user.

Yes, you can use this structured discovery process for refactoring and configuration changes. The workflow applies to any feature planning, small utilities, or changes where exploring intent, constraints, and trade-offs through one-at-a-time questions is required.

The design validation workflow handles alternative approaches by generating 2-3 distinct options with detailed trade-offs. It then recommends a preferred path with reasons, presenting these designs in incremental sections to obtain explicit user approval before proceeding.