reversa-docs-storyteller

Convert RCG specifications and soul into interactive HTML onboarding documentation.

Updated May 16, 2026
One-click install
npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-docs-storyteller
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-docs-storyteller
Source: https://github.com/ricardops34/rcg-crm/tree/main/.agents/skills/reversa-docs-storyteller
Command: npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-docs-storyteller

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Transforms engineering specs and project “soul” into a clear, navigable documentation experience that helps new contributors understand the system quickly.

Core Features & Use Cases

  • Glossary generation with interactive client-side search: Creates a glossary from soul concepts to make terminology discoverable without server requests.
  • Navigable slide deck (6 to 10 slides) for onboarding: Produces a structured overview that adapts to available pages and existing documentation depth.
  • Per-feature “How a Feature Works” pages: Generates one HTML page per selected spec to explain each feature’s intent and structure in a consistent format.

Quick Start

Use the reversa-docs-storyteller skill to generate glossario.html, deck.html, and the feature pages from your existing _reversa_sdd/ specs and .reversa/soul.md.

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 interactive onboarding documentation from engineering specs?▼

Generate interactive onboarding documentation by converting system specifications into a searchable glossary, navigable slide deck, and per-feature HTML pages. This approach transforms engineering specs into navigable docs that help new contributors understand the system quickly.

What is the best way to create a searchable glossary from project specifications?▼

Create a searchable glossary from project specifications by extracting core concepts and rendering them into an HTML page with interactive client-side search. This makes terminology discoverable without requiring any server requests.

How do I build a slide deck for engineering onboarding from existing specs?▼

Build an onboarding slide deck by processing system specifications to produce a structured navigable overview of 6 to 10 slides. The deck adapts its structure based on available pages and existing documentation depth.

Does this documentation generation workflow require specific configuration files?▼

This documentation generation workflow requires reading .reversa/state.json and .reversa/documentation/.config.json. It uses these configuration files to generate data assets and applies safe fallbacks when inputs are missing.

Can I generate per-feature HTML pages to explain how a feature works?▼

Generate per-feature HTML pages by selecting specifications and rendering one page per feature. Each page explains the feature's intent and structure in a consistent format for onboarding and discovery.

What happens to feature storytelling outputs when input specs are missing?▼

When input specs are missing, feature storytelling outputs use safe fallbacks provided by templates. The process still writes outputs under the documentation directory, ensuring onboarding assets render without failing.