What problem does it solve? In a multi-phase spec-driven development workflow (PRD, SRS, tech docs, code, tests, review), it is hard to know where each feature stands, which single command to run next, and what is blocking progress. This Skill reads workflow state and answers "what now" with exactly one answer, instead of regenerating documents or code itself. ## Core Features & Use Cases - Status routing (default mode): Reads workflow state and reports each feature's phase, loop count, blockers, and the single next command, prioritizing blocked inputs, edited artifacts, open findings, and gate verdicts. - Blast radius analysis (--blast): Diffs scenario spec hashes against the trace file to show exactly which code, tests, prompts, and gates are impacted by a spec change before any regeneration happens. - Framework self-check (--doctor): Validates the framework itself against data-defined checks (forbidden literals, path reality, gate coverage, cache freshness) and reports pass/fail per file without auto-fixing. - Bug-fix entry point (--fix-bug): Enters the loop mid-chain for bugfixes, enforcing diagnosis-first classification, a failing regression test before any fix, and promotion to SRS when the spec is wrong. - Use Case: After editing a feature's spec file, run the blast mode to see that only UC1's scenarios changed, which implementation and test files are impacted, and which gates flip to stale — so you regenerate only the affected scope. ## Quick Start Ask the assistant to run /sdlc to report where every feature stands and which single command comes next in the development loop.