reversa-forward

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/GleisonOliveira/dockerpilot-mcp --skill reversa-forward-gleisonoliveira
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-forward
Source: https://github.com/GleisonOliveira/dockerpilot-mcp/tree/main/.agents/skills/reversa-forward
Command: npx skills add https://github.com/GleisonOliveira/dockerpilot-mcp --skill reversa-forward-gleisonoliveira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When evolving a project with the Reversa forward pipeline, it is hard to know which stage the active feature is in and which agent should run next. This Skill inspects the physical artifacts of the active feature and tells you exactly where you are and what to run next, without writing or modifying any 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, and others) based on the detected stage and any free-form argument passed by the user. - Greenfield and Legacy Support: Detects whether a reverse-engineering extraction exists in _reversa_sdd/ and adapts the pipeline accordingly, creating folders only when absent and never overwriting existing files. - Use Case: You return to a project after a week and cannot remember if the current feature still needs clarification, planning, or coding. Run /reversa-forward and it reports the exact stage, open [DÚVIDA] markers, action progress, and the recommended next command. ## Quick Start Ask the agent to run /reversa-forward to detect the current stage of my active feature and suggest the next step in the pipeline.

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 step of my feature pipeline to run next?▼

Run /reversa-forward. It reads the active feature directory and classifies the stage based on which artifacts exist, such as requirements.md, roadmap.md, and actions.md, then suggests the exact next agent to run.

How does the Reversa forward orchestrator detect the feature stage?▼

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

Can I use the forward pipeline without a legacy reverse extraction?▼

Yes. If `_reversa_sdd/` is missing or empty, the skill operates in greenfield mode, creates the needed folders without writing any files inside them, and the pipeline continues without legacy anchoring.

Does reversa-forward modify my project files?▼

No. It is strictly read-and-route: it never writes to active-requirements.json, never creates feature directories, and never modifies artifacts. The only exceptions are creating absent folders and filling a blank user name in state.json.

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

The skill reports the ambiguity and offers two explicit choices: type CONTINUAR to proceed with the active feature, or NOVA to route the new description to /reversa-requirements. It never decides on its own.