skills/find-next-phase-number/SKILL.md
Determine the next sequential phase ID for creating a new phase. Use when planning a new phase.
npx skillsauth add adamrdrew/ushabti find-next-phase-numberInstall 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.
Run this command to determine the next available phase number:
current=$(ls -1 .ushabti/phases/ 2>/dev/null | sed 's/-.*//' | sort -n | tail -1)
if [ -z "$current" ]; then
echo "0001 (first phase)"
else
printf "%04d (after %s)\n" $((10#$current + 1)) "$current"
fi
0001, 0002, 0003, ...0001-initial-setup, 0002-add-auth, ...Once you have the next number and a slug:
mkdir -p .ushabti/phases/NNNN-your-slug
Replace NNNN with the next ID and your-slug with a short, lowercase, hyphenated description.
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