brainstormlisted

Use when the user wants to clarify a vague idea, compare meaningful directions, or choose a product or technical approach before planning. Explore conversationally, gather repo or external evidence only when it changes the decision, and write the chosen direction to `brainstorm.md`. Do not create an implementation plan or edit product code.
danielleit241/forge · ★ 1 · AI & Automation · score 70

Install: claude install-skill danielleit241/forge

# brainstorm Turn uncertainty into a user-confirmed direction. Keep the discussion natural; do not force research, option counts, debate, or a formal consensus ritual when the decision is already clear. ## Workflow 1. Restate the goal, outcome, and constraints. Ask only questions that cannot be answered from the request or repository. 2. Use `scout --repo` when local behavior or constraints affect the direction. Use research only for an external or version-sensitive claim that matters. 3. Compare alternatives only when there is a real tradeoff. State a recommendation and its downside. 4. Confirm the user's chosen direction, assumptions, and Not Doing boundary. 5. Write `plans/YYMMDD-{slug}/brainstorm.md` with the decision, evidence that affected it, tradeoffs, open questions, and Not Doing. This is the only brainstorm artifact. If the user wants implementation planning, hand off to `plan` with that file. Do not produce phase files, a separate research report, or a duplicate summary.