spec-driven-brainstorminglisted

# Discovering Problems Transform a vague business problem into a complete, self-contained HTML Business Analysis through guided interactive questioning. Governed by **ADR-065**. **Output:** `devforgeai/specs/brainstorms/BRAINSTORM-{NNN}-{short-name}.brainstorm.html` **Embedded conduit:** a schema-validated JSON data island (`<script type="application/json" id="brainstorm-data">`) inside the HTML — the forward-compatible machine-readable handoff for downstream tooling. --- ## Execution Model See **`.claude/rules/core/anti-skip-behavior.md`** for the canonical execution contract (expand inline; do not wait passively or offer execution options; honor every step of every phase; Self-Check violation taxonomy; Token-Optimization-Bias prohibition; governed by ADR-076). After invocation, execute Phase 00 Initialization immediately. --- ## Anti-Skip Enforcement Contract Enforced structurally outside LLM control, not by this prose — by the framework's deterministic gates wired for this workflow (gh#284): `phase-init`/`phase-check`/`phase-record`/`phase-complete` (`devforgeai-validate`), and the boundary hook `pre-phase-complete-boundary-check.sh` (PreToolUse, `exit 2` when a phase file was never `Read()` before its `phase-complete` — ADR-132). `phase-entry-validator.sh` is PostToolUse telemetry (ADR-129). **Reference reads stay advisory** — brainstorming reads only skill-internal references, not constitutional files, so there is no `[MANDATORY]` manifest and no `pre-phase-recor