reversa-docs-storyteller

Generate narrative documentation artifacts from Reversa specs.

1|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-docs-storyteller-rdinda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-docs-storyteller
Source: https://github.com/Rdinda/FMA_Pontos/tree/main/.agents/skills/reversa-docs-storyteller
Command: npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-docs-storyteller-rdinda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns technical specs and project concepts into human-friendly narrative documentation so new contributors can understand the system quickly through clear pages and an interactive deck.

Core Features & Use Cases

  • Interactive Glossary: Generates an HTML glossary with client-side search to help users learn key concepts (from soul.json) without digging through raw specs.
  • Navigable Story Deck: Produces a 6 to 10 slide deck (or fewer when inputs are missing) to provide an onboarding path from purpose to architecture to feature highlights.
  • Feature How a Feature Works Pages: Creates one detailed documentation page per selected feature spec to explain requirements, context, and implementation details in a consistent format.

Quick Start

Activate reversa-docs-storyteller to generate glossary, deck, and per-feature pages from the existing Reversa docs inputs.

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 documentation from technical specs for onboarding?

Generate interactive documentation by reading project specs to produce navigable HTML glossaries, slide decks, and feature pages. This onboarding documentation transforms raw technical concepts into human-friendly narrative artifacts for new contributors.

What is the best way to create a navigable slide deck from feature documentation?

Creating a navigable slide deck from feature documentation involves parsing specs to generate a 6 to 10 slide onboarding deck. It guides users from purpose to architecture to feature highlights, scaling down gracefully when inputs are missing.

Can I generate an interactive HTML glossary from project concepts without manual coding?

Generate an interactive HTML glossary from project concepts automatically to provide client-side search. This allows new users to learn key definitions quickly without digging through raw technical specs or manually coding web pages.

How do I create per-feature documentation pages for a multi-feature system?

Create per-feature documentation pages by deriving feature specs into individual "How a Feature Works" pages. This process extracts requirements, context, and implementation details into a consistent format for multi-feature system onboarding.

Does documentation generation work with partial or missing spec inputs?

Documentation generation works with partial or missing inputs by scaling outputs down gracefully. In greenfield scenarios with incomplete specs, it still produces navigable glossary and deck artifacts by deriving available information from existing configuration files.

What configuration files are required to generate navigable documentation artifacts?

Required configuration files include .reversa/state.json and .reversa/documentation/.config.json. These inputs are parsed to derive soul.json and features-index.json, which drive the generation of all documentation outputs strictly under the documentation directory.