Skip to content
archived Visibility internal Owner erik@uvilo.com Approver _ Created 2026-06-14 Updated 2026-06-14

Project Automation Plan 4

Scope: Implement the execution-side workflow: Execute, Eval, Verify, Extract, and Extract_Eval, with persisted report files and the correct return loops.


Task 1 — Rename Implement to Execute and remove Fix as a standalone lifecycle phase

Spec Section 1 uses Execute and Eval; there is no standalone Fix phase in the canonical lifecycle.

Update the implementation skill currently named Project_Implement so it becomes Project_Execute, uses Execute phase names throughout, and returns directly from failed Eval runs back to Execute for the same plan.

Task 2 — Implement Eval with one durable report file per plan

Spec Section 2 requires {Project}_Eval_{N}.md, with repeated eval runs appended within the same plan-specific file.

Create or update Project_Eval so it runs in a fresh evaluator session, writes findings to the per-plan Eval report file, appends reruns within that file, and sets the next phase correctly based on pass/fail.

Task 3 — Persist Verify and Extract review output to files

Spec Section 2 requires verification output in {Project}_Verification.md and extraction review output in {Project}_Extract_Eval.md.

Update Project_Verify, Project_Extract, and Project_Extract_Eval so verification findings are appended to the verification file, extraction review findings are written to the Extract_Eval file, and both phases provide stable file targets for Erik_Todo review links.

Task 4 — Verify the closing loop behavior

Spec Sections 1 and 2 require Verify to remain the project-wide review gate and Extract_Eval to return to Extract when findings exist.

Verify in the updated skill text that: failed Eval returns to Execute; Verify findings route to the correct next action without using Fix; failed Extract_Eval returns to Extract; and every review artifact is persisted before the phase changes.

Task 5 — Build, commit, push

Spec Sections 1 and 2 require the execution-side loop to be verifiable and durable.

Run the build, stage the execution-side skill changes, commit with message Project Automation: Plan 4 — execute, verify, and extract report flow, and push to dev.