reversa-requirements

Convert feature ideas into traceable requirements.md documents for Reversa workflows.

1.5k|383|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/sandeco/reversa --skill reversa-requirements-sandeco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-requirements
Source: https://github.com/sandeco/reversa/tree/main/agents/reversa-requirements
Command: npx skills add https://github.com/sandeco/reversa --skill reversa-requirements-sandeco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforma uma ideia de feature em um documento de requisitos completo e operacional, ancorado nos artefatos já extraídos do sistema legado pelo Reversa, para que agentes de coding evoluam o software com rastreabilidade e menor risco de quebra.

Core Features & Use Cases

  • Requisitos orientados por contexto: lê .reversa/state.json e arquivos de extração _reversa_sdd/ (ex.: architecture.md, domain.md, inventory.md) para embasar cada exigência em evidências.
  • Orquestração de segurança e qualidade: aplica validações iniciais, respeita ganchos definidos em .reversa/hooks.yml e executa auto-validação iterativa usando quality-template.md.
  • Gestão de fluxo de features (forward): detecta feature anterior em andamento via active-requirements.json e artefatos físicos da pasta da feature, pedindo confirmação ao usuário antes de qualquer escrita; suporta continuar, criar em paralelo ou abandonar.
  • Saída padronizada para execução: gera requirements.md via template .reversa/templates/requirements-template.md, salva em feature-dir com escrita atômica e inclui trilha de planejamento para o próximo skill (/reversa-clarify ou /reversa-plan).

Quick Start

Diga ao agente: "quero levantar requisitos para uma nova feature de autenticação com suporte a login por email e recuperação de senha".

Frequently Asked Questions about reversa-requirements

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

FAQPage Schema
How do I generate traceable requirements for AI coding agents from a feature idea?

To generate traceable requirements for AI coding agents, the system converts a free-form feature idea into a complete requirements.md document, anchoring each specification in extracted legacy artifacts to ensure workflow traceability and lower breakage risk.

What is the best way to base new feature requirements on existing legacy system artifacts?

Basing new feature requirements on legacy artifacts requires reading extracted architecture, domain, and inventory files from the state directory, grounding every operational specification in existing system evidence for lower modernization risk.

How do I manage concurrent feature requirement generation workflows?

Managing concurrent feature requirement workflows involves detecting active tasks via state files and physical directories, prompting the user to confirm whether to continue, run in parallel, or abandon the previous feature before any atomic file writes.

Does requirements generation respect pre and post hooks for quality validation?

Requirements generation respects pre and post hooks defined in configuration files, applying initial validations and iterative auto-validation using quality templates to ensure the operational document passes project quality checks.

How do I standardize AI-ready requirements output for downstream planning steps?

To standardize AI-ready requirements output, the system uses project templates to generate requirements.md with atomic writes, including a planning trail that routes the workflow to the next clarification or planning skill.