skills.rest
Pabloprogramador23
Pabloprogramador23COMMUNITY
Explore all skills by this author →
GitHub

reversa-plan

Translate feature requirements into technical delta artifacts for legacy systems.

Updated Jun 6, 2026
Search Tags:#planning#requirements#roadmap#legacy#reversa-plan#technical-delta
One-click install
npx skills add https://github.com/Pabloprogramador23/loja --skill reversa-plan-pabloprogramador23
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-plan
Source: https://github.com/Pabloprogramador23/loja/tree/main/.agents/skills/reversa-plan
Command: npx skills add https://github.com/Pabloprogramador23/loja --skill reversa-plan-pabloprogramador23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Este Skill converte requisitos de uma feature em um delta técnico concreto, facilitando a passagem do backlog para o desenho da solução.

Core Features & Use Cases

  • Gera roadmap técnico, investigação, data-delta, onboarding e interfaces da feature ativa.
  • Transforma requisitos legados em artefatos executáveis e planos de migração.
  • Fornece orientações e gatilhos para aplicação de princípios de engenharia reversa e validação de viabilidade.

Quick Start

Forneça o requirements.md da feature ativa e o skill gerará o delta técnico inicial.

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 delta for legacy systems?▼

To translate feature requirements into a technical delta, provide a requirements.md file to generate a concrete plan specifying data models, interfaces, and migration artifacts aligned with legacy system constraints.

What is a delta-driven plan for software migration?▼

A delta-driven plan converts active feature requirements into executable artifacts like roadmap.md, investigation.md, and onboarding.md, specifying the exact technical changes needed across legacy interfaces and data models.

How do I generate a technical roadmap from feature requirements?▼

You generate a technical roadmap by inputting feature requirements, which produces a structured roadmap.md alongside investigation and data-delta artifacts to guide forward planning workflows.

Can I use this for onboarding and interface definitions across legacy systems?▼

Yes, you can use it for onboarding and interface definitions by processing feature requirements to generate onboarding.md and interface definitions tailored to legacy system constraints and data models.

What is the best way to plan a feature migration across legacy codebases?▼

The best way to plan a feature migration is using a delta-driven approach that applies reverse engineering principles to validate feasibility and output structured investigation and data-delta artifacts.

Do I need a requirements.md file to start generating the technical delta?▼

Yes, you need to provide a requirements.md file for the active feature, which serves as the input to generate the initial technical delta and subsequent roadmap artifacts.

Related Skills

Explore More Software Engineering Skills→
ricardops34ricardops34

reversa-plan

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

Community
Intermediate
stribusstribus
1

reversa-plan

Translate legacy requirements into a technical delta roadmap with artifacts.

Community
Advanced
darelabs-techdarelabs-tech

dare-reverse

Generate documentation, flowcharts, and domain models from DARE CLI reverse-engineering artifacts.

Official
Advanced
afsjrafsjr

reversa-plan

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

Community
Advanced