Project Automation Plan 5

Scope: Update the content-phase skills so they hand off correctly into the new evaluation phases and reference the persisted report files the human will review.

---

Task 1 — Update Project_Requirements and Project_Research

Spec Sections 1 and 5 require the Requirements phase to lead into Requirements_Eval and the human-review workflow to use stable project artifacts.

Edit Forge/Skills/Project_Requirements/SKILL.md so it ends at Requirements_Completed, prepares the human review step cleanly, and references the upcoming Requirements_Eval artifact. Edit Forge/Skills/Project_Research/SKILL.md so it uses only canonical terminology and clearly distinguishes Research decision review from later evaluation reports.

Task 2 — Update Project_Spec and Project_Plan

Spec Section 1 requires Spec to hand off to Spec_Eval and Plan to hand off to Plan_Eval, with no inline audit delegation.

Edit Forge/Skills/Project_Spec/SKILL.md and Forge/Skills/Project_Plan/SKILL.md so each ends cleanly at its own phase completion, points to its next evaluation phase, removes legacy audit terminology, and tells the human where the persisted evaluation file will appear.

Task 3 — Update sidebar/build/status details for the content-phase skills

Spec Section 3 requires the workflow audit to verify complete work products, including sidebar updates, statuses, and build/commit/push steps.

For Project_Requirements, Project_Research, Project_Spec, and Project_Plan, verify and fix any missing sidebar updates, document-status transitions, or build/commit/push steps so they satisfy the workflow audit checklist.

Task 4 — Build, commit, push

Spec Sections 1, 3, and 5 require these handoffs to be consistent before agent routing is updated.

Run the build, stage the content-phase skill updates, commit with message Project Automation: Plan 5 — content phase skill handoffs, and push to dev.