Verified:GitHub

reversa-writer

Generate requirements, design, and task files from legacy knowledge.

Updated Mar 31, 2026

Search Tags:#requirements #spec generation #task planning #design documentation #legacy modernization #reverse engineering #agent workflows

Ready to run

npx skills add https://github.com/afsjr/secretaria_escola_csm --skill reversa-writer-afsjr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reversa-writer
Source: https://github.com/afsjr/secretaria_escola_csm/tree/main/.agents/skills/reversa-writer
Command: npx skills add https://github.com/afsjr/secretaria_escola_csm --skill reversa-writer-afsjr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill converts extracted legacy-knowledge into formal, traceable specifications that enable reliable reimplementation by other agents, without relying on the original source code.

Core Features & Use Cases

Generates operational specs: Produces requirements, design, and tasks in a folder-per-unit layout aligned to the configured granularity.
Creates consistent unit artifacts: Always generates requirements.md, design.md, and tasks.md for each unit, using the repository’s templates.
Supports reverse-engineering planning: Guides the generation process step-by-step, including resolving doc_level, doc_language, and spec scope from Reversa state/config.

Quick Start

Run the reversa-writer skill to generate unit specifications for the legacy system according to the output folder and granularity settings already defined in .reversa/state.json and .reversa/config.toml.

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 extracted legacy system knowledge?▼

Executable specifications for legacy knowledge are generated by reading Reversa state and config to resolve output paths, granularity, and language. The tool then produces folder-per-unit structures containing canonical requirements, design, and tasks files without overwriting existing outputs.

What is reverse engineering specification generation for legacy modernization?▼

Reverse engineering specification generation converts extracted legacy knowledge into formal, traceable specifications for legacy modernization. It enables reliable reimplementation by agents without needing the original source code, producing structured requirements, design, and task documentation.

How do I plan a reverse engineering documentation workflow for multiple modules?▼

Planning a reverse engineering documentation workflow involves resolving `doc_level`, `doc_language`, and spec scope from Reversa state. The process produces an ordered, user-confirmed generation plan covering modules, endpoints, contracts, use-cases, or configured custom folders.

Can I generate design documentation without overwriting existing spec files?▼

Yes, generating design documentation without overwriting existing spec files is supported. The skill explicitly preserves existing outputs and only generates missing `requirements.md`, `design.md`, and `tasks.md` files using the repository's configured templates.

Do I need a Reversa config file to generate task planning and requirements specs?▼

Yes, a Reversa config file is required to generate task planning and requirements specs. The skill reads `.reversa/state.json` and `.reversa/config.toml` to determine output paths, granularity, language, and spec scope before generating any artifacts.