What problem does it solve? When evolving a feature through a multi-stage spec-driven pipeline (requirements, clarify, plan, to-do, coding), it is easy to lose track of where the work actually stands. This Skill inspects the real artifacts on disk and tells you exactly which stage the active feature is in and which agent should run next, without ever writing feature artifacts itself. ## Core Features & Use Cases - Physical stage detection: Reads .reversa/active-requirements.json and the feature directory to classify the stage as vazio, requirements, plan, coding-em-progresso, or done based on actual files and checkbox states, never 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) and handles free-text arguments, paused features, and ambiguity between continuing or starting a new feature. - Greenfield and legacy support: Detects whether a reverse-engineering extraction exists, creates _reversa_sdd/ and _reversa_forward/ folders when absent, and persists the spec granularity decision atomically in .reversa/config.toml. - Use Case: You return to a project after a week, type "/reversa-forward", and it reports that actions.md has 3 of 8 actions checked off, then suggests /reversa-coding and waits for your CONTINUAR confirmation. ## Quick Start Type "/reversa-forward" to have the assistant inspect the current feature state and suggest the next pipeline step.
