Menu
Documentation system location and maintenance requirements. Load when consulting or updating project documentation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Bootstrap phase context for Builder. Provides current phase, next step, and full phase file contents.
Bootstrap phase context for Overseer. Provides phase under review with full file contents and card metadata.
Approve a phase — sets status to complete, marks all steps reviewed, updates linked card. Use when declaring a phase green.
Create a phase directory with all required files in one call. Use instead of separate mkdir + Write calls when creating a new phase.
Kick a phase back to building — sets status and adds new step entries to progress.yaml. Use when requesting fixes from Builder.
Mark a step as implemented in progress.yaml with notes and touched files. Use after completing each step instead of manual Edit calls.
| name | describe-docs-system |
| description | Documentation system location and maintenance requirements. Load when consulting or updating project documentation. |
| user-invocable | false |
Project documentation lives in .ushabti/docs/.
.ushabti/docs/
├── index.md # Index of all project documentation
└── *.md # Documentation on project systems
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.
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.