Forge-Documentation-Generation

Generates draft architecture documentation and glossary entries from codebase knowledge graphs.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Nealsch/ForgeOS --skill forge-documentation-generation-nealsch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Forge-Documentation-Generation
Source: https://github.com/Nealsch/ForgeOS/tree/main/Framework/05-Skills/07-Documentation%20and%20Knowledge/Forge-Documentation-Generation
Command: npx skills add https://github.com/Nealsch/ForgeOS --skill forge-documentation-generation-nealsch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Undocumented or stale codebases force engineers to reverse-engineer architecture by hand. This Skill converts the knowledge graph and analysis report produced by codebase analysis tooling into draft documentation, so architecture overviews, component summaries, and data-flow descriptions no longer have to be written from scratch. ## Core Features & Use Cases - Draft Architecture Documentation: Generates architecture overviews from community/structure data, component summaries from node clusters, and data-flow descriptions from edge relations. - Glossary Candidate Generation: Proposes glossary entries for high-degree ("god node") and surprising concepts found in the analysis report. - Confidence-Labelled Output: Preserves EXTRACTED / INFERRED / AMBIGUOUS confidence labels in generated text and checks graph freshness before documenting current state. - Use Case: When onboarding an unfamiliar repository, run codebase analysis first, then use this Skill to produce the documentation section of an Architecture Assessment for the Technical Writer to review and publish. ## Quick Start Use the Forge-Documentation-Generation skill to generate draft architecture documentation and glossary candidates from the knowledge graph and analysis report for this repository.

Frequently Asked Questions about Forge-Documentation-Generation

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

FAQPage Schema
How do I generate architecture documentation from a codebase automatically?▼

Run codebase analysis tooling to produce a knowledge graph and analysis report, then apply this Skill to convert community structures, node clusters, and edge relations into draft architecture overviews, component summaries, and data-flow descriptions.

How to document an undocumented legacy codebase?▼

First build a knowledge graph with confidence-labelled edges using codebase analysis tooling, then use this Skill to draft documentation from the graph. Generated drafts go to a Technical Writer for review before publication.

Does this Skill depend on a specific graph analysis tool?▼

No. Per ADR-008, it reads only the outputs of the Codebase Analysis Capability Contract and never addresses Graphify or any specific tool directly, so the underlying analysis tool can be replaced without changing the Skill.

When should I not use automated documentation generation?▼

Avoid it when no knowledge graph or analysis report exists, when authoritative documentation is already current, or when documentation must capture business rules not present in code — use requirements elicitation instead.

How are uncertain findings handled in generated documentation?▼

Every generated claim keeps its source confidence label: EXTRACTED, INFERRED, or AMBIGUOUS. Text relying on INFERRED or AMBIGUOUS edges is explicitly marked so reviewers know what needs verification.