name: plan-progress-journal description: Record implementation progress against responsibility-based plan tasks in this repository. Use when feature work, refactors, bug fixes, or test updates are completed and the matching task folder in plan/tasks/* must be updated with status changes and a dated work log.

Plan Progress Journal

Name: plan-progress-journal
Rating: 87
Author: nichori-115

Use this workflow after implementing a change so the responsibility plan and history stay current.

Workflow

•Pick the responsibility area from references/area-map.md.
•Run scripts/record_progress.py with area, summary, and files.
•If a task is completed, pass --task "..." to mark the checklist item [x].
•Keep the summary concrete (what changed and why).

Command

bash

python3 .codex/skills/plan-progress-journal/scripts/record_progress.py \
  --area gameplay-engine \
  --status done \
  --summary "Split run scoring into dedicated engine file" \
  --files Sources/PenantSimLite/GameState+RunScoringEngine.swift Sources/PenantSimLite/PenantSimLite.swift \
  --task "Add inning-level run model"

Outputs

•Updates plan/tasks/<area>/TASKS.md when --task is provided.
•Appends area history at plan/tasks/<area>/HISTORY.md.
•Appends central history at plan/progress-log.md.
•Triggers board refresh by running improvement-board-sync/scripts/update_board.py.

Rules

•Do not use vague summaries such as "fix" or "update".
•Use relative repo paths in --files.
•Keep one execution per feature batch or bug-fix batch.