reversa-docs-storyteller

Generate glossario.html, deck.html, and features pages from Reversa Docs specs.

Updated Nov 4, 2025
One-click install
npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-docs-storyteller-markson22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-docs-storyteller
Source: https://github.com/Markson22/MKV-SYTEM/tree/main/.agents/skills/reversa-docs-storyteller
Command: npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-docs-storyteller-markson22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables rapid onboarding by turning project specs into an accessible glossary, a navigable slide deck, and per-feature detail pages, reducing ramp-up time and aligning team understanding.

Core Features & Use Cases

  • Glossary with client-side search to help newcomers understand domain concepts.
  • 6-10 slide deck that communicates project context, architecture, modules, metrics, and decisions.
  • Per-feature pages that explain "How a Feature Works" with examples, mapping to specs in _reversa_sdd and soul.md.
  • Auto-generated outputs glossario.html, deck.html, and features/<slug>.html to accelerate documentation.

Quick Start

Activate with /reversa-docs-storyteller and follow prompts to feed soul.md and _reversa_sdd inputs for glossario.html, deck.html, and feature pages.

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 from markdown documentation?

To generate an interactive glossary from markdown documentation, input your project specs like .reversa/soul.md to auto-generate a glossario.html file with client-side search for domain concepts.

What is the best way to create a navigable slide deck for project onboarding?

Creating a navigable slide deck for project onboarding is best achieved by processing _reversa_sdd feature specs to generate a 6-10 slide deck.html that communicates architecture, modules, and decisions.

How do I generate per-feature detail pages from system specs?

Generate per-feature detail pages from system specs by feeding _reversa_sdd inputs to create features/<slug>.html files that explain how a feature works with examples mapped to soul.md.

Can I automate documentation generation if my soul.md file is missing?

Automating documentation generation handles missing soul.md inputs gracefully, ensuring the process still generates glossary, deck, and per-feature pages without failing the entire workflow.

Does the documentation generator work with frontmatter and templates?

The documentation generator works with frontmatter and templates by obeying the provided structures within _reversa_sdd specs to ensure auto-generated HTML pages match your project's formatting rules.