← ClaudeAtlas

doc-routinglisted

Documentation Router & Architect — decides WHERE new information belongs in the project documentation system. Use BEFORE creating/updating any docs: PRD, features, journeys, integrations, NFR, requirements. Guarantees consistency and prevents duplication. Triggers: "doc routing", "document this", "where to put docs", "doc architecture", «куда писать», «документация», "/doc-routing"
akuroglo/claude-code-setup · ★ 0 · AI & Automation · score 75
Install: claude install-skill akuroglo/claude-code-setup
# /doc-routing — Documentation Router ## Purpose The single authoritative skill for deciding **"which information goes where"** in project documentation. Prevents: - Duplication between the PRD and feature docs - Lost context (no designated home for important information) - Drift between documents - Ad-hoc decisions about doc structure Other doc skills (e.g. `doc-feature`) delegate routing decisions to this skill. This skill operates on the **Source layer** of the Source → Presentation model — see `docs/DOCUMENTATION_STRATEGY.md` (template ships in this repo: `templates/DOCUMENTATION_STRATEGY.md.template`). Derived/public docs sync from the files routed here. ## When to Use - The user says "document X" - Before creating/updating any docs in `docs/` or `.claude/research/` - When reviewing existing documentation - Whenever the question "where does this go?" comes up - Automatically before `doc-feature` ## Decision Tree ``` Information to document │ ▼ [What does it describe?] │ ┌────────┼────────┬───────────┬──────────┬────────────┬──────────┬──────────┐ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ Product Module Cross- External Non- Roadmap / Decision Glossary / (WHY) (HOW) module service functional tracker rationale terminology │ │ flow │ (perf/sec/ │ │ ▼ ▼ │ ▼