/rota-brainstorm
Negotiate the design of one Major item before planning it.
When to use
Use when a Major feature or P0 bug needs design negotiation before implementation planning, or on “brainstorm 42”, “design this item”.
Reach for another skill when
- the scope is the whole project or a milestone, not one backlog item:
/rota-vision - the shape is already clear and you need tasks with verify steps:
/rota-plan - one factual question must be tried out before any design makes sense:
/rota-spike
/rota-brainstorm 42
Read #42, KNOWLEDGE.md and DECISIONS.md. Question: does "resolved" mean Completed only, or ARCHIVE.md too?
Completed only.
Design drafted: 3 approaches with tradeoffs, recommended #2. Approve and hand off to /rota-plan, approve with no plan yet, or revise?
- the approved design stored as a note on issue #42 (file backend
.rota/designs/<ID>.md) - nothing in code
Flags and modes
--grill- force the one-pass grilling of open decisions on any item, not only Major features and P0 bugs
Details
Per-item design exploration before /rota-plan: Socratic discovery, 2-3 approaches with tradeoffs, then a sectioned design approved section by section. It stores the design as .rota/designs/<ID>.md (file backend) or a note on the issue (issue backend), which /rota-plan reads as soft input. Major features and P0 bugs get one grilling pass first, settling every open decision before drafting; --grill forces that pass on any item. The skill is skipped when the issue body already has ## Acceptance.
See brainstorming a design for the full flow.