Project Automation Plan 2

Scope: Update Project_Create and the create-time templates so new projects start with the correct uniqueness guarantees and the file structure needed by the new workflow.

---

Task 1 — Add global project-name conflict checking to Project_Create

Spec Section 9 requires Project_Create to block duplicate project names across all departments’ Projects/ and Archived/ folders before any files are created.

Edit Forge/Skills/Project_Create/SKILL.md so its procedure begins with a repo-wide conflict check for the requested project name. The procedure must stop with a clear user-facing conflict message if any active or archived project already uses that name.

Task 2 — Implement the uniqueness check in the create-time script or command path

Spec Section 9 requires the check to happen before copying templates, creating folders, or adding sidebar entries.

Locate the code or script path used by Project_Create to create new project folders. Add the actual repo-wide search there so the skill’s documented behavior is enforced in execution, not only described in prose.

Task 3 — Add templates for persisted evaluation reports

Spec Section 2 requires durable report artifacts for Requirements_Eval, Spec_Eval, Plan_Eval, Eval, Extract_Eval, and project audit output. None of these templates currently exist — all must be created.

Create new templates under Forge/Skills/Project_Create/templates/ for each persisted report file type. Use a shared structure where possible, but ensure the per-plan Eval report and the audit-results report have fields appropriate to their roles.

Task 4 — Update Project_Create to support the report-file workflow

Spec Sections 2 and 8 require the project to support persisted report files and a durable runs document.

Edit Forge/Skills/Project_Create/SKILL.md so it references the new eval-report templates. No placeholder files are created at project creation time — each phase creates its report file lazily when that phase runs. Document this lazy-creation convention explicitly in the skill.

Task 5 — Build, commit, push

Spec Section 9 requires the uniqueness behavior to be implemented and verifiable.

Run the build, stage the create-skill and template changes, commit with message Project Automation: Plan 2 — project creation uniqueness and templates, and push to dev.