reversa-plan

Generates a delta-based technical proposal from requirements for legacy-system planning.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts an active feature’s requirements into a concrete, delta-based technical plan that can be executed safely against a legacy system.

Core Features & Use Cases

  • Requirements-to-roadmap delta planning: Translates requirements.md into roadmap.md as an explicit change-over-legacy proposal.
  • Technical impact & principle verification: Gathers affected context from _reversa_sdd/ artifacts, verifies against principles.md, and records applied conflicts/premises.
  • Generates execution-ready artifacts: Produces investigation.md, data-delta.md, onboarding.md, and per-external-contract documentation in interfaces/<name>.md when applicable.
  • Confidence tagging and uncertainty handling: Uses 🟢/🟡/🔴 for decisions and treats unresolved [DÚVIDA] markers as explicit premises when proceeding.

Quick Start

Type /reversa-plan while an active feature and its requirements.md are present so the skill generates the roadmap, investigation, data delta, onboarding steps, and affected interface contracts.

Frequently Asked Questions about reversa-plan

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

FAQPage Schema
How do I generate a technical plan for legacy system modernization?

To generate a technical plan for legacy system modernization, you translate active feature requirements into a delta-based roadmap that explicitly defines changes over the existing architecture. This approach produces execution-ready artifacts like investigation and data-delta files.

What is a delta-based roadmap in software architecture?

A delta-based roadmap in software architecture is a change-over-legacy proposal that maps the exact differences between current systems and new feature requirements. It isolates architectural and data model migrations into safe, executable steps.

How do I handle unresolved premises and uncertainty during technical planning?

You handle unresolved premises during technical planning by treating explicit markers like DÚVIDA as documented assumptions when proceeding. Confidence levels are tagged using green, yellow, and red indicators to record decisions and applied conflicts.

What artifacts are needed for data model migration and API contract definition?

Artifacts needed for data model migration and API contract definition include investigation files, data-delta documents, onboarding steps, and per-external-contract interface documentation. These are generated atomically from validated feature requirements.

Do I need existing requirements files to start legacy modernization planning?

Yes, you need an active feature and its existing requirements file to start legacy modernization planning. The planning process reads this state and validates it against established principles before generating the roadmap and technical artifacts.