spec-driven-remediationlisted

# Spec-Driven Remediation Apply automated and guided fixes to story, epic, and context files based on structured audit findings from `/validate-stories`. Every step uses Execute-Verify-Record to prevent token optimization bias from skipping phases. **Audit findings are the input. Fixed files are the output. User approval gates every structural change.** **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 parameters from conversation context markers set by `/fix-story` command. See `references/parameter-extraction.md` for the extraction algorithm. ## Command Integration | Context Marker | Set By | Description | |----------------|--------|-------------| | `$FIX_MODE` | /fix-stor