reversa-plan

Translates feature requirements into architectural roadmaps with delta-based planning and validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill bridges the gap between high-level requirements and technical implementation by generating a structured delta-based plan that respects existing architectural constraints.

Core Features & Use Cases

  • Delta-based Planning: Generates technical roadmaps as incremental changes rather than full system rewrites.
  • Context-Aware Analysis: Integrates existing architecture, state machines, and principles to ensure consistency.
  • Artifact Generation: Automatically creates roadmap, investigation, data-delta, and interface documentation.

Quick Start

Invoke the reversa-plan skill to generate a technical roadmap based on the active requirements in the current feature directory.

Frequently Asked Questions about reversa-plan

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

FAQPage Schema
How do I create a technical roadmap from legacy code without a full system rewrite?

Delta-based planning generates technical roadmaps as incremental architectural changes rather than full system rewrites. It calculates the delta against legacy system states, ensuring new features respect existing constraints while producing structured implementation steps.

How does delta analysis work for architectural migrations?

Delta analysis for architectural migrations works by comparing proposed feature requirements against existing state machines and architectural principles. It calculates the technical gap and outputs structured documentation including data migrations, interface contracts, and implementation steps.

What is the best way to translate feature requirements into concrete implementation steps?

The best way to translate feature requirements into implementation steps is using a framework that validates changes against established architecture. This bridges high-level requirements and technical execution by generating structured, context-aware roadmaps complete with interface contracts and data migration plans.

Can I generate interface contracts and data migration plans from existing state machines?

Yes, you can generate interface contracts and data migration plans from existing state machines. The planning process validates proposed feature changes against established state machine definitions and automatically produces the required technical design artifacts.

How do I ensure new technical designs respect existing architectural principles?

To ensure new technical designs respect existing architectural principles, validate proposed changes against established constraints during roadmap generation. Context-aware analysis integrates existing architecture and state machines to guarantee consistency across the generated implementation steps.