skills.rest
stribus
stribusCOMMUNITY
Explore all skills by this author →
GitHub

reversa-writer

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

1|Updated Nov 20, 2025
Search Tags:#specification#requirements#task-tracking#design-docs#reverse-engineering#legacy-system#unit-folder
One-click install
npx skills add https://github.com/stribus/pygerengastos --skill reversa-writer-stribus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-writer
Source: https://github.com/stribus/pygerengastos/tree/main/.agents/skills/reversa-writer
Command: npx skills add https://github.com/stribus/pygerengastos --skill reversa-writer-stribus

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. Use na fase de engenharia reversa para facilitar a reconstrução e migração de sistemas legados.

Core Features & Use Cases

  • Estrutura de pasta por unidade com os arquivos requirements.md, design.md e tasks.md, mantendo rastreabilidade da origem.
  • Templates padronizados para documentação de requisitos, design técnico e atividades de implementação.
  • Use case: analise um sistema legado e gere a árvore de especificações pronta para validação, revisão e migração incremental.

Quick Start

Execute esta skill para gerar pastas de especificação por unidade a partir do contexto de engenharia reversa.

Frequently Asked Questions about reversa-writer

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

FAQPage Schema
How do I reverse engineer legacy system specifications into unit folders?▼

Reverse engineering legacy systems into unit folders transforms artifacts into per-unit directories containing requirements.md, design.md, and tasks.md files. This structure maintains traceable provenance and clear task mappings for incremental migration.

What is the best way to document legacy code for incremental migration?▼

Documenting legacy code for incremental migration works best by generating executable specifications as operational contracts. This delivers standardized templates for requirements, technical design, and implementation tasks mapped to individual system units.

Can I generate task tracking documents from existing design docs?▼

You can generate task tracking documents from existing design docs by processing legacy artifacts through the reverse-engineering workflow. It outputs tasks.md files alongside requirements and design templates, ensuring clear task mappings for reimplementation.

Does this reverse-engineering workflow support traceable provenance for requirements?▼

The reverse-engineering workflow supports traceable provenance for requirements by transforming legacy artifacts into design-ready documents. It maintains strict traceability back to the original system source within each unit folder.

When do I need to create executable specifications for legacy systems?▼

You need to create executable specifications for legacy systems when preparing for validation, review, and incremental migration. This process converts opaque legacy artifacts into structured, design-ready operational contracts.

Related Skills

Explore More Software Engineering Skills→
AlexandrePontesjrAlexandrePontesjr

reversa-writer

Generate requirements, design, and tasks specifications from Reversa state and config files.

Community
Advanced
Pabloprogramador23Pabloprogramador23

reversa-writer

Generate requirements.md, design.md, and tasks.md per legacy unit.

Community
Advanced
bartoszwarzochabartoszwarzocha

openspec-workflow

Automate OpenSpec change request creation, tracking, and closing workflows.

Community
Advanced
cmetechcmetech

excavate-source-analysis

Decompose source code into per-unit behavioral analyses with provenance.

Community
Advanced