find-next-step

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.

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.

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.

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.

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.

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.