spec-driven-devlisted

# Spec-Driven Development Implement user stories using strict TDD (Red-Green-Refactor) while enforcing all 6 context file constraints. **Context files are THE LAW:** tech-stack.md, source-tree/, dependencies.md, coding-standards.md, architecture-constraints.md, anti-patterns.md **If ambiguous or conflicts detected: HALT and use AskUserQuestion** --- ## 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 State 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`. --- ## Parameter Extraction Extract story ID from conversation context. See `references/parameter-extraction.md` for the extraction algorithm. ## Command Integration | Context Marker | Set By | Description | |----------------|--------|-------------| | `$STORY_ID` | /dev, /resume-dev | Story identifier (STORY-NNN) | | `$FORCE_FLAG` | /dev | Bypass dependency checks | | `$REMEDIATION_MODE`