Forge Project Cleanup Plan Eval

Evaluation of all Plans for Forge_Project_Cleanup.

---

Evaluation Context

Field	Value
Phase	Plan_Eval
Run date	2026-06-26
Agent / session	Project Evaluator, fresh independent review session
Department	Forge
Project	Forge_Project_Cleanup
Vision	Forge/Projects/Forge_Project_Cleanup/Forge_Project_Cleanup_Vision.md
Research	Forge/Projects/Forge_Project_Cleanup/Forge_Project_Cleanup_Research.md
Spec	Forge/Projects/Forge_Project_Cleanup/Forge_Project_Cleanup_Spec.md
Plans	Plan 1 (todos replacement), Plan 2 (WIP removal), Plan 3 (bot prompts), Plan 4 (infrastructure/verification)
Skill	project-plan-eval

Verdict

Approved.

Checklist

#	Checklist Item	Plan 1	Plan 2	Plan 3	Plan 4	Note
1	Self-contained	✅	✅	✅	✅	Each task quotes the relevant Spec section and provides replacement text or content inline. An implementer can complete every task without consulting Vision, Research, or Spec.
2	Procedural, not declarative	✅	✅	✅	✅	Every task describes how to do the work step by step with specific file paths, search strings, replacement text, and tool names.
3	Single session	✅	✅	✅	✅	Plan 1 (8 tasks), Plan 2 (7 tasks), Plan 3 (6 tasks), and Plan 4 (6 tasks) are each scoped for one focused session.
4	Spec coverage	✅	✅	✅	✅	Plan 1 covers §2; Plan 2 covers §3 and §8; Plan 3 covers §4, §5, §6, §11, §12; Plan 4 covers §7, §9, §10, §14. All Spec sections are accounted for.
5	No gaps or overlaps	✅	✅	✅	✅	Each Plan has a distinct scope. Plan 1 and Plan 2 both touch Project_Verify/SKILL.md and Project_Extract_Eval/SKILL.md but for different replacement targets (Erik_Todo vs WIP), so there is no redundant work.
6	Ordered	✅	✅	✅	✅	Within each Plan: inventory → update → verify. Across Plans: Plan 1 and 2 update Knowledge/Skills before Plan 3 updates bot prompts (which must reference the updated Knowledge). Plan 4 verifies after all changes.
7	Task quality	✅	✅	✅	✅	Every task has a context quote block referencing the Spec section and actionable procedural steps.
8	No checkboxes	✅	✅	✅	✅	No checkboxes found in any Plan.
9	Planning scope rule	✅	✅	✅	✅	Plans direct edits to files explicitly named in their tasks. No Plan directs creation, modification, or deletion of files outside its named scope during planning-time. Implementation-time edits to named files are correct per the scope rule.
10	Testable output	✅	✅	✅	✅	Plan 1 Task 8, Plan 2 Task 7, Plan 3 Task 6, and Plan 4 Task 5 each provide verification steps whose output can be checked before the next Plan begins.

Items

#	Type	Description	Status	Disposition
E1	Variance	Plan 2 Task 2 references Workflow document section numbers (§3, §4.8, §4.9, §4.10, §6, §10) that may shift after Plan 1 Task 2 adds new subsections to the same document. However, each reference also includes the section heading or content description (e.g., “In the Document Types table (§3)”, “Remove section §4.10 (WIP document definition) entirely”), providing sufficient context to locate the correct section even if numbers change.	🟢 Resolved	Reject

Disposition values: Fix | Update plan | Reject | Defer to future cycle | Change requested by user

Status values: 🔴 Open | 🟡 In progress | 🟢 Resolved

Resolution Log

#	Disposition	Action taken	Resolved
E1	Reject	The section-number references in Plan 2 Task 2 are accompanied by heading/content descriptions that make them unambiguous even after Plan 1 modifies the same document. An implementing agent will locate sections by heading, not by number alone. No change needed.	Yes

Spec Coverage Traceability

Spec Section	Plan Coverage	Tasks
§1 — Project System Scope	Plan 4	Task 1 (infrastructure inventory)
§2 — todos Tool Group	Plan 1	Tasks 1–8 (full replacement cycle)
§3 — WIP System Removed	Plan 2	Tasks 1–7 (full removal cycle)
§4 — Durable Work-Product Communication	Plan 3	Tasks 2–5 (bot prompt updates)
§5 — Standard Handoff Packets	Plan 3	Tasks 2–5 (bot prompt updates)
§6 — Bot Compliance with Knowledge	Plan 3	Tasks 1, 6 (inventory + compliance audit)
§7 — Infrastructure Inventory & Verification	Plan 4	Tasks 1–2 (inventory + evidence)
§8 — Lifecycle, Templates, Pages, Sidebar	Plan 2	Task 6 (sidebar/page output)
§9 — Charter Alignment	Plan 4	Task 3 (alignment matrix)
§10 — Ambiguity Handling	Plan 4	Task 4 (ambiguity log)
§11 — Globally Unique Project Names	Plan 3	Task 2 (Runner prompt update)
§12 — User-Configurable Human Gates	Plan 3	Task 2 (Runner prompt update)
§13 — Requirement Traceability	Verified	All Vision requirements R1–R9 map to Spec sections covered above
§14 — Acceptance Criteria	Plan 4	Task 5 (final verification)

Cross-Plan Dependency Summary

Dependency	Reason
Plan 1 → Plan 3	Bot prompts must reference the updated Knowledge documents (todos tool group, no Erik_Todo)
Plan 2 → Plan 3	Bot prompts must reference the updated Knowledge documents (no WIP, recovery contract)
Plans 1+2+3 → Plan 4	Verification can only run after all changes are implemented

Plan 1 and Plan 2 are independent of each other and could run in parallel, but the Plans sequence them (Plan 2 references Plan 1 as prior plan) which is also acceptable.

Build / Commit Evidence

Step	Evidence
Phase update	Phase set to Plan_Eval_Started in commit 9b1faef; pushed to dev.

Next-Step Instruction

Set Phase: Plan_Eval_Completed. The Plans are approved for the Execute phase, subject to normal Runner routing and any configured human gate behavior.