reversa-requirements

To generate complete requirements from a feature idea, the skill converts natural language input into a structured requirements.md document grounded in reverse pipeline artifacts. It reads reversa state, executes mandatory hooks, and populates templates using contextual architecture files.

A reverse pipeline in feature planning extracts context from legacy artifacts to ground new requirements generation. It uses physical artifacts in folders like _reversa_sdd to trace architecture and domain inventory, ensuring new features align with existing systems.

To start feature planning using natural language, provide a free-form sentence describing the desired change. The skill detects active features via physical artifacts, prompts for user decisions if needed, and outputs a requirements.md document with bounded [DÚVIDA] markers.

Yes, you can use YAML frontmatter and agent orchestration for requirements documentation. The skill orchestrates agents by verifying optional and mandatory hooks, detecting active features, and managing the reverse state output folder to ensure accurate documentation.

If there is an active feature during requirements generation, the skill detects it through physical artifacts and halts to request a user decision before writing. This guardrail prevents overwriting existing work and ensures the user confirms the new feature direction.