spec-driven-ideationlisted

# Spec-Driven Ideation Transform business ideas into structured, actionable requirements through guided interactive questioning with structural anti-skip enforcement. **Output:** `devforgeai/specs/requirements/{project-name}-requirements.md` (YAML per F4 schema) **Feeds Into:** `/create-solution-architecture` command for epic generation, `/create-system-architecture` for architecture --- ## 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: the `devforgeai-validate` phase gates, the `settings.json`-registered `.claude/hooks/` scripts, and `.claude/hooks/phase-steps-registry.json` (ADR-076). Behavioral residue: `.claude/rules/core/anti-skip-behavior.md`. Layer 4 (CLI phase-gate) **is wired** as of gh#283: `ideation` is registered in `phase_state.py` `WORKFLOW_SCHEMAS`, and Phase 00 + every phase file call `phase-init` / `phase-check` / `phase-record` / `phase-complete`. The active boundary enforcer is **`pre-phase-complete-boundary-check.sh`** (PreToolUse `exit 2` when a BLOCK-policy phase file [phases 01–0