document-module

Document software module architecture with Mermaid diagrams and Markdown.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/AbsolutSystems/absolutpowers --skill document-module
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: document-module
Source: https://github.com/AbsolutSystems/absolutpowers/tree/main/claude/skills/document-module
Command: npx skills add https://github.com/AbsolutSystems/absolutpowers --skill document-module

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an existing code module into clear architectural documentation, so teams can understand structure, responsibilities, dependencies, and key flows without manually reverse-engineering the codebase.

Core Features & Use Cases

  • Code-scan driven documentation: Analyzes the module’s source files to describe its public API, internal components, and external dependencies.
  • Architecture diagrams: Produces C1, C2, and C3 views plus sequence diagrams to explain how the module fits into the wider system and how its main workflows operate.
  • Dual outputs: Generates a Markdown source-of-truth document for AI usage and a self-contained HTML version for human readers.
  • Use case: Ideal when onboarding a new engineer to an auth, billing, or domain module and you need a reliable architecture overview with traceable evidence from the code.

Quick Start

Ask the skill to document the architecture of the module or folder path you want analyzed, and it will scan the code and generate the module documentation files with diagrams.

Frequently Asked Questions about document-module

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

FAQPage Schema
How do I generate architecture documentation from source code?

Architecture documentation is generated by scanning an existing module's source files to extract its public API, internal components, and external dependencies. This produces Markdown and HTML deliverables with embedded diagrams explaining the structure.

What is the best way to reverse engineer a software module's structure?

Reverse engineering a software module is best done by scanning the codebase to map structure, responsibilities, and key flows. This yields evidence-based architecture diagrams and documentation, avoiding the need to manually trace the codebase.

How do I create Mermaid diagrams for existing code?

To create Mermaid diagrams for existing code, you scan the module to generate C1, C2, and C3 architecture views along with sequence diagrams. These diagrams visually explain how the module fits into the wider system and its main workflows.

Can I document a module's public API and dependencies without reading the entire codebase?

Yes, you can document a module's public API and dependencies without reading the entire codebase by running a code-scan driven analysis. This automatically extracts structural information and external links to create a reliable architecture overview.

Does module documentation work for onboarding engineers to internal systems?

Module documentation works effectively for onboarding engineers to internal systems by providing clear architectural overviews with traceable evidence. It explains module responsibilities and key flows, accelerating understanding of complex domain modules.

What formats are output when documenting module architecture?

When documenting module architecture, the outputs are a Markdown source-of-truth document for AI usage and a self-contained HTML version for human readers. Both formats include the generated Mermaid C1-C3 and sequence diagrams.