| name | brainstorming |
| description | Turn a vague idea into one selected direction and a compact Design Handoff, then recommend the next owner. |
| disable-model-invocation | true |
brainstorming
Explicit-only. Turn vague intent into one selected direction and a Design Handoff. Stay at product/design/architecture altitude: no file-by-file steps, tracker mutations, executor prompts, or a parallel project charter. Recommend the next owner as text; never invoke it.
Workflow
- Ground in context first. Inspect safely discoverable repository context (README, docs, existing code, the task mirror, sprint notes) before asking anything. Never ask what context already answers. Never restate a fact the user has already supplied.
- Size the pass by clarity.
- Genuinely vague work: ask 1-5 material questions, one at a time, each only when its answer would change the decision. Stop asking once the direction is determined.
- Clear, low-risk request: ask at most one question — often zero. Keep the pass short.
- Honor an explicitly requested successor or route without re-asking.
- If the user delegates the judgment, choose and explain rather than block.
- Compare viable approaches. Name the genuinely viable approaches and their material trade-offs. Recommend one. Accept an override.
- Resolve what matters. Settle high-impact uncertainty. Record low-impact uncertainty under Open decisions requiring a human instead of prolonging the interview.
- Emit the Design Handoff below — every field, verbatim labels.
- Recommend a successor using the routing table.
Design Handoff
## Design Handoff
Problem:
User-visible outcome:
Chosen direction:
Why this direction:
Important alternatives rejected:
Constraints and compatibility requirements:
Open decisions requiring a human:
Recommended next step:
Why:
Successor routing
Recommend exactly one, based on the result.
| Result | Recommended next step |
|---|
| Direction selected, implementation intent still needs synthesis | feature-spec |
| An adequate source artifact needs decomposition/tracking | tracker-neutral decomposition handoff; recommend dev-backlog shape only when it is observed available, else record literal shape unavailable and stop |
| Already a settled single unit | implement (localized) or relay (durable/high-risk), by task-specific evidence |
| User asked for exploration only | stop after the handoff |
| User asked to stress-test an already-chosen plan | recommend a compatible grill capability only when it is observed available, else record it unavailable and stop — do not impersonate grill |
Availability is observed, never inferred from prose or from unrelated global installations on this machine. Detailed examples and edge cases: references/routing.md.
Capabilities
Uses two capabilities: read-only inline_repository_work and blocking_user_question. If the blocking-question capability is unavailable, do not guess through the blocker — inspect what is discoverable, move every unresolved material decision into Open decisions requiring a human, and keep the Design Handoff contract unchanged.
