What problem does it solve? When working in a project gated by the requirements-framework, it is easy to lose track of which phase you are in and which command to run next. This Skill resolves that uncertainty by mapping requirement state to the single next step in the phase pipeline. ## Core Features & Use Cases - Phase-to-command mapping: Shows the default 6-node pipeline (Design → Plan → Validate → Build → Review → Ship) and which command satisfies each phase gate, such as /brainstorming, /write-plan, /arch-review, /execute-plan, and /deep-review. - Config-aware routing: Explains that the /req conductor command resolves the project's configured workflow live, so custom phase orders always override the default table. - Transition guidance: Lists common transitions (e.g., after /write-plan flips plan_written, the next phase is validate) plus the build-phase loops /pre-commit and /verification-before-completion. - Use Case: You return to a project after a break and are unsure where you left off. Run req status, consult this index, and learn that the plan_validated gate is open, so the next step is /arch-review. ## Quick Start Ask the assistant what workflow step comes next in this requirements-framework project, or run /req to be routed automatically.
