reversa-forward

Detect the current Reversa pipeline stage from local artifacts and propose the next agent.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you move an ongoing Reversa feature forward by detecting the current physical stage of the feature artifacts and then routing you to the correct next agent in the pipeline.

Core Features & Use Cases

  • Pipeline orchestration: Detects whether the active feature is in requirements, plan, coding-in-progress, or done, and suggests the next compatible skill.
  • Legacy vs greenfield handling: Anchors decisions to existing extraction artifacts when detected; otherwise prepares the required Reversa folders in a non-invasive way.
  • Non-writing behavior: Reads Reversa state/config and only routes to the next skill, preventing accidental artifact overwrites.

Quick Start

Run reversa-forward by typing /reversa-forward or iniciar evolução to identify the current stage and get the next recommended command.

Frequently Asked Questions about reversa-forward

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

FAQPage Schema
How do I route the next pipeline step for an active feature evolution?

Pipeline routing for feature evolution detects the current physical stage from local artifacts and proposes the correct next agent. It reads state configuration to determine whether the feature is in requirements, plan, or coding, then suggests the compatible next skill.

What is state detection in requirements-to-code pipeline orchestration?

State detection in pipeline orchestration identifies the current phase of a feature by reading local pipeline artifacts and state files. It anchors decisions to existing extraction artifacts for legacy projects or prepares required folders for greenfield setups.

How do I continue a feature pipeline from requirements through coding without overwriting artifacts?

Continuing a feature pipeline without overwriting artifacts requires a non-writing routing skill that reads state configuration and only suggests the next step. It prevents accidental artifact overwrites by ending with a prompt for you to manually continue.

Can I use pipeline state detection for both legacy and greenfield project routing?

Yes, pipeline state detection supports both legacy and greenfield project routing. It anchors routing decisions to existing extraction artifacts when detected for legacy code, and non-invasively prepares required folders when no artifacts are found for greenfield features.

Does the pipeline routing skill execute the next agent automatically?

No, the pipeline routing skill does not execute the next agent automatically. It identifies the current stage, optionally guides the specs organization menu, and ends by prompting you to continue without running the next skill itself.