adamrdrew/get-phase-status
skills/get-phase-status/SKILL.md
Check the current status of a phase. Use when you need to understand where a phase is in the workflow.
$ install --global
skillsauthnpx skillsauth add adamrdrew/ushabti get-phase-statusInstall 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:36 AM58.5s1 file scanned
SKILL.md
- name:
- get-phase-status
- description:
- Check the current status of a phase. Use when you need to understand where a phase is in the workflow.
- user-invocable:
- false
Phase Status
How to Check Status
Run this command to see all phases with their status and step counts:
if [ -d .ushabti/phases ] && [ "$(ls -A .ushabti/phases 2>/dev/null)" ]; then
for dir in .ushabti/phases/*/; do
name=$(basename "$dir")
status=$(grep "^ status:" "$dir/progress.yaml" 2>/dev/null | awk '{print $2}')
impl=$(grep -c "implemented: true" "$dir/progress.yaml" 2>/dev/null || echo 0)
total=$(grep -c "implemented:" "$dir/progress.yaml" 2>/dev/null || echo 0)
echo "$name: $status ($impl/$total steps)"
done
else
echo "No phases exist yet"
fi
Status Values
| Status | Meaning | Next Action |
|--------|---------|-------------|
| planned | Phase created, not started | Builder begins implementation |
| building | Implementation in progress | Builder continues or addresses fixes |
| review | Implementation complete | Overseer reviews |
| complete | Phase is green | Scribe plans next phase |
Status Transitions
planned → building (Builder starts)
building → review (Builder finishes all steps)
review → building (Overseer requests fixes)
review → complete (Overseer approves)
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