adamrdrew/find-next-step
skills/find-next-step/SKILL.md
Find the next unimplemented step in a phase. Use when determining what to work on next.
$ install --global
skillsauthnpx skillsauth add adamrdrew/ushabti find-next-stepInstall 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:35 AM56.1s1 file scanned
SKILL.md
- name:
- find-next-step
- description:
- Find the next unimplemented step in a phase. Use when determining what to work on next.
- user-invocable:
- false
Next Step
How to Find Next Step
Run this command to see active phases and their next unimplemented step:
if [ -d .ushabti/phases ] && [ "$(ls -A .ushabti/phases 2>/dev/null)" ]; then
for dir in .ushabti/phases/*/; do
status=$(grep "^ status:" "$dir/progress.yaml" 2>/dev/null | awk '{print $2}')
if [ "$status" = "building" ] || [ "$status" = "planned" ]; then
name=$(basename "$dir")
next=$(awk '/- id:/{id=$3} /implemented: false/{print id; exit}' "$dir/progress.yaml" 2>/dev/null)
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)
if [ -n "$next" ]; then
echo "$name: next step is $next ($impl/$total done)"
else
echo "$name: all steps implemented - ready for review"
fi
fi
done
else
echo "No active phases"
fi
How Steps Are Tracked
In progress.yaml, each step has:
id: Step identifier (S001, S002, ...)implemented: false until Builder completes itreviewed: false until Overseer verifies it
Workflow
- Find the current phase (use find-current-phase)
- Read
progress.yamlto find first step withimplemented: false - Read that step's details in
steps.md - Implement the step
- Update
progress.yaml: setimplemented: true, add notes, list touched files - Repeat until all steps are implemented
When All Steps Are Done
If no steps have implemented: false, the phase is ready for review. Set phase.status: review in progress.yaml and hand off to Overseer.
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