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.