reversa-forward

Detects the active feature stage in the Reversa forward pipeline and routes to the next agent.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/Ruggery/OCR_Cartorio --skill reversa-forward-ruggery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-forward
Source: https://github.com/Ruggery/OCR_Cartorio/tree/main/.agents/skills/reversa-forward
Command: npx skills add https://github.com/Ruggery/OCR_Cartorio --skill reversa-forward-ruggery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When evolving a project with the Reversa framework, it is hard to know which pipeline step comes next for the active feature. This Skill inspects the physical artifacts in _reversa_forward/ and tells you exactly where you are and which agent to run next, without ever writing or modifying feature artifacts itself. ## Core Features & Use Cases - Stage Detection: Reads .reversa/active-requirements.json and the feature directory to classify the stage as empty, requirements, plan, coding-in-progress, or done based on physical artifacts like requirements.md, roadmap.md, and actions.md checkboxes. - Routing Matrix: Suggests the next agent (/reversa-requirements, /reversa-clarify, /reversa-plan, /reversa-to-do, /reversa-coding, /reversa-sync) based on the detected stage, open [DÚVIDA] markers, and addenda status. - Greenfield and Legacy Support: Detects whether a reverse-engineering extraction exists in _reversa_sdd/ and adapts the pipeline accordingly, including persisting the spec granularity decision in .reversa/config.toml. - Use Case: You return to a project mid-feature and run /reversa-forward; it reports that 3 of 7 actions in actions.md are complete and suggests continuing with /reversa-coding, waiting for your CONTINUAR confirmation. ## Quick Start Run /reversa-forward to detect the current stage of my active feature and tell me which Reversa agent to run next.

Frequently Asked Questions about reversa-forward

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

FAQPage Schema
How do I know which Reversa pipeline step to run next?▼

Run /reversa-forward. It reads .reversa/active-requirements.json and the feature directory, classifies the physical stage from artifacts like requirements.md, roadmap.md, and actions.md, then suggests the next agent and waits for you to type CONTINUAR.

How does reversa-forward detect the feature stage?▼

It inspects physical artifacts only, never self-declared metadata. Missing requirements.md means empty, roadmap.md present means plan stage, and open versus closed checkboxes in actions.md distinguish coding-in-progress from done.

Does reversa-forward work on greenfield projects without legacy extraction?▼

Yes. If _reversa_sdd/ is absent or empty, it operates in greenfield mode, creates the output and forward folders if missing, and prompts you to decide spec granularity, which it persists in .reversa/config.toml.

Can reversa-forward modify or create feature artifacts?▼

No. It is strictly read-and-route: it never writes active-requirements.json, never creates feature directories, and never edits files in _reversa_sdd/ or _reversa_forward/. The only exceptions are creating empty folders and filling a blank user name in state.json.

What happens if I pass a new feature idea while another feature is active?▼

It does not decide for you. It reports the ambiguity and offers two paths: type CONTINUAR to proceed with the active feature's next stage, or NOVA to route the new description to /reversa-requirements, which handles re-execution policy.