documentation

Generate and synchronize README files, API specs, ADRs, and diagrams with source code.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/Ayub-Khan/immortal_agent_swarm --skill documentation-ayub-khan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation
Source: https://github.com/Ayub-Khan/immortal_agent_swarm/tree/main/.agents/skills/documentation
Command: npx skills add https://github.com/Ayub-Khan/immortal_agent_swarm --skill documentation-ayub-khan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and maintain comprehensive project documentation including READMEs, API docs (OpenAPI), Architecture Decision Records (ADRs), and diagrams as code.

Core Features & Use Cases

  • Templates and patterns for README, API docs, ADRs, and diagrams as code.
  • Sync with code to ensure docs stay up-to-date with source.
  • Use Case: When starting a new project, generate standard docs skeletons and keep them updated as code evolves.

Quick Start

Create a complete documentation suite for a project by generating READMEs, API docs, ADRs, and diagrams from code.

Frequently Asked Questions about documentation

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

FAQPage Schema
How do I generate consistent README files and API documentation for a new software project?

You can generate README files and API documentation using standardized templates that create documentation skeletons, ensuring project docs remain uniform and synchronized with your source code as it evolves.

What are architecture decision records and when should I document them?

Architecture Decision Records (ADRs) capture significant technical decisions and their context. You should document ADRs when starting new projects or making structural changes to maintain a clear history of architectural choices alongside your codebase.

Can I synchronize OpenAPI specifications and diagrams as code with my source code?

Yes, you can synchronize OpenAPI specifications and diagrams rendered as code with your source files. Tooling support detects code changes and updates the documentation automatically to prevent configuration drift.

What is the best way to maintain technical documentation at scale without it becoming outdated?

Maintaining technical documentation at scale requires syncing docs with code to ensure they stay up-to-date with source. Using templates and patterns for API specs and diagrams keeps everything consistent as your codebase evolves.

Do I need any specific frameworks to create architecture diagrams as code?

No specific frameworks are required as dependencies. The tooling provides templates and patterns to render architecture diagrams as code directly within your existing software project environment without external framework constraints.