find-next-step

Parse .ushabti/phases/*/progress.yaml and report the next unimplemented step.

7|1|Updated Jan 27, 2026

Search Tags:#automation #workflow #bash #project-management #next-step #phase-progress

Ready to run

npx skills add https://github.com/adamrdrew/ushabti --skill find-next-step

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: find-next-step
Source: https://github.com/adamrdrew/ushabti/tree/main/skills/find-next-step
Command: npx skills add https://github.com/adamrdrew/ushabti --skill find-next-step

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly identify the next unimplemented step in a phase, preventing stalled work and enabling focused progression.

Core Features & Use Cases

Scans .ushabti/phases/*/progress.yaml to locate phases with building or planned status and a next unimplemented step.
Reports the phase name and the next step, or notes when all steps are implemented.
Useful for sprint planning, backlog grooming, and maintaining momentum in phase-based workflows.

Quick Start

Run this command to identify the next unimplemented step across active phases.

Frequently Asked Questions about find-next-step

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify the next unimplemented step in a phase-driven workflow?▼

To identify the next unimplemented step, parse the progress.yaml files within your phase directories to locate the first incomplete task. This allows you to quickly find the next step for each active phase, preventing stalled work and enabling focused progression.

How does tracking phase progress help with sprint planning?▼

Tracking phase progress helps with sprint planning by scanning active phases to report the next unimplemented step or noting completion. This maintains momentum in phase-based workflows by ensuring teams always know the immediate next action required.

Can I use bash automation to find the next step across multiple active phases?▼

Yes, you can use bash automation to find the next step across multiple active phases by parsing the progress.yaml files in your phase directories. The script inspects phases with building or planned status and reports the first unimplemented step found.

What is the best way to prepare for a project review using phase progress data?▼

The best way to prepare for a project review using phase progress data is to scan for phases with planned or building status and report their next unimplemented steps. This provides a clear overview of remaining work and current momentum across the workflow.

What happens when all steps in a phase are implemented?▼

When all steps in a phase are implemented, the progress inspection reports that all steps are complete. This prevents the system from stalling while searching for a next step and confirms that the active phase requires no further unimplemented actions.

Do I need a specific directory structure to track unimplemented steps?▼

Yes, you need a specific directory structure to track unimplemented steps. The process requires parsing progress.yaml files located within .ushabti/phases/ directories to accurately locate and report the next unimplemented step for active phases.