What problem does it solve? Determining the correct next step in a multi-phase feature lifecycle requires reading feature state, lifecycle definitions, and dependency status across governance repositories, which is error-prone when done manually. ## Core Features & Use Cases - Deterministic Routing: Invokes next-ops.py suggest to compute the next phase from feature.yaml and lifecycle.yaml, returning a structured JSON status of unblocked, blocked, or fail. - Dependency Gating: Blocks progression when dependency features have not reached a complete phase, listing each blocker for the user. - Direct Phase Delegation: On an unblocked status, delegates immediately to the appropriate lens-{phase} conductor skill with no extra confirmation prompt. - Use Case: A developer finishes a planning phase and runs /next with a feature ID; the skill checks governance state, confirms dependencies are complete, and hands off to the development phase conductor automatically. ## Quick Start Ask the assistant to run the next step for your feature by providing its feature ID, for example: run /next for feature my-feature-id.
