reversa-plan

Translate legacy requirements into a technical delta roadmap with artifacts.

1|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/stribus/pygerengastos --skill reversa-plan-stribus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-plan
Source: https://github.com/stribus/pygerengastos/tree/main/.agents/skills/reversa-plan
Command: npx skills add https://github.com/stribus/pygerengastos --skill reversa-plan-stribus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates legacy feature requirements into a concrete technical delta roadmap, enabling teams to plan investigations, data deltas, onboarding steps, and interface specifications.

Core Features & Use Cases

  • Automated roadmap generation: Converts a set of requirements into a structured roadmap including data-delta and onboarding tasks.
  • Interface and contract planning: Produces preliminary interface descriptions for external contracts and internal modules.
  • Use Case: When a feature evolves, feed its active requirements and let the tool output a plan with milestones and artifacts.

Quick Start

Provide the active feature requirements and trigger /reversa-plan to generate the initial roadmap.

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 roadmap from legacy feature requirements?

To generate a technical roadmap from legacy requirements, provide the active feature constraints to trigger automated processing that outputs structured investigation, data-delta, and onboarding specifications. This translates existing requirements into a concrete delta roadmap with milestone artifacts.

What is a data-delta specification in forward-planning architecture?

A data-delta specification in forward-planning architecture defines the precise structural changes required between the current and target system states. It is generated alongside investigation and onboarding documents to map the exact data modifications needed for evolving features.

How do I plan interface contracts and onboarding steps for a new feature?

Plan interface contracts and onboarding steps by feeding active feature requirements into a delta roadmap generator, which produces preliminary interface descriptions for external contracts and internal modules alongside a structured onboarding document.

Can I use automated roadmap generation for evolving feature requirements without external dependencies?

Yes, automated roadmap generation for evolving feature requirements operates without external dependencies, directly processing active constraints to output investigation, data-delta, onboarding, and interface specification artifacts.

What is the best way to translate requirements into a delta roadmap with interface specifications?

The best way to translate requirements into a delta roadmap is providing the active feature constraints to an automated planning tool, which outputs a structured roadmap alongside investigation, data-delta, onboarding, and interface contract documents.

When should I avoid using automated delta roadmap generation for architecture planning?

Avoid using automated delta roadmap generation when active feature requirements or constraints are incomplete or undefined, as the process relies on fully specified inputs to produce accurate investigation, data-delta, onboarding, and interface artifacts.