reversa-forward

Detect the current Reversa feature stage and suggest the next pipeline agent.

Updated May 16, 2026
One-click install
npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-forward
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-forward
Source: https://github.com/ricardops34/rcg-crm/tree/main/.agents/skills/reversa-forward
Command: npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-forward

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ele elimina a incerteza de “em que etapa estamos” e qual deve ser o próximo passo ao evoluir uma feature no pipeline forward do Reversa, guiando a continuidade do fluxo com base no estado físico dos artefatos.

Core Features & Use Cases

  • Detecta o estágio físico da feature ativa: identifica se a feature está vazia, em requirements, plan, coding-em-progresso ou done a partir dos arquivos em .reversa/ e da pasta da feature.
  • Orquestra o próximo skill recomendado: sugere o agente correto do ciclo (requirements, clarify, plan, to-do, audit, quality, coding) sem executar automações extras.
  • Lida com legado e greenfield: ancora em _reversa_sdd/ quando existe extração reversa, ou prepara o modo greenfield com criação apenas de pastas necessárias.
  • Preserva segurança e controle do usuário: nunca roda o próximo skill automaticamente; sempre pede para o usuário digitar CONTINUAR.

Quick Start

Digite /reversa-forward para o orquestrador detectar o estado atual da feature e sugerir o próximo skill apropriado.

Frequently Asked Questions about reversa-forward

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

FAQPage Schema
How do I determine the current physical stage of a feature in a coding workflow?

To determine the current physical stage of a feature in a coding workflow, this skill analyzes the markdown artifacts and configuration files within the project's state directories. It identifies whether the feature is at the requirements, plan, coding, or completion stage based on physical files.

What is the best way to orchestrate the next agent in a feature evolution pipeline?

The best way to orchestrate the next agent in a feature evolution pipeline is by using an automated routing mechanism that reads the current project state and suggests the appropriate downstream skill. This ensures the correct agent is selected without executing unintended automations.

How do I route feature development from zero in a greenfield project?

To route feature development from zero in a greenfield project, the orchestrator prepares the necessary folder structures and anchors the initial stage. It detects the empty feature state and suggests the first appropriate agent to begin the workflow.

Does the pipeline orchestrator execute downstream skills automatically?

No, the pipeline orchestrator does not execute downstream skills automatically. It outputs a next-step suggestion and requires explicit user confirmation to proceed, ensuring the user retains full control and safety over the coding workflow.

Can I use agent routing with legacy codebases that have reverse engineering artifacts?

Yes, you can use agent routing with legacy codebases. The orchestrator anchors its stage detection to existing reverse engineering extraction folders, allowing it to seamlessly continue the feature evolution workflow from the current legacy artifacts.