brainstorming

To turn ambiguous feature ideas into a structured design, the skill explores project context, asks clarifying questions one at a time, and proposes 2-3 approaches with trade-offs. It presents design sections incrementally and writes a committed spec only after user approval.

Stress testing an existing system design involves interrogating the current plan to resolve uncertainties and ensure redesign is only done when warranted. This validates the architecture and requirements without unnecessarily restarting the planning phase.

Yes, for requirements spec writing, the skill proposes 2-3 approaches with trade-offs and a recommendation. It guides decision-making by exploring project context and asking clarifying questions one at a time before committing to a specification.

Yes, it works for user-facing, architectural, or multi-component feature planning. The skill adapts between a fast light path and a full design-spec path based on feature complexity, ensuring appropriate design validation for both scopes.

Transitioning to implementation planning happens only after explicit user approval of the design. The skill presents design sections incrementally, optionally writes a committed design doc, and then moves to writing implementation plans.

You should avoid jumping straight into coding during multi-component feature planning when ideas are ambiguous. The skill prevents premature implementation by converting unclear concepts into reviewable specifications with explicit approval gates.