brainstorming

To convert ambiguous ideas into approved design specifications, this skill reviews project context, asks clarifying questions sequentially, proposes viable approaches with trade-offs, and requires user approval before drafting a committed design doc.

The best way to enforce an approval workflow before implementation is applying a hard gate against coding actions, presenting design sections for explicit user approval, and preventing transition to planning until validated.

Yes, you can use this skill for small to medium scope component design, behavior changes, and feature requests, establishing a coherent architectural plan before any coding begins.

Requirements discovery for spec writing works by reviewing current project context and asking one clarifying question at a time to refine scope and success criteria for architecture changes.

The design specification process includes only implementation gating and no code writing; it transitions solely by invoking the writing-plans skill after the final design doc is committed and reviewed.