Brainstorming Ideas Into Designs

Overview

The Process

• Review current project context first (key files/docs, recent commits, existing patterns).
• Ask one question per message to refine the idea (prefer multiple-choice when possible).
• Focus on: purpose, constraints, success criteria, non-goals.

• Propose 2–3 approaches with trade-offs.
• Recommend one approach and explain why.

• Present the design in 200–300 word chunks and confirm after each chunk.
• Cover: architecture, components, data flow, error handling, testing.
• Be ready to backtrack if the user says something doesn’t fit.

After the Design

• Write the validated design to

  docs/plans/YYYY-MM-DD-<topic>-design.md

  when that convention exists; otherwise create

  docs/plans/

  or ask where to put it.
• If you have a writing-quality skill available, use it before finalizing the doc.
• If the repo is under git and the user wants it tracked, commit the design doc.

• Ask: “Ready to set up for implementation?”
• If the user wants a separate workspace, use a git worktree.
• Create a concrete implementation plan before writing code.

Key Principles

• One question at a time — Don’t overwhelm with a questionnaire.
• Multiple choice preferred — Faster to answer and reduces ambiguity.
• YAGNI ruthlessly — Remove unnecessary scope/features from designs.
• Explore alternatives — Always consider 2–3 viable approaches.
• Incremental validation — Confirm each design chunk before continuing.
• Be flexible — Adjust quickly when something doesn’t fit.