Menu
Required sections and format for phase.md. Load when defining phase intent, scope, and acceptance criteria.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | describe-phase-file |
| description | Required sections and format for phase.md. Load when defining phase intent, scope, and acceptance criteria. |
| user-invocable | false |
Defines what the Phase accomplishes and how success is measured.
Required sections:
Optional metadata:
card: {slug}) if this phase was derived from a card. This field should appear immediately after the phase title and before the Intent section. When Overseer completes the phase, the referenced card will be marked as done.Acceptance criteria must be verifiable by the Overseer.
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.