documentation

Trace code paths to generate data-flow diagrams, ADRs, and API documentation.

4|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/rbaumier/skills --skill documentation-rbaumier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation
Source: https://github.com/rbaumier/skills/tree/main/documentation
Command: npx skills add https://github.com/rbaumier/skills --skill documentation-rbaumier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates and maintains technical documentation by tracing actual code paths to produce data-flow diagrams, decision records (ADRs), and actionable gotchas, enabling accurate, code-grounded docs even in legacy systems.

Core Features & Use Cases

  • Trace-based documentation: output data-flow diagrams (entry -> transforms -> destination) from code.
  • ADR and architecture artifacts: capture decisions, rationale, and consequences alongside API docs and READMEs.
  • Reverse documentation workflow: derive docs from existing code to surface intent and reduce doc rot.

Quick Start

Run the documentation workflow on your codebase to generate up-to-date diagrams, ADRs, and reference docs from your codebase.

Frequently Asked Questions about documentation

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

FAQPage Schema
How do I generate data-flow diagrams from existing code?

Generate data-flow diagrams by tracing actual code paths to map data from entry points through transformations to destinations. This trace-based approach produces accurate visual documentation directly from your codebase logic.

What is reverse documentation for legacy codebases?

Reverse documentation derives technical docs from existing code to surface intent and reduce doc rot. It analyzes legacy code paths to produce updated architecture guides, ADRs, and reference materials.

Can I generate ADRs and architecture guides automatically?

Yes, generate Architecture Decision Records automatically by capturing decisions, rationale, and consequences alongside API docs and READMEs. It traces code paths to ground architecture artifacts in actual implementation logic.

Does this documentation tool support OpenAPI and Mermaid diagrams?

Yes, it supports OpenAPI and REST and GraphQL API docs, plus Mermaid diagrams for architecture visualization. It generates structured artifacts with citations including file paths for traceable technical claims.

What's the best way to maintain technical docs and prevent doc rot?

Prevent doc rot by running automated documentation workflows that perform doc freshness checks against your codebase. This trace-based approach regenerates up-to-date diagrams and reference docs from actual code paths.