reversa-forward

To determine the current stage of a feature in a forward pipeline, an orchestrator reads state.json and active-requirements.json to route users to the appropriate next skill without executing artifacts.

State-aware routing for feature management workflows reads forward state to recommend the next appropriate agent, ensuring smooth pipeline progress by prompting for continuation rather than automatic execution.

To route a paused feature to the next recommended skill, the orchestrator evaluates the active feature state and suggests requirements, clarify, plan, to-do, audit, quality, or coding skills based on current progress.

The forward pipeline orchestrator supports legacy projects by working with both legacy reverse state and new features, guiding transitions and routing to the appropriate next skill without performing actions.

You cannot automatically execute the next skill in the pipeline after routing, because safe orchestration design always prompts for explicit continuation before proceeding to the recommended agent.

Your feature workflow needs state.json and active-requirements.json because the routing orchestrator reads these files to detect the active feature stage and determine the recommended next skill to run.