reversa-plan

Generate roadmap, investigation, data-delta, and onboarding documents from active feature requirements.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It transforms a feature’s requirements into a concrete technical evolution plan expressed as a controlled delta against the legacy system, reducing ambiguity and rework.

Core Features & Use Cases

  • Roadmap generation as a delta: Produces roadmap.md describing architectural, data, and contract changes relative to the existing legacy artifacts.
  • Investigation and alternatives: Creates investigation.md to capture research, evaluated options, and applicable patterns.
  • Data-delta and onboarding: Generates data-delta.md for conceptual model differences and onboarding.md so a human can validate the feature quickly, plus optional interfaces/ contract docs when external touchpoints exist.

Quick Start

Run the reversa-plan skill for the current active feature so it drafts the roadmap, investigation notes, data delta, onboarding steps, and affected external interfaces.

Frequently Asked Questions about reversa-plan

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

FAQPage Schema
How do I turn active requirements into a technical delta for legacy system rebuilding?▼

To turn active requirements into a technical delta, you need a tool that parses requirements and generates a roadmap, investigation notes, and data-delta documents expressing changes relative to existing legacy artifacts.

What documents are needed for forward rebuilding workflow planning?▼

Forward rebuilding workflow planning requires a roadmap, investigation, data-delta, and onboarding documents, plus optional interface contracts, all generated as a delta over the legacy system constraints.

How do I generate a technical roadmap from an active-requirements.json file?▼

Generating a technical roadmap from active-requirements.json involves validating the file, parsing requirements.md, applying before-plan hooks, and emitting artifacts from a roadmap template with documented deltas and risks.

Can I handle requirement doubts or open questions during system design planning?▼

Handling requirement doubts during system design planning is supported by parsing requirements.md files and specifically processing [DÚVIDA] tags to ensure open questions are captured and addressed in the technical delta.

Does generating a data-delta and onboarding plan require reverse-engineered SDD artifacts?▼

Generating a data-delta and onboarding plan strictly requires the solution to be grounded in reverse-engineered SDD artifacts and existing legacy constraints to ensure accurate workflow planning.

What is the best way to plan interface contract changes for external touchpoints?▼

Planning interface contract changes is best handled by generating optional interface contract documents alongside the roadmap and data-delta, ensuring all external touchpoints are documented relative to the legacy system.