Brainstorming Ideas Into Designs

DIVERGENCE FROM superpowers:brainstorming: Lightly forked. The one-question-at-a-time / present-alternatives / validate-incrementally discipline is shared. CC10x ADDS: the Spec File Workflow, the AskUserQuestion interview machinery, the full design-document template, the router-owned machine-readable handoff that carries the design forward into the PLAN workflow, a front-of-flow scope-triage gate that decomposes multi-subsystem requests and brainstorms only the first sub-project, a Design Self-Review gate that scans the produced design for placeholders, contradictions, and ambiguity before the handoff, an accreting domain glossary plus inline ADR-on-rejection notes (durable vocabulary + rejected-alternative decisions, emitted via the router-owned handoff to feed ORIENT and the planner downstream), and a gated synthesize-now fast path that drafts the design from existing context when goal + constraints + acceptance are already evident, skipping the full interview.

Overview

Help turn rough ideas into fully formed designs through collaborative dialogue. Don't jump to solutions - explore the problem space first.

Core principle: Understand what to build BEFORE designing how to build it. Use the user's language for domain concepts; do not invent new terminology when the repo or prompt already has a stable name for the thing.

Violating the letter of this process is violating the spirit of brainstorming.

The Iron Law

NO DESIGN WITHOUT UNDERSTANDING PURPOSE AND CONSTRAINTS