---

name: docs-routing category: knowledge-documentation/documentation version: 1.0.0 description: Ensure every meaningful output lands in the right place and stays findable author: blackbox5/core verified: true tags: [documentation, routing, organization, knowledge-management]

Docs Routing + Ledger

This skill prevents "we did work but can't find it" by requiring:

• a canonical destination
• a traceable artifact pointer
• a ledger entry

The goal is traceability - anyone should be able to find what was created, where it lives, and what supporting artifacts exist.

<routing_rules> Reusable knowledge that should be referenced long-term .knowledge/ subdirectories organized by topic Best practices, architecture decisions, research summaries Raw outputs, sources, temporary working files Plan folder artifacts/ subdirectory Raw data, source lists, intermediate outputs Research that produces reusable insights .knowledge/deepresearch/ Link back to plan artifacts for full context </routing_rules>

<best_practices> Always use the ledger - it's the single source of truth for what exists where Keep artifacts raw and unprocessed Make canonical knowledge polished and standalone Use descriptive filenames that indicate content type Include dates in ledger entries for chronological tracking Update indexes proactively, not reactively </best_practices>

<anti_patterns> Create docs without updating ledger Mix artifacts and canonical knowledge in same location Forget to link canonical docs back to their source artifacts Use vague filenames that don't indicate content Skip updating indexes - "I'll do it later" </anti_patterns>

<integration_notes> Use this skill when:

• Creating new docs outside .blackbox/
• Moving or renaming docs
• Promoting research results into visible docs
• Organizing existing knowledge

This skill integrates with:

• deep-research - Research outputs need proper routing
• intelligent-routing - For determining where things go
• first-principles-thinking - Analysis outputs often need routing </integration_notes>

<output_format> Ledger entry format:

CopyYYYY-MM-DD — <type> — <topic> — <knowledge path> — artifacts: <plan path>

Example:

Copy2026-01-18 — research — state management comparison — .knowledge/deepresearch/state-management.md — artifacts: agents/.plans/state-research/

Types:

• research
• best-practices
• architecture
• decision
• tutorial
• reference </output_format>

<error_handling> If LEDGER.md doesn't exist:

• Create it at .knowledge/LEDGER.md
• Add header explaining purpose
• Start with first entry

If .knowledge structure doesn't exist:

• Create appropriate subdirectories
• Add README.md explaining organization
• Document structure choices

If destination is unclear:

• Use intelligent-routing to determine best location
• Create new subdirectory if warranted
• Document decision in folder's .purpose.md </error_handling>

<related_skills> deep-research intelligent-routing first-principles-thinking </related_skills>

<see_also> .knowledge/LEDGER.md - Knowledge tracking ledger .knowledge/deepresearch/ - Reusable research storage agents/.plans/ - Plan and artifact storage </see_also>