reversa-forward

Detect the active feature's pipeline stage from .reversa artifacts and route to the next skill.

1.5k|383|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/sandeco/reversa --skill reversa-forward-sandeco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-forward
Source: https://github.com/sandeco/reversa/tree/main/agents/reversa-forward
Command: npx skills add https://github.com/sandeco/reversa --skill reversa-forward-sandeco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill coordinates the next step of Reversa’s forward evolution pipeline by inspecting the current feature’s physical state in .reversa artifacts, so you can move from requirements to coding without guessing what stage is missing.

Core Features & Use Cases

  • Pipeline stage detection from files: Determines whether the active feature is empty, in requirements, in planning, in coding, or done by checking for the presence and checklist state of specific markdown artifacts.
  • Greedy-free orchestration: Never runs other skills automatically; it always asks the user to confirm by typing CONTINUAR.
  • Greenfield/legacy anchoring: Uses .reversa/state.json to resolve _reversa_sdd and _reversa_forward paths, detects legacy extraction artifacts when available, and creates needed folders in greenfield mode without writing feature files.
  • Routing logic: Suggests the correct next skill (reversa-requirements, reversa-clarify, reversa-plan, reversa-to-do, reversa-coding, reversa-resume) based on stage and any free-text argument provided.

Quick Start

Run /reversa-forward and reply with CONTINUAR to route the pipeline to the appropriate next skill for the currently active feature.

Frequently Asked Questions about reversa-forward

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route a legacy modernization pipeline to the correct development stage?

Pipeline stage detection inspects .reversa/active-requirements.json and markdown artifacts to determine whether a feature is empty, in requirements, planning, coding, or done, ensuring you advance without guessing the missing stage.

What is the best way to manage feature evolution from requirements to coding without skipping steps?

Greedy-free orchestration inspects .reversa artifacts to identify the current feature stage and suggests the next skill, requiring explicit user confirmation via CONTINUAR before advancing to prevent skipping steps.

How do I start a greenfield feature creation workflow using pipeline routing?

For greenfield feature creation, the skill reads .reversa/state.json to resolve forward paths and creates required folders without writing feature artifacts, then routes to the appropriate next skill after user confirmation.

Does the pipeline routing automatically execute the next skill after detecting the stage?

No, pipeline routing never executes subsequent skills automatically; it always prompts the user to type CONTINUAR to confirm and advance the feature to the suggested next skill in the workflow.

What limitations exist when using pipeline routing for requirements planning?

A key limitation is that pipeline routing depends on .reversa/state.json and active-requirements.json artifacts to resolve paths and detect stages; without these files, it cannot determine the correct next skill to suggest.