reversa-forward

Pipeline routing works by reading .reversa/state.json to determine if a feature is active and which stage it is in, then routing the user to the correct next skill without executing it automatically.

Route to the next stage by inspecting the state file to determine the current stage and selecting the correct next step. It supports both legacy and greenfield projects, ensuring consistent workflow guidance through a CONTINUE prompt.

No, the pipeline orchestrator never executes the next skill automatically. It only routes the user to the appropriate next step and ends with a CONTINUE prompt, keeping the user in control of execution.

Yes, pipeline routing supports both legacy and greenfield projects. The orchestrator inspects the feature state to ensure consistent workflow guidance and clear routing for any project context.

The orchestrator routes to requirements, clarify, plan, to-do, audit, quality, and coding stages. It selects the destination by checking if the feature state is vazio, requirements, plan, coding-em-progresso, or done.

The orchestrator stops at a CONTINUE prompt because it only routes users to the next skill and never executes it automatically. This design ensures you maintain manual control over workflow progression.