Forge Project Plan 4 — Completion Skills & System Integration

Scope: Create the 4 completion/utility skills (Check, Extract, Complete, and Rename), update FORGE.md, and retire the existing Archive_Project skill by folding it into Project_Complete. Spec: Forge Project Spec Prior plan: Plan 3 — Execution Phase Skills

---

Task 1 — Create the Project_Check Skill

Check skill. Final project-level evaluation after all Plans are implemented.

Create Forge/Skills/Project_Check/SKILL.md with:

• When to Use: When all Plans have been implemented and individually evaluated, and the project needs a final review.
• Inputs: Project path
• Must be a fresh agent session.
• Procedure:
  1. Read: Requirements, Spec (do NOT read Research, Plans, Learnings, or WIP)
  2. Verify every Verification Criterion (V1, V2…) is satisfied
  3. Verify the implementation matches the Spec as a whole
  4. Produce a findings report (same categories as Plan evaluation: defect, deviation, gap)
  5. Present to user — user decides per item: fix, accept, reject, defer
  6. If fixes are minor, implement them directly
  7. If fixes are substantial, create a new Plan and loop back to Implement
  8. Commit
• Rules:
  • This is a holistic check — looks at the complete system, not individual Plans
  • Requirements and Spec should already reflect accepted deviations from Plan evaluations
  • If a new Plan is needed, it follows the normal Plan → Implement → Evaluate cycle

---

Task 2 — Create the Project_Extract Skill

Extract skill. Extracts knowledge and skills from the project to permanent locations.

Create Forge/Skills/Project_Extract/SKILL.md with:

• When to Use: When project evaluation is complete and knowledge needs to be extracted before completion.
• Inputs: Project path
• Procedure:
  1. Read: Requirements, Spec (and skim project work products)
  2. Identify extractable content in these categories:
     • System documentation → department root-level Knowledge files
     • Reusable procedures → department Skills/ folder
     • Configuration knowledge → Infrastructure or system docs
     • Spec as documentation → sometimes the Spec (with edits) becomes permanent docs
     • Insights for existing docs → fold into existing knowledge files
  3. For each extraction:
     • Create or update the target document
     • Add sidebar entry if new
  4. Present the extraction list to the user for confirmation
  5. Verify: no useful information remains trapped inside the project folder
  6. Commit
• Rules:
  • Every piece of useful information must reach a permanent home
  • Don’t extract trivially obvious content — focus on hard-won knowledge
  • Extracted content should be self-contained in its new location (don’t leave dangling references to the project)

---

Task 3 — Create the Project_Complete Skill

Complete skill. Archives or publishes the project. Subsumes the existing Archive_Project skill.

Create Forge/Skills/Project_Complete/SKILL.md with:

• When to Use: When knowledge extraction is done and the project is ready to close.
• Inputs: Project path, completion action (archive or publish)
• Procedure:
  1. Confirm with user: archive (one-time project) or publish (ongoing process)?
  2. If Archive:
     • Set status: archived on all .md files in the project
     • Move project directory to {Dept}/Archived/ using git mv
     • Update sidebar paths from projects/ to archived/
     • Move the sidebar group from Projects to Archived section
     • Update or create {Dept}/Archived/index.md
  3. If Publish:
     • Set status: published on all .md files
     • Keep project in {Dept}/Projects/
  4. Clean up:
     • Ensure WIP file is deleted (it’s gitignored, but clean up if present)
     • Ensure Learnings file is empty (should have been cleared in evaluation)
  5. Run cd .internal && npm run build to verify
  6. Commit
• Rules:
  • Always use git mv for directory moves to preserve history
  • After this skill is created, update the existing Archive_Project skill to point to Project_Complete as its successor, and mark it as deprecated

---

Task 4 — Create the Project_Rename Skill

Rename utility skill (not a lifecycle phase). Renames a project or moves it to another department.

Create Forge/Skills/Project_Rename/SKILL.md with:

• When to Use: When a project needs to be renamed or moved to a different department.
• Inputs: Project path (current), new project name and/or new department
• Procedure:
  1. Determine the scope: rename only, move only, or both
  2. Rename files: All project files are prefixed with the folder name. Rename every {OldName}_*.md to {NewName}_*.md using git mv
  3. Rename folder: git mv the project folder to the new name
  4. If moving departments: git mv the folder to {NewDept}/Projects/{ProjectName}/
  5. Update internal references: Search all .md files in the project for old name references and update them (links, titles, header tables)
  6. Update sidebar: Replace all old slug paths with new ones in .internal/astro.config.mjs. If moving departments, relocate the sidebar group.
  7. Update external references: Search the repo for links to the old project path and update them (grep -rl "old/path")
  8. Run cd .internal && npm run build to verify
  9. Commit
• Rules:
  • Always use git mv to preserve history
  • File prefix must always match the folder name
  • Review all internal links — broken links are the most common rename issue

---

Task 5 — Update FORGE.md

R9: The WORK TRACKING section of FORGE.md must reflect the new project lifecycle.

Read the current FORGE.md WORK TRACKING section and update it:

1. Replace the project session workflow to reference the new lifecycle:

   • Step 1: Read the Plan (current) + State (current) + WIP (check for crash)
   • Step 2: Check git status for uncommitted changes
   • Step 3: Pick the next unchecked task from State and execute
   • Step 4: Update WIP and State as you go; record Learnings when obstacles occur
   • Step 5: At end: update State, commit and push

2. Update project file descriptions:

   • Remove History.md from project file list
   • Add: Plan (frozen procedural steps), State (living todo), Learnings (temporary obstacles/decisions), WIP (ephemeral crash recovery)
   • Add a reference to Project_Flow skill for the full lifecycle

3. Keep History.md for one-off tasks (Output/) which don’t use the full lifecycle

4. Update the Skills List in PERSISTENT KNOWLEDGE to include all 14 new skills (alphabetical order): Project_Complete, Project_Create, Project_Create_Plan, Project_Evaluate, Project_Evaluate_Plan, Project_Extract, Project_Fix_Implementation, Project_Flow, Project_Implement_Plan, Project_Rename, Project_Requirements, Project_Research, Project_Spec

5. Mark Archive_Project as deprecated in the skills list (it’s subsumed by Project_Complete)

---

Task 6 — Sidebar and Index Registration

Register all 4 new skills and verify the complete system.

1. Add Project_Evaluate, Project_Extract, Project_Complete, Project_Rename to Forge/Skills/index.md
2. Add all 4 to the Skills List in Forge/Configs/FORGE.md (done in Task 5)
3. Add sidebar entries in .internal/astro.config.mjs
4. Run cd .internal && npm run build to verify the entire sidebar
5. Do a final audit: all 14 skills exist, all 7 templates exist, FORGE.md is updated
6. Commit all files together