skills/describe-progress-file/SKILL.md
Structure and field ownership for progress.yaml. Load when reading or updating phase progress state.
npx skillsauth add adamrdrew/ushabti describe-progress-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.
Machine-readable state of the Phase. Structure:
phase:
id: NNNN
slug: short-slug
title: Title
status: planned|building|review|complete
steps:
- id: S001
title: Short title
implemented: false
reviewed: false
notes: ""
touched: []
Status transitions:
planned → building (when Builder starts)building → review (when all steps implemented)review → building (if Overseer requests fixes)review → complete (when Overseer approves)Field ownership:
implemented: Set by Builder when step is donereviewed: Set only by Overseernotes: Updated by whoever completes the steptouched: List of files meaningfully modifieddata-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