Claude-skill-registry describe-docs-system
Documentation system location and maintenance requirements. Load when consulting or updating project documentation.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/describe-docs-system" ~/.claude/skills/majiayu000-claude-skill-registry-describe-docs-system && rm -rf "$T"
manifest:
skills/data/describe-docs-system/SKILL.mdsource content
Documentation System
Project documentation lives in
.ushabti/docs/.
.ushabti/docs/ ├── index.md # Index of all project documentation └── *.md # Documentation on project systems
Agent Responsibilities
Scribe: MUST consult
.ushabti/docs/ when planning Phases. Understanding documented systems is prerequisite to coherent planning.
Builder: MUST consult
.ushabti/docs/ during implementation. When code changes affect documented systems, update the relevant docs. Include docs files in the touched list in progress.yaml when updated.
Overseer: MUST verify that docs are reconciled with code changes before declaring a Phase complete. Stale docs are defects.
Review Gate
A Phase cannot be marked complete until docs are reconciled with the code work performed during that Phase. This is a hard requirement enforced by Overseer.