メニュー
Phase directory layout, naming conventions, and required files. Load when creating or navigating phase directories.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | describe-phase-directory-structure |
| description | Phase directory layout, naming conventions, and required files. Load when creating or navigating phase directories. |
| user-invocable | false |
.ushabti/phases/NNNN-short-slug/
├── phase.md # Intent, scope, acceptance criteria
├── steps.md # Ordered implementation steps
├── progress.yaml # Machine-tracked state
└── review.md # Review findings
Naming: Phase IDs are zero-padded and sequential (0001, 0002, ...). Slugs are short, lowercase, hyphenated, and descriptive.
Example: 0003-http-client-retry
Bootstrap phase context for Builder. Provides current phase, next step, and full phase file contents.
Bootstrap phase context for Overseer. Provides phase under review with full file contents and card metadata.
Approve a phase — sets status to complete, marks all steps reviewed, updates linked card. Use when declaring a phase green.
Create a phase directory with all required files in one call. Use instead of separate mkdir + Write calls when creating a new phase.
Kick a phase back to building — sets status and adds new step entries to progress.yaml. Use when requesting fixes from Builder.
Mark a step as implemented in progress.yaml with notes and touched files. Use after completing each step instead of manual Edit calls.