brainstorminglisted
Install: claude install-skill rarango10/GoHarness
# Brainstorming
Turn an idea into a clarified, approved design through conversation — before writing a spec or touching code.
This project's workflow is: brainstorm (this skill) → spec (`docs/`) → implementation (TDD) → verification → commit. This skill covers only the first step. Writing the spec file and planning implementation are out of scope here — they happen after this skill's approval gate.
<HARD-GATE>
Do NOT invoke any implementation skill, write any code, write a spec file, or take any implementation action until you have told your human partner what you intend and they have explicitly approved it.
</HARD-GATE>
## Anti-Pattern: "Too Simple To Need Approval"
Every brainstorm ends with the human partner approving the design before anything else happens. For a small change the design might be two sentences in chat — but you must still present it and get a yes. "Simple" changes the size of the design, never whether approval is needed.
| Thought | Reality |
|---------|---------|
| "This is too simple to need a design" | Simple means a short design, not no design. |
| "The design is obvious — I'll start while they read it" | Present, then stop. Don't act until you hear yes. |
| "They approved something similar before" | Each idea gets its own approval. |
| "They said 'go ahead' / 'sure, do it' — I can also draft the spec while I'm at it" | Approving the design isn't approval to skip the next checkpoint. Announce the next step and stop — don't bundle it into the same