reversa-requirements

Convert free-form feature ideas into requirements.md using reverse-engineering artifacts.

Updated May 16, 2026
One-click install
npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-requirements
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-requirements
Source: https://github.com/ricardops34/rcg-crm/tree/main/.agents/skills/reversa-requirements
Command: npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps convert a free-form feature idea into a structured, complete requirements document by grounding it in the existing reverse-engineering artifacts, so you don’t miss critical business rules or implementation constraints.

Core Features & Use Cases

  • Requirements authoring: Transforms a user’s phrase or paragraph into a full requirements.md covering the feature from the reverse-engineered system.
  • Pipeline integration: Reads .reversa/state.json to discover the correct _reversa_sdd/ and _reversa_forward/ folders and prepares the forward feature directory accordingly.
  • Safety workflow with hooks: Loads .reversa/hooks.yml (when valid) and runs required before-requirements hooks, while listing optional ones for the user.
  • Feature in-progress handling: Detects ongoing features via _reversa/active-requirements.json and physical artifacts (presence/absence of requirements.md, roadmap.md, actions.md) and asks the user whether to continue, create in parallel, or abandon.
  • Context-driven citations: Ensures requirement references point to the relevant _reversa_sdd/<file>#<section> sources in the produced document.

Quick Start

Run /reversa-requirements with a single sentence describing the feature you want to build, such as “Criar um módulo para importar pagamentos bancários e registrar as conciliações no sistema.”

Frequently Asked Questions about reversa-requirements

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

FAQPage Schema
How do I generate a requirements document from a free-form feature idea?

To generate a requirements document from a feature idea, provide a single sentence describing the feature. The system transforms it into a complete requirements.md grounded in reverse-engineering artifacts and contextual citations.

How does feature planning integrate with existing reverse engineering artifacts?

Feature planning integrates with reverse engineering artifacts by reading .reversa/state.json to resolve folders. It grounds new requirements in existing _reversa_sdd/ sources, ensuring citations point to relevant system files.

Do I need a specific pipeline workflow to turn an idea into requirements?

You need the Reversa forward pipeline workflow. The process detects ongoing features via active-requirements.json and physical artifacts, asking whether to continue, create in parallel, or abandon before writing requirements.md.

Can I run custom hooks before generating requirements documentation?

You can run custom hooks before generating requirements by defining them in .reversa/hooks.yml. The system loads this file, executes required before-requirements hooks, and lists optional ones for your review.

What happens if I start requirements authoring while another feature is in progress?

If another feature is in progress, requirements authoring detects it via active-requirements.json and physical stage artifacts. It then asks whether you want to continue the existing feature, create a new one in parallel, or abandon it.

How are contextual citations handled in reverse engineering requirements?

Contextual citations in reverse engineering requirements are handled automatically. The system ensures all requirement references point directly to the relevant _reversa_sdd/<file>#<section> sources within the produced document.