skills/describe-phase-file/SKILL.md
Required sections and format for phase.md. Load when defining phase intent, scope, and acceptance criteria.
npx skillsauth add adamrdrew/ushabti describe-phase-fileInstall 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.
Defines what the Phase accomplishes and how success is measured.
Required sections:
Optional metadata:
card: {slug}) if this phase was derived from a card. This field should appear immediately after the phase title and before the Intent section. When Overseer completes the phase, the referenced card will be marked as done.Acceptance criteria must be verifiable by the Overseer.
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