reversa-forward

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

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/Helcio-Nogueira/Painel_Inteligente_Hackaton_2026 --skill reversa-forward-helcio-nogueira
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-forward
Source: https://github.com/Helcio-Nogueira/Painel_Inteligente_Hackaton_2026/tree/main/.agents/skills/reversa-forward
Command: npx skills add https://github.com/Helcio-Nogueira/Painel_Inteligente_Hackaton_2026 --skill reversa-forward-helcio-nogueira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When evolving a feature through a multi-stage pipeline (requirements, clarify, plan, to-do, coding), it is easy to lose track of which step comes next. This Skill inspects the actual artifacts on disk and tells you exactly where the active feature stands and which agent to invoke next, without ever writing feature artifacts itself. ## Core Features & Use Cases - Physical stage detection: Reads active-requirements.json and the feature directory to classify the stage as vazio, requirements, plan, coding-em-progresso, or done based on real files, not self-declared metadata. - Routing matrix: Maps each detected stage to the correct next skill (/reversa-requirements, /reversa-clarify, /reversa-plan, /reversa-to-do, /reversa-coding), including handling of [DÚVIDA] markers and paused features. - Greenfield and legacy support: Works whether or not a reverse-engineering extraction exists in _reversa_sdd/, creating empty folders when needed and persisting spec granularity decisions in .reversa/config.toml via atomic writes. - Use Case: You return to a project after a week, type /reversa-forward, and it reports that actions.md has 3 of 8 tasks checked off, then suggests /reversa-coding and waits for your CONTINUAR confirmation. ## Quick Start Type /reversa-forward in your AI agent to detect the current feature stage and get a suggestion for the next pipeline step.

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 comes next in a spec-driven feature pipeline?▼

Run /reversa-forward and it inspects the feature directory for requirements.md, roadmap.md, and actions.md to determine the current stage. It then suggests the next agent, such as /reversa-plan or /reversa-coding, and waits for your confirmation before proceeding.

How does the orchestrator detect the current feature stage?▼

It reads .reversa/active-requirements.json to find the feature directory, then checks which artifact files exist and counts open versus closed checkboxes in actions.md. Detection is based purely on physical files, never on self-declared metadata fields.

Does reversa-forward work on a new project without legacy extraction?▼

Yes, it supports greenfield projects. If the reverse-extraction folder is missing, it creates the empty output and forward folders, prompts you to choose a spec granularity, and continues routing normally without legacy anchoring.

Can reversa-forward modify or create feature artifacts?▼

No, it is strictly read-and-route. It never writes to active-requirements.json, never creates feature directories, and never modifies artifacts, with narrow exceptions for 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 options: type CONTINUAR to keep working on the active feature, or NOVA to route the new description to /reversa-requirements, which handles re-execution policy.