reversa-docs-storyteller

Transform project specs into glossaries, slide decks, and feature pages.

1|Updated Nov 20, 2025

Search Tags:#documentation #storytelling #onboarding #glossary #deck #feature-pages

Ready to run

npx skills add https://github.com/stribus/pygerengastos --skill reversa-docs-storyteller-stribus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reversa-docs-storyteller
Source: https://github.com/stribus/pygerengastos/tree/main/.agents/skills/reversa-docs-storyteller
Command: npx skills add https://github.com/stribus/pygerengastos --skill reversa-docs-storyteller-stribus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms project specs and narrative requirements into a turnkey onboarding package, including an interactive glossary, a navigable slide deck, and per-feature implementation pages.

Core Features & Use Cases

Interactive glossary with client-side search for terms and definitions derived from the soul and specs.
Navigable slide deck (6 to 10 slides) that communicates project purposes, architecture, modules, metrics, and decisions.
Per-feature pages ("How a Feature Works") detailing individual capabilities with cross-links to the glossary and deck.
Outputs consolidated in .reversa/documentation: glossario.html, deck.html, and features/<slug>.html along with soul.json and features-index.json.

Quick Start

Activate with /reversa-docs-storyteller to generate glossario.html, deck.html, and feature pages from soul.md and _reversa_sdd specs.

Frequently Asked Questions about reversa-docs-storyteller

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

FAQPage Schema

How do I generate an interactive glossary and onboarding deck from project specs?▼

To generate an interactive glossary and onboarding deck from project specs, use a template-driven configuration that transforms soul and _reversa_sdd specs into client-side searchable HTML glossaries and navigable slide decks.

What is the best way to create feature detail pages for technical documentation?▼

The best way to create feature detail pages is to render individual capability pages from project specs, cross-linking them directly to your navigable deck and glossary to ensure cohesive onboarding documentation.

Can I generate a 6 to 10 slide deck directly from my project's soul and spec files?▼

Yes, you can generate a 6 to 10 slide deck directly from soul and _reversa_sdd spec files. The output communicates project purposes, architecture, modules, metrics, and decisions via deck templating.

Do I need specific spec formats to produce glossary and feature pages?▼

You need soul and _reversa_sdd spec formats to produce glossary and feature pages. The system parses these inputs to derive terms, definitions, and per-feature implementation details for rendering.

What output files are generated for the reversa documentation onboarding package?▼

The generated onboarding package outputs consolidated files in the .reversa/documentation directory, including glossario.html, deck.html, features/<slug>.html, soul.json, and features-index.json.

Are there limitations when deriving a cohesive narrative from technical specs?▼

A limitation when deriving a cohesive narrative is that the output strictly requires template-driven configuration from soul and _reversa_sdd specs, meaning undocumented features will not appear in the glossary or deck.