Menu
Structure and field ownership for progress.yaml. Load when reading or updating phase progress state.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | describe-progress-file |
| description | Structure and field ownership for progress.yaml. Load when reading or updating phase progress state. |
| user-invocable | false |
Machine-readable state of the Phase. Structure:
phase:
id: NNNN
slug: short-slug
title: Title
status: planned|building|review|complete
steps:
- id: S001
title: Short title
implemented: false
reviewed: false
notes: ""
touched: []
Status transitions:
planned → building (when Builder starts)building → review (when all steps implemented)review → building (if Overseer requests fixes)review → complete (when Overseer approves)Field ownership:
implemented: Set by Builder when step is donereviewed: Set only by Overseernotes: Updated by whoever completes the steptouched: List of files meaningfully modifiedBootstrap 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.