Documentation

Generate and update Markdown documentation from codebases and design notes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation workflows are often manual and error-prone, leading to out-of-date or inconsistent technical docs that slow onboarding and maintenance.

Core Features & Use Cases

  • Generate initial docs from code, comments, and design notes.
  • Update existing docs automatically as code or APIs evolve.
  • Use Case: Automatically refresh API reference docs after each sprint to reflect new endpoints and changes.

Quick Start

Generate the project's technical documentation from the latest codebase.

Frequently Asked Questions about Documentation

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

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

You can generate technical documentation by parsing code comments, design specs, and changelogs to produce Markdown files with consistent frontmatter. This process creates initial docs for software projects, APIs, and architecture references directly from your existing codebase.

What is the best way to keep API reference docs in sync with code changes?

Automated documentation generation keeps API reference docs in sync by updating existing Markdown files as code evolves. You can automatically refresh API documentation after each sprint to reflect new endpoints and modifications without manual writing.

Can I use this to create developer guides from design notes and code comments?

Yes, you can create developer guides by applying documentation automation to parse design notes and code comments. It generates structured Markdown documentation across multiple languages and repositories for software projects and architecture references.

Does documentation generation work across different programming languages and repositories?

Documentation generation works across languages and repositories by parsing code comments and design specs. It produces consistent Markdown documentation files with standardized frontmatter for various software projects, APIs, and developer guides.

How do I update existing Markdown documentation when APIs evolve?

You can update existing Markdown documentation automatically as APIs evolve by parsing the latest codebase and changelogs. This ensures technical docs remain synchronized with product changes, reducing manual errors and onboarding friction.