Brainstorming Ideas Into Designs

Overview

Transform rough ideas into fully-formed designs through structured questioning and alternative exploration.

Core principle: Ask questions to understand, explore alternatives, present design incrementally for validation.

Announce at start: "I'm using the Brainstorming skill to refine your idea into a design."

When design is approved and implementation will follow:

Announce: "I'm using the Using Git Worktrees skill to set up an isolated workspace."
Switch to skills/collaboration/using-git-worktrees
Follow that skill's process for directory selection, safety verification, and setup
Return here when worktree ready

Ask: "Ready to create the implementation plan?"

When your human partner confirms (any affirmative response):

Announce: "I'm using the Writing Plans skill to create the implementation plan."
Switch to skills/collaboration/writing-plans skill
Create detailed plan in the worktree

You can and should go backward when:

Partner reveals new constraint during Phase 2 or 3 → Return to Phase 1 to understand it
Validation shows fundamental gap in requirements → Return to Phase 1
Partner questions approach during Phase 3 → Return to Phase 2 to explore alternatives
Something doesn't make sense → Go back and clarify

Don't force forward linearly when going backward would give better results.

During exploration:

When approaches have genuine trade-offs: skills/architecture/preserving-productive-tensions

Before proposing changes to existing code: