---
name: brainstorm
description: Design a change before implementation.
---

# Brainstorm

Explore the repository and clarify the goal, constraints, and acceptance criteria. Present only viable approaches and state a recommendation. Write the resulting design to `docs/specs/YYYY-MM-DD-<slug>-design.md`.

For work that needs Factory execution, create a concise markdown plan with explicit files, behavior, and verification, then hand it to the appropriate Factory ADW. Factory state, phases, evidence, and decisions are owned by `modules/harness/factory/`; use its CLI and prompt contracts rather than inventing an execution journal or plan protocol.

Keep designs contract-level: describe seams, data shapes, error handling, and tests, not implementation bodies. Ask the user only for genuine preference or irreversible decisions. Do not create execution JSONL, dispatch waves, resume instructions, or runner-specific commands.