describe-phase-directory-structure

A standardized phase directory structure requires phase.md for intent, steps.md for steps, progress.yaml for machine state, and review.md for findings to ensure consistent project organization.

You organize phase-specific artifacts by creating a phase directory under .ushabti/phases/ using a zero-padded ID, then storing intent, steps, machine state, and review findings in standardized files.

Phase IDs and slugs should use zero-padded numbers for the directory name, ensuring phases sort correctly and maintain a consistent folder layout across different projects.

You need to create a new phase directory when starting a new phase in a Ushabti project, ensuring all required artifacts like phase.md, steps.md, progress.yaml, and review.md are properly initialized.

Yes, the phase directory layout enforces a standardized folder structure with no external dependencies, relying only on required files like phase.md, steps.md, progress.yaml, and review.md for organization.

A standardized directory layout is needed for phase management to ensure consistency across projects, providing a ready reference for creating, navigating, and auditing phases without structural ambiguity.