Project Automation Plan 1

Scope: Update the canonical lifecycle definition files so the repo has one authoritative evaluation-based lifecycle, one report-persistence standard, and one phase naming convention.

---

Task 1 — Update the canonical lifecycle text in Project Flow

Spec Section 1 defines the canonical lifecycle as Create → Requirements → Requirements_Eval → Research → Spec → Spec_Eval → Plan → Plan_Eval → Execute → Eval → Verify → Extract → Extract_Eval → Complete and requires one shared phase naming convention.

Edit Forge/Skills/Project_Flow/SKILL.md so its lifecycle section, phase detection logic, and terminology all use the evaluation-based lifecycle. Replace legacy Implement, Evaluate, Fix, Spec_Audit, and Plan_Audit phase names with the canonical terms from the Spec.

Task 2 — Add the persisted-report standard to the shared lifecycle docs

Spec Section 2 requires every review- or evaluation-producing phase to write to a durable markdown file, and those report artifacts are part of the canonical workflow definition.

Edit Forge/Skills/Project_Flow/SKILL.md, Forge/Configs/Agents/Project_Snippet.md, and Forge/Configs/Agents/Forge_Chat_Prompt.md so each explains that evaluation/report phases persist their outputs to files, including the stable artifact set named in Spec Section 2.

Task 3 — Verify the three canonical lifecycle strings are identical

Spec Section 1 states that the lifecycle string appears identically in Project Flow, Project Snippet, and Forge_Chat_Prompt.

After editing, compare the lifecycle string in all three files and confirm they match exactly, including phase order and spelling.

Task 4 — Build, commit, push

Spec Section 3 requires structural changes to be persisted and verifiable.

Run the site build, stage the changed files, commit with message Project Automation: Plan 1 — canonical lifecycle and report standard, and push to dev.