skills.rest
Markson22
Markson22COMMUNITY
Explore all skills by this author →
GitHub

reversa-writer

Generate per-unit specification folders with requirements.md, design.md, and tasks.md from legacy systems.

Updated Nov 4, 2025
Search Tags:#specifications#legacy-systems#contracts#design-docs#reverse-engineering#unit-organization
One-click install
npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-writer-markson22
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-writer
Source: https://github.com/Markson22/MKV-SYTEM/tree/main/.agents/skills/reversa-writer
Command: npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-writer-markson22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gera especificações executáveis do sistema legado como contratos operacionais, em formato de pasta-por-unit com requirements.md, design.md e tasks.md, para facilitar a reversão e migração.

Core Features & Use Cases

  • Creates a folder-per-unit specification layout that maps legacy components to structured docs.
  • Produces three canonical documents per unit (requirements.md, design.md, tasks.md) for traceability and migration planning.
  • Use Case: For each legacy module, generate a unit folder that captures responsibilities, constraints, and actionable steps for modernization.

Quick Start

Convert a legacy component into a unit by generating the per-unit specification documents.

Frequently Asked Questions about reversa-writer

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

FAQPage Schema
How do I generate executable specifications from legacy systems?▼

Executable specifications from legacy systems are generated as per-unit folder contracts containing requirements.md, design.md, and tasks.md. This structure maps legacy components into traceable documents capturing responsibilities and actionable migration steps.

What is the best way to reverse-engineer a legacy component into a unit spec?▼

The best way to reverse-engineer a legacy component into a unit spec is during the analysis phase by generating a dedicated unit folder. This folder enforces frontmatter-driven identity and contains requirements.md, design.md, and tasks.md for full traceability.

How do I trace legacy code constraints for a migration project?▼

Trace legacy code constraints for migration by generating per-unit specification documents. Each unit folder produces requirements.md, design.md, and tasks.md to capture constraints and actionable modernization steps.

Does this approach include optional resources like scripts and references in the output?▼

Yes, the executable specification output references optional resources like scripts, references, and assets when present. These are organized alongside the canonical requirements.md, design.md, and tasks.md files within the per-unit folder structure.

When should I use a folder-per-unit structure for design docs?▼

Use a folder-per-unit structure for design docs when mapping multiple legacy components to structured specifications. It enforces frontmatter-driven unit identity and produces canonical requirements, design, and tasks documents per module.

Related Skills

Explore More Software Engineering Skills→
ggazzoggazzo

reversa-archaeologist

Analyze legacy codebases module-by-module and extract algorithms, control flows, and data structures.

Community
Advanced
stribusstribus
1

reversa-writer

Generate per-unit requirements.md, design.md, and tasks.md from legacy systems.

Community
Advanced
nobu007nobu007

spec-flow-auto

Automate PRD-to-SPEC workflows generating requirements.md, design.md, and tasks.md.

Community
Advanced
antigravityos187-sketchantigravityos187-sketch

architecture-validation

Detect circular dependencies, coupling issues, and layer violations with jCodemunch.

Community
Advanced