docs-generation

Convert a knowledge graph into a structured docs/ folder with TOC and AGENTS.md.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/ignidus/iscagent --skill docs-generation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-generation
Source: https://github.com/ignidus/iscagent/tree/main/skills/docs-generation
Command: npx skills add https://github.com/ignidus/iscagent --skill docs-generation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a machine-generated knowledge graph into accessible project documentation to accelerate onboarding and share architecture context with humans and agents.

Core Features & Use Cases

  • Knowledge-graph to docs: generate human-readable overviews, architecture diagrams, and onboarding content from a discovered knowledge graph.
  • Structured output: creates a docs/ directory with README.md, architecture.md, onboarding.md, AGENTS.md, and per-layer modules.
  • Onboarding and handoff: ideal for enabling new team members and AI agents to understand the codebase quickly.

Quick Start

Run the docs-generation skill to produce a complete docs/ folder from your knowledge graph.

Frequently Asked Questions about docs-generation

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

FAQPage Schema
How do I generate project documentation from a knowledge graph?

To generate project documentation from a knowledge graph, you need a tool that transforms graph data into a structured docs/ folder with prose, architecture diagrams, onboarding content, and an agent reference file.

How does knowledge graph documentation work for onboarding new team members?

Knowledge graph documentation works by converting machine-generated graph data into accessible overviews and architecture content, accelerating onboarding by helping new team members and AI agents understand the codebase quickly.

What files do I need in a docs folder for agent-readable codebase context?

An agent-readable docs folder requires a README.md, architecture.md, onboarding.md, per-layer modules, and an AGENTS.md file to share architecture context effectively with AI agents.

Can I automate onboarding documentation using my existing knowledge graph data?

You can automate onboarding documentation by processing existing knowledge graph data to automatically output structured human-readable docs, eliminating manual writing and ensuring architecture context is consistently shared.

What is the best way to turn codebase architecture into readable docs?

The best way to turn codebase architecture into readable docs is transforming a discovered knowledge graph into a structured directory containing overviews, architecture diagrams, and onboarding content.

Does docs generation require a knowledge graph to be present beforehand?

Knowledge graph documentation generation requires a knowledge graph to be present beforehand, as the process transforms existing graph data into a complete docs folder rather than analyzing source code directly.