Forge Project Plan 3 — Execution Phase Skills

Scope: Create the 3 skills for the execution phases: Implement, Evaluate, and Fix. Spec: Forge Project Spec Prior plan: Plan 2 — Definition Phase Skills

---

Task 1 — Create the Project_Implement Skill

Implement skill. The core execution skill — runs a Plan step-by-step, maintains State, WIP, and Learnings.

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

• When to Use: When a Plan is approved and ready for implementation.
• Inputs: Project path, Plan document to implement
• Context boundary: The implementing agent reads only the current Plan, State, and WIP. It must NOT read Requirements, Research, or Spec.
• Procedure:
  1. Read the Plan document
  2. Create the State document from the Plan:
     • Copy Forge/Skills/Project_Create/templates/State_Template.md to {Dept}/Projects/{Project}/{Project}_State_{Qualifier}.md (qualifier matches the Plan)
     • Convert each Plan Task into a checkbox item, with subtasks as nested checkboxes
  3. Create the WIP document:
     • Copy Forge/Skills/Project_Create/templates/WIP_Template.md to {Dept}/Projects/{Project}/{Project}_WIP.md
     • WIP is temporary and gets wiped at the end of each session
  4. Create the Learnings document:
     • Copy Forge/Skills/Project_Create/templates/Learnings_Template.md to {Dept}/Projects/{Project}/{Project}_Learnings.md
  5. Implement each task in order:
     • Mark the task [STARTED] in State
     • Execute the task’s procedural steps
     • Append steps taken, file paths touched, commands run to WIP
     • If an obstacle or unexpected decision occurs, add an entry to Learnings (L1, L2…)
     • Mark the task [x] when complete
  6. After all tasks: add sidebar entries for State and Learnings, build, commit
• Rules:
  • Context boundary is sacred. Never consult Requirements, Research, or Spec during implementation. If the Plan is missing context, that is a Plan authoring failure — stop and escalate.
  • Append to WIP after every meaningful step for crash recovery
  • Learnings entries must specify a Destination for where the insight should permanently live
  • State checkboxes use the conventions: no prefix (not started), [STARTED], [UNVERIFIED], [BLOCKED], [x]
  • If a crash occurred (WIP is non-empty at session start), resume from the last WIP entry

---

Task 2 — Create the Project_Evaluate Skill

Evaluate skill. A fresh agent evaluates Plan implementation against Requirements and Spec.

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

• When to Use: When a Plan’s implementation is complete (all State items checked) and needs evaluation.
• Inputs: Project path, which Plan to evaluate
• Must be a fresh agent session — new conversation with clean context, no carryover from implementation.
• Procedure:
  1. Read: Requirements, Spec, current Plan, current State, Learnings
  2. Review the implementation against Requirements and Spec:
     • Check each Requirement (R1, R2…) — is it addressed?
     • Check each Verification Criterion (V1, V2…) — is it satisfied?
     • Compare actual implementation to Plan intent
  3. Produce a defect/deviation report. Each item is categorized as one of:
     • Defect — implementation doesn’t match Spec or Requirements
     • Deviation — implementation differs from Plan for a reason
     • Gap — something in Requirements/Spec wasn’t addressed
     • Learning — entry from Learnings that needs permanent storage
  4. Present the report to the user for review
  5. For each item, the user decides: fix, accept, reject, or defer
  6. Process user decisions:
     • fix: Add corrective tasks to State and implement them (invoke Project_Fix_Implementation)
     • accept: Update Requirements and/or Spec retroactively to match reality
     • reject: Do nothing (user rejects the assessment)
     • defer: Add as tasks for a future Plan
  7. Incorporate Learnings entries into permanent documents per their Destination field, then clear the Learnings file
  8. If later Plans exist and are affected by changes, revise them (Plans are only revised before their implementation begins)
  9. Mark the Plan’s section in State as Approved ✓
  10. Commit
• Rules:
  • Plans are never modified — they are historical records of intent
  • Accepted deviations retroactively update Requirements and/or Spec (those are evergreen)
  • Learnings must be cleared by Evaluate — nothing stays in the temporary file
  • This must be a separate agent session from the implementation

---

Task 3 — Create the Project_Fix Skill

Fix skill. Implements fixes identified during Plan evaluation.

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

• When to Use: When Plan evaluation identifies defects that need fixing.
• Inputs: Project path, evaluation report with items marked “fix”, current State
• Procedure:
  1. Read the evaluation report (inline in the conversation from Evaluate) and current State
  2. Add corrective tasks to the State document as new checkbox items
  3. Implement each fix:
     • Mark [STARTED] in State
     • Execute the fix
     • Append to WIP
     • If new obstacles arise, add to Learnings
     • Mark [x] when complete
  4. If fixes reveal the need to update Requirements or Spec, note this for the evaluator
  5. Commit
• Rules:
  • Fix implementation follows the same discipline as Plan implementation (State, WIP, Learnings)
  • Context boundary is relaxed: the agent has access to the evaluation report which references Requirements and Spec
  • Plans are still never modified
  • If a fix is too large to be a patch, recommend creating a new Plan instead

---

Task 4 — Sidebar and Index Registration

Register all 3 new skills.

1. Add Project_Implement, Project_Evaluate, Project_Fix to Forge/Skills/index.md
2. Add all 3 to the Skills List in Forge/Configs/FORGE.md (alphabetical order)
3. Add sidebar entries in .internal/astro.config.mjs
4. Run cd .internal && npm run build to verify
5. Commit all files together