skills/describe-phase-directory-structure/SKILL.md
Phase directory layout, naming conventions, and required files. Load when creating or navigating phase directories.
npx skillsauth add adamrdrew/ushabti describe-phase-directory-structureInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
.ushabti/phases/NNNN-short-slug/
├── phase.md # Intent, scope, acceptance criteria
├── steps.md # Ordered implementation steps
├── progress.yaml # Machine-tracked state
└── review.md # Review findings
Naming: Phase IDs are zero-padded and sequential (0001, 0002, ...). Slugs are short, lowercase, hyphenated, and descriptive.
Example: 0003-http-client-retry
data-ai
Set the status field in a phase's progress.yaml. Use instead of manual Edit calls when transitioning phase status.
development
Query the status of a phase. Returns structured status information for external consumers.
data-ai
Mark a step as implemented in progress.yaml with notes and touched files. Use after completing each step instead of manual Edit calls.
testing
# 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