skills.rest
AlexandrePontesjr
AlexandrePontesjrCOMMUNITY
Explore all skills by this author →
GitHub

reversa-plan

Translate active feature requirements into a technical delta roadmap over legacy systems.

Updated May 5, 2026
Search Tags:#interfaces#requirements#roadmap#technical planning#architecture migration#Reversa#delta design
One-click install
npx skills add https://github.com/AlexandrePontesjr/calculadora-Juridica --skill reversa-plan-alexandrepontesjr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-plan
Source: https://github.com/AlexandrePontesjr/calculadora-Juridica/tree/main/.agents/skills/reversa-plan
Command: npx skills add https://github.com/AlexandrePontesjr/calculadora-Juridica --skill reversa-plan-alexandrepontesjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an active feature’s requirements into a concrete, legible technical plan that shows exactly what changes as a delta over the existing legacy system.

Core Features & Use Cases

  • Requirements-to-roadmap translation: Converts the active requirements.md into a step-by-step engineering plan that includes decisions, risks, and a “criteria de pronto” (done criteria).
  • Legacy impact mapping: Collects and records which _reversa_sdd/* and other Reversa artifacts will be touched, so later coding can reference impact precisely.
  • Contract/interface definition when needed: Generates feature-dir/interfaces/<nome>.md files for any external contracts affected by the change.

Quick Start

Ask the Skill to generate the roadmap and related investigation, data-delta, onboarding, and interface files for the current active feature.

Frequently Asked Questions about reversa-plan

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

FAQPage Schema
How do I translate feature requirements into a technical migration roadmap?▼

Translating feature requirements into a technical migration roadmap involves mapping active requirements as a delta over existing legacy systems. This process generates a step-by-step engineering plan with decisions, risks, and done criteria.

What is technical delta design in architecture migration planning?▼

Technical delta design in architecture migration planning defines exact changes needed over an existing legacy system. It records impacted artifacts and generates interface contracts to ensure later coding references precise impact points.

How do I generate interface contracts from active feature requirements?▼

Generating interface contracts from active feature requirements involves analyzing external contracts affected by planned changes. This planning phase produces specific interface definition files documenting required external interactions.

Can I plan an investigation and data-delta roadmap for legacy system features?▼

Yes, you can plan an investigation and data-delta roadmap for legacy system features. The planning process outputs detailed investigation notes and data-delta files alongside the main roadmap to guide implementation over existing architecture.

What do I need to start technical planning for a feature delta roadmap?▼

Starting technical planning for a feature delta roadmap requires active requirements files and existing legacy state files. The process reads these inputs, validates marked doubts, applies hooks, and emits the roadmap.

Related Skills

Explore More Software Engineering Skills→
afsjrafsjr

reversa-plan

Generate a technical roadmap as a delta over legacy architecture from active requirements.

Community
Advanced
stribusstribus
1

reversa-plan

Translate legacy requirements into a technical delta roadmap with artifacts.

Community
Advanced
ricardops34ricardops34

reversa-plan

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

Community
Intermediate
nksethnkseth

legacy-modernizer

Document legacy system architecture and define an incremental migration strategy.

Community
Advanced