brainstorming

Start by exploring the current project context, then clarify purpose, constraints, and success criteria one question at a time. Propose 2-3 approaches with trade-offs, present the design in small sections for approval, and write the result to a dated design document.

Present the design in sections of 200-300 words and get explicit approval after each section rather than delivering one large document. Always show the full section text in the same message as the approval question so reviewers see exactly what they are confirming.

Yes, every project goes through the design process regardless of perceived simplicity, including single-function utilities and config changes. The design can be only a few sentences for simple work, but it must be presented and approved before implementation.

Decompose when the request describes multiple independent subsystems that cannot fit a single spec. Identify the independent pieces, their relationships, and build order, then run the normal design flow on the first sub-project.

After the spec passes an inline self-review for placeholders, consistency, scope, and ambiguity, the user reviews the written file. Once approved, the workflow transitions to the writing-plans skill to create a detailed implementation plan.