Detects the physical stage of an active feature and routes to the next Reversa pipeline skill.
npx skills add https://github.com/RLuf/fzagent --skill reversa-forward-rluf
Please help me install this Agent Skill. Skill: reversa-forward Source: https://github.com/RLuf/fzagent/tree/main/.agents/skills/reversa-forward Command: npx skills add https://github.com/RLuf/fzagent --skill reversa-forward-rluf
.reversa/active-requirements.json and the feature directory to classify the stage as empty, requirements, plan, coding-in-progress, or done based on real files, not self-declared metadata. - Routing matrix: Suggests the next skill (/reversa-requirements, /reversa-clarify, /reversa-plan, /reversa-to-do, /reversa-coding) based on the detected stage, open [DÚVIDA] markers, and checkbox counts in actions.md. - Greenfield and legacy support: Detects whether a reverse-engineering extraction exists and adapts the pipeline accordingly, including persisting the spec granularity decision in .reversa/config.toml. - Use Case: You return to a project after a week and type "/reversa-forward". The Skill reports that roadmap.md exists but actions.md does not, and suggests running /reversa-to-do next, waiting for your CONTINUAR confirmation. ## Quick Start Type "/reversa-forward" to check the current stage of your active feature and get a suggestion for the next pipeline skill.High-intent search queries and answers about installing and using this skill.
Run /reversa-forward and it inspects the feature directory for physical artifacts like requirements.md, roadmap.md, and actions.md. Based on which files exist and their checkbox states, it suggests the next skill such as /reversa-plan or /reversa-coding.
It reads .reversa/active-requirements.json to find the feature directory, then checks which artifact files exist. Open checkboxes in actions.md indicate coding in progress, while [DÚVIDA] markers in requirements.md indicate clarification is needed.
Yes, the pipeline works in greenfield mode when no reverse extraction exists. The skill creates the output and forward folders if missing and proceeds without legacy anchoring, though decisions will not reference extracted artifacts.
No, it is strictly read-only for feature artifacts and never writes to active-requirements.json or files inside the feature directories. Its only allowed writes are creating missing pipeline folders and persisting the spec granularity decision in config.toml.
The skill reports the ambiguity without deciding for you. It offers two options: type CONTINUAR to proceed with the active feature, or NOVA to route your description to /reversa-requirements for a new feature.
sandecoGenerate requirements.md, design.md, and tasks.md specifications from Reversa state and config artifacts.
Helcio-NogueiraDetects the physical stage of an active feature and routes to the next Reversa pipeline agent.
TestAny-ioReview Low-Level Design documents against PRD, HLD, API contracts, and Guardrails.
softwaresaltOrchestrate the Spec-Driven Development lifecycle from specification through adversarial analysis and operator review.