adamrdrew/describe-docs-system
skills/describe-docs-system/SKILL.md
Documentation system location and maintenance requirements. Load when consulting or updating project documentation.
$ install --global
skillsauthnpx skillsauth add adamrdrew/ushabti describe-docs-systemInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 1, 2026, 7:28 AM52.6s1 file scanned
SKILL.md
- name:
- describe-docs-system
- description:
- Documentation system location and maintenance requirements. Load when consulting or updating project documentation.
- user-invocable:
- false
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.
Related Skills
adamrdrew/set-phase-status
data-ai
VerifiedTrustedCommunity
Set the status field in a phase's progress.yaml. Use instead of manual Edit calls when transitioning phase status.
5SKILL.mdUpdated Mar 30, 2026
adamrdrew/phase-status
development
VerifiedTrustedCommunity
Query the status of a phase. Returns structured status information for external consumers.
5SKILL.mdUpdated Mar 30, 2026
adamrdrew/mark-step-done
data-ai
VerifiedTrustedCommunity
Mark a step as implemented in progress.yaml with notes and touched files. Use after completing each step instead of manual Edit calls.
5SKILL.mdUpdated Mar 30, 2026
adamrdrew/skills/list-cards
testing
VerifiedTrustedCommunity
# List Cards Scan and list all Hieroglyphs-compatible cards in `.ushabti/cards/`, with optional filtering by status or other criteria. ## When to Use Use this skill when: - You need to see all available work items - Looking for cards in a specific state (e.g., only `todo` cards) - Determining which cards to plan next - Checking card priorities and types ## Card Location Cards are stored in: ``` .ushabti/cards/{slug}/card.md ``` Each card is a directory containing a `card.md` file with YAML
5SKILL.mdUpdated Mar 30, 2026