brainstorm

brainstorm

Turn a fuzzy problem into a structured set of candidate ADRs and plan items. This skill is generative and read/propose-only — it never writes ADRs or plan files directly. On approval it hands each candidate to the new-adr and new-plan skills.

Step 0 — Preconditions and context

1. Confirm the repo is bootstrapped (or note that the output can seed a fresh run of the bootstrap skill).
2. Read CONVENTIONS.md for ADR shape and lifecycle, and skim INDEX.md + existing ADRs so candidates don't duplicate or contradict what already exists, and so dependencies point at real ADRs.

Step 0.5 — Assessment (run first)

Run the shared assessment protocol before decomposing:

• Depth selector first. Ask how deep this assessment should go: express — every choice takes its recommended default; only questions with no derivable default (the free-text essentials) are still asked; guided — only the questions marked high-impact below, plus the free-text essentials; full — every question below. If the repo's CONVENTIONS.md records an Assessment depth:, pre-select it as the recommended option — the selector always appears; a recorded depth is never applied silently. Otherwise recommend full when the request arrived with little or no context and express when it is already fully specified. At any question the operator may answer "defaults from here" or "go deeper"; honour the switch immediately.

• Ask the questions below one at a time, each with a recommended option and a one-line reason; wait for each answer.

• Use structured selection (single- or multiple-choice). If the host exposes a structured single-/multi-select question tool, use it and mark the recommended option; otherwise list options A/B/C in plain text and name the recommended one. Use free text only where an enumerable set is impossible (e.g. the goal statement).

• The operator decides. Never proceed past a question without an answer, and never guess scope when invoked with no context.