Project Automation Plan 3

Scope: Implement the evaluation-phase skills for Requirements, Spec, and Plan, and make each one persist its findings to a stable report file.

---

Task 1 — Create the Requirements_Eval skill

Spec Section 1 defines Requirements_Eval as a formal phase, and Spec Section 2 requires its output to be written to {Project}_Requirements_Eval.md. No existing skill covers this phase — create a new one.

Create Forge/Skills/Project_Requirements_Eval/SKILL.md with: phase start/end names (Requirements_Eval_Started / Requirements_Eval_Completed), independent-reviewer requirement, context boundary (read only Requirements and any existing Requirements_Eval report), checklist for clarity/testability/non-contradiction/completeness, procedure that writes findings to {Project}_Requirements_Eval.md, return to Requirements phase when findings exist, sidebar update, and build/commit/push.

Task 2 — Replace Project_Spec_Audit with Project_Spec_Eval

Spec Sections 1 and 2 require Spec_Eval instead of Spec_Audit, and the output must be saved to {Project}_Spec_Eval.md. The existing skill at Forge/Skills/Project_Spec_Audit/SKILL.md must be replaced.

Trash Forge/Skills/Project_Spec_Audit/, then create Forge/Skills/Project_Spec_Eval/SKILL.md with: phase start/end names (Spec_Eval_Started / Spec_Eval_Completed), independent-reviewer requirement, context boundary (read only Requirements, Research, Spec), the existing Spec_Audit checklist adapted for the new naming, procedure that writes findings to {Project}_Spec_Eval.md, return to Spec phase when findings exist, sidebar update, and build/commit/push.

Task 3 — Replace Project_Plan_Audit with Project_Plan_Eval

Spec Sections 1 and 2 require Plan_Eval instead of Plan_Audit, and the output must be saved to {Project}_Plan_Eval.md. The existing skill at Forge/Skills/Project_Plan_Audit/SKILL.md must be replaced.

Trash Forge/Skills/Project_Plan_Audit/, then create Forge/Skills/Project_Plan_Eval/SKILL.md with: phase start/end names (Plan_Eval_Started / Plan_Eval_Completed), independent-reviewer requirement, context boundary (read only Requirements, Research, Spec, and all Plans), the existing Plan_Audit checklist adapted for the new naming, procedure that writes findings to {Project}_Plan_Eval.md, return to Plan phase when findings exist, sidebar update, and build/commit/push. Also fix the planning scope rule checklist item: the rule should distinguish between (a) revising plan documents during planning (Plan+State only, plus Requirements/Spec if needed), and (b) implementation plans that direct edits to the files explicitly named in their tasks — the latter is correct and should not be flagged as a defect.

Task 4 — Verify eval-revise behavior for all three skills

Spec Section 1 requires each evaluation phase to return the project to the preceding content phase when findings exist.

For Requirements_Eval, Spec_Eval, and Plan_Eval, verify that the documented return path is Requirements, Spec, and Plan respectively, and that the persisted report file survives reruns as durable review history.

Task 5 — Build, commit, push

Spec Sections 1 and 2 require evaluation phases to be both routable and durable.

Run the build, stage the new or renamed eval skills and report templates, commit with message Project Automation: Plan 3 — requirements/spec/plan eval skills, and push to dev.