documentation

Routes documentation tasks to scaffold, update, or migrate skills via manifest.json.

2|Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Arasz/ai-badger --skill documentation-arasz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation
Source: https://github.com/Arasz/ai-badger/tree/main/features/common/skills/documentation
Command: npx skills add https://github.com/Arasz/ai-badger --skill documentation-arasz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Documentation work spans three very different jobs — creating a docs tree from nothing, keeping existing docs accurate after code changes, and reorganising a legacy tree wholesale — and picking the wrong procedure wastes effort or corrupts history. This gateway skill reads the task and routes it to exactly one specialized member skill. ## Core Features & Use Cases - Task routing: Matches the request against a routing table and machine-readable triggers in manifest.json, then opens exactly one member's SKILL.md so only relevant instructions load. - Three member skills: scaffold-documentation creates the canonical Diátaxis tree and directory READMEs; update-documentation makes evidence-backed single changes with ledger records; migrate-documentation runs a resumable, state-file-driven wholesale reorganization. - Shared references: Members cite each other's placement, trust, amendments, and structure references by path, so guidance ships with the skill that owns it. - Use Case: A user says "reorganise docs/, it's a mess" — the gateway matches the migrate-documentation member, which then drives a phased, git-mv-based migration with drain gates before any legacy file is deleted. ## Quick Start Ask the agent to handle a documentation task — for example "set up the docs structure for this repo" — and it will route to the matching member skill and execute it.

Frequently Asked Questions about documentation

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

FAQPage Schema
How do I choose between scaffold, update, and migrate documentation skills?

Match the task to the routing table: scaffold-documentation when no docs tree exists, update-documentation for a single change to an existing tree, and migrate-documentation for wholesale reorganization. The manifest.json triggers column automates this matching.

How do I create a documentation structure for a new repository?

The scaffold-documentation member creates the canonical Diátaxis tree (tutorials, how-to, reference, explanation, adr, work), writes a complete root README map plus one README per directory, and records seeded files in the project's ledger if one exists.

Can this skill migrate a large legacy docs folder without losing git history?

Yes. The migrate-documentation member uses git mv in rename-only commits, records old-to-new path edges instead of redirect stubs, and keeps all resumable state in a committed state file so history and progress survive across sessions.

Does the documentation skill work without the optional ledger tool?

Yes. The ledger extensions activate only when .ai-badger/config.json sets docs.tool; without it, the base skills run the same gates manually, losing automation but nothing else.

When should I not use this documentation gateway?

Do not use it for writing prose inside a document that already has a home — that is ordinary editing. It also does not apply when no member's triggers match; in that case it reports no match rather than improvising.