design-exploration

Pre-implementation design exploration involves gathering codebase context and evaluating alternative architectural approaches to produce a validated design specification. This Skill facilitates that process by proposing multiple designs with trade-offs for review before coding begins.

Brainstorming a design plan is best handled through incremental design presentation, where approaches are proposed in manageable sections. This allows you to evaluate architectural patterns, gather input on challenges, and refine the plan step-by-step with user validation.

Yes, automatic context gathering is supported during architectural planning. It collects relevant project information by executing parallel agents, ensuring the proposed design approaches are grounded in your actual codebase structure before refinement.

Yes, user interaction is required for refining design specifications. The process presents designs incrementally and relies on your feedback at each step to validate the chosen architectural approaches and ensure the final plan is well-thought-out.

Pre-implementation design exploration should be bypassed when a task requires immediate coding without architectural planning, or when evaluating multiple design trade-offs is unnecessary for the scope of the specific software development task at hand.