Use docs cockpit
Single-file project dashboard (Kanban + Sprint + KPI) from YAML frontmatter. Ships as a Claude Code plugin.
npx -y skills add Guohao1020/docs-cockpit --skill use-docs-cockpitAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Entry/router for the docs-cockpit skill ecosystem. Loaded by default in any project that has a docs-cockpit.yaml. Tells the agent: this project uses docs-cockpit; cognition lives in skills, python only renders; route to docs-cockpit-build (create/extend association), docs-cockpit-rebuild (refresh/diagnose/read-status/health checkup), or CLI docs-cockpit render (just regenerate HTML).
SKILL.md
2.8 KB, as published. Nobody here has run it
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 report feeds the dashboard health panel) | docs-cockpit-rebuild skill | 「体检一下」 "run a health check" |
| Upgrade docs-cockpit itself | CLI docs-cockpit upgrade (see references/operations.md · upgrade) | 「升级 docs-cockpit」 "update docs-cockpit" |
Discriminator between the two skills: build = the association does not exist yet (or whole-project planning); rebuild = it already exists and needs diagnosis / refresh (or just reading).
When NOT to apply
If the project has no docs-cockpit.yaml at the repo root, this router does not apply — the project does not use docs-cockpit. (The SessionStart hook injects this file conditionally, but a marketplace install can also trigger it directly; check for the config first.)