reversa-docs-storyteller

To generate interactive documentation from legacy feature specs, the process reads .reversa state and soul files to produce navigable HTML pages. This Skill transforms reverse-engineered specifications into a glossary, slide deck, and per-feature pages for onboarding.

The best way to create an onboarding deck and glossary for a legacy codebase is deriving content from project soul and feature requirements. This generates a 6 to 10 slide navigable deck and a client-side searchable glossary with deep links.

Yes, you need .reversa/soul.md and _reversa_sdd requirement files to generate feature spec HTML pages. The process reads these files along with state.json and documentation config to derive the features index and output HTML documentation.

Interactive documentation generation handles non-destructive backup behavior by writing only to the .reversa/documentation/ directory. It preserves existing project files while safely generating new glossary, deck, and feature HTML artifacts.

Yes, you can use this documentation generation process for both AI coding agents and human developers. It produces an operational docs set with navigable HTML pages and a searchable glossary that serves human onboarding and AI traceability.

A limitation when generating per-feature HTML pages is that content is constrained to available spec data, causing adaptive slide inclusion. It strictly writes to .reversa/documentation/ and cannot modify external project files.