use-docs-cockpitlisted

# use-docs-cockpit > **[Session context · docs-cockpit router]** This block is injected at session start in any project with a `docs-cockpit.yaml`. Its only job: route you to the right skill before you act on any docs-cockpit-related intent. This project manages its documentation association system (module ↔ subtask ↔ spec/plan/RFC anchors) with **docs-cockpit**. North-star: **cognition lives in skills, Python only renders — and anchor precision comes first: a wrong anchor is worse than a missing anchor.** This file is a router only. Each routed skill carries its own complete workflow — read it before acting; do not improvise doc-association work from here. ## Routing | You want to | Use | Trigger examples | |---|---|---| | Build or extend the association system — set up the cockpit itself (config + scan dirs + debug build issues), plan the whole project's spec/plan, wire modules to docs, fill anchor gaps (0→1 / whole-project) | `docs-cockpit-build` skill | 「把项目做成看板」「把文档体系建起来」「关联模块和文档」「规划 spec」 | | Refresh an EXISTING association that drifted — anchors stale after refactor, spec evolved and links need re-sync | `docs-cockpit-rebuild` skill | 「关联乱了重新梳理」「anchor 失效了」 | | Just regenerate the dashboard HTML, no association work | CLI `docs-cockpit render` | 「重新生成 dashboard」 | | Read status / progress / blockers, no file changes | `docs-cockpit-rebuild` Phase 1 (pure status queries end there) | 「项目进度怎么样」「哪些卡了」 | | Run a project health checkup / 健康检查 (existing cockpit — the rep