reversa-forward

A feature pipeline orchestrator determines the next workflow step by reading the active feature state from `.reversa/state.json` and inspecting existing artifacts to resolve the current stage. It then validates inputs and routes to the appropriate forward skill without executing it automatically.

To route to the next forward step in a legacy project, the orchestrator inspects `.reversa/state.json` to resolve output and forward folders. It then evaluates existing artifacts to identify the current feature stage and suggests the next pipeline skill, prompting you to proceed.

Forward feature evolution orchestration is the process of routing a software feature through a pipeline of stages like requirements, planning, and coding. The orchestrator detects the feature's current physical stage and suggests the next agent without running it automatically.

Yes, the routing orchestrator operates on both legacy and greenfield projects. It inspects the project's state file and artifact folders to determine the active feature's current stage and route to the next pipeline step regardless of project age.

No, the forward pipeline orchestrator does not execute the next skill automatically. It validates inputs, determines the appropriate next forward step based on feature artifacts, and prompts the user to proceed manually.

A forward feature orchestrator routes between pipeline stages including requirements, clarify, plan, to-do, audit, quality, and coding. It detects the current stage by inspecting artifacts and directs you to the next appropriate skill in the sequence.