reversa-forward

Pipeline orchestration for feature management is handled by inspecting the _reversa_forward directory to detect the current stage and recommending the next skill without executing it. It coordinates routing decisions across projects using the Reversa framework.

The Reversa forward pipeline is a feature progression cycle that detects the current stage by inspecting artifacts in the _reversa_forward directory. It then suggests the next skill in the cycle, such as requirements, clarify, plan, to-do, audit, quality, or coding.

Safe routing is enforced by recommending the next skill in the pipeline without executing it automatically. Users must explicitly confirm by typing CONTINUE to proceed, ensuring manual oversight over feature progression.

The Reversa framework is required because the orchestration operates across projects using it. It relies on the _reversa_forward directory and its artifacts to detect the feature stage and align teams on progression.

Stage skipping is not supported by the orchestration logic. It detects the current feature stage and recommends the sequential next skill in the cycle, requiring explicit user confirmation to advance.

The pipeline recommends the next skill rather than executing it to enforce safe routing decisions. This design centralizes guidance and requires explicit user confirmation to proceed, preventing unintended automated actions.