What problem does it solve? When evolving a project with the Reversa forward pipeline, it is hard to know which step comes next: requirements, clarification, planning, task breakdown, coding, or sync. This Skill inspects the actual artifacts on disk and tells you exactly where the active feature stands and which skill to run next, without ever writing or modifying feature artifacts itself. ## Core Features & Use Cases - Physical 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 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, /reversa-sync) and handles ambiguous cases like a new idea passed while a feature is active. - Greenfield and legacy support: Detects whether a reverse-engineering extraction exists in _reversa_sdd/, creates the folder structure when absent, and persists the spec granularity decision atomically in .reversa/config.toml. - Use Case: You return to a project after a week, run /reversa-forward, and it reports that 3 of 7 actions in actions.md are complete, suggesting /reversa-coding as the next step and waiting for your CONTINUAR confirmation. ## Quick Start Run "/reversa-forward" in your project to detect the current feature stage and get a suggestion for the next Reversa pipeline skill.
