Agent skill
find-next-step
Find the next unimplemented step in a phase. Use when determining what to work on next.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/find-next-step
SKILL.md
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.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?