Create and maintain repo-local PDCA goal-loop work folders with decision points, state history archives, restart prompts, and visual status dashboards. Use when the user asks to create, organize, continue, audit, visualize, or standardize work/ task folders with non-linear execution and durable state history.
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.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Create and maintain repo-local PDCA goal-loop work folders with decision points, state history archives, restart prompts, and visual status dashboards. Use when the user asks to create, organize, continue, audit, visualize, or standardize work/ task folders with non-linear execution and durable state history.
Work PDCA Loop
Use this skill for repo-local work/ task folders that must be easy to sort, resume, audit, visualize, and hand off.
This is not a static template. It models work as a PDCA loop:
Plan: frame objective, constraints, acceptance, and decision criteria.
Do: execute the smallest tracer path that can produce evidence.
Check: compare evidence against acceptance, risks, and regressions.
Act: close, continue, or pivot based on recorded decisions.
Execution must not be purely linear. Decision points such as D1 and D2 determine whether to continue, split, research, pivot, or close.
Decision points are first-class state, not prose only.
Example shape:
{"id":"D1","phase":"D1","question":"Which route should the next implementation take?","status":"open","options":[{"id":"direct","label":"Direct implementation","next_phase":"P2","criteria":"Scope is clear, blast radius is small, and validation path is known."}],"selected_option_id":null,"rationale":"","decided_at":null}
Do not move past a decision phase without recording:
selected option
rationale
next phase
timestamp
Generator
Prefer the bundled PDCA generator for new folders:
bun ~/.agents/skills/work-pdca-loop/scripts/create-pdca-goal.mjs \
--project-root /path/to/project \
--work-root work \
--slug dyncode-sync-event-listener-goal \
--title "Dyncode Sync Event Listener Goal" \
--objective "Design and implement sync table listener registration." \
--date 20260706
Package script form inside this skill directory:
bun run create -- --project-root /path/to/project --work-root work --slug dyncode-sync-event-listener-goal --title "Dyncode Sync Event Listener Goal" --objective "Design and implement sync table listener registration."
The script fails if the target folder already exists. It creates required files, an initial state.json, an initial state snapshot, and a creation event.
State Updates
Do not edit state.json by blind overwrite when changing status. Use the update script so old state is archived first.
Project paths may use ~. Passing /path/to/project/work is normalized to project root plus workRoot=work. Custom state schemas still work when compatible fields exist (objective, current_phase, phases, decision_points, validation).
Maintenance Checklist
Keep state.json.status, state.json.pdca.stage, and state.json.next_action current.
Use update-pdca-state.mjs for state changes so history is preserved.
Record validation commands after they run.
Record decision option and rationale before crossing decision phases.
Update references when a folder is renamed.
When a task is withdrawn, keep status: "withdrawn" and explain why.
Do not mark a broad goal complete unless current evidence proves all required work.
