Skip to content
Uvilo OS
archived Visibility internal Owner erik@uvilo.com Approver _ Created 2026-04-20 Updated 2026-04-20

Forge Project Plan 5 — Revisions

Scope: Revisions to the project lifecycle system identified during Project Check — phase values, naming conventions, diagram updates, skill renames, sidebar reorder, and process corrections. Spec: Forge Project Spec Prior plan: Plan 4 — Completion & Integration

Task 1 — Update Phase Values: Underscores and Cycle Numbers

Phase values currently use PascalCase (CreateStarted) with no cycle tracking. The standard is {Phase}_{Status} with cycle numbers for Implement/Evaluate/Fix: Plan_Started, Implement_1_Started, Evaluate_2_Completed.

Files to update:

  1. Spec §3.3 (Forge_Project_Spec.md) — update the Phase value format from {PhaseName}Started/{PhaseName}Completed to {PhaseName}_{Status} and add cycle number rules for Implement/Evaluate/Fix
  2. Phase_Template.md — change Phase: CreateStarted to Phase: Create_Started
  3. Project_Flow SKILL.md — update every Phase value in the Phase Detection table (e.g. CreateStarted → Create_Started, ImplementStarted → Implement_1_Started)
  4. Project_Create SKILL.md — update Phase: CreateStarted to Phase: Create_Started
  5. Project_Requirements SKILL.md — update Phase: RequirementsStarted / RequirementsCompleted → Requirements_Started / Requirements_Completed
  6. Project_Research SKILL.md — same pattern
  7. Project_Spec SKILL.md — same pattern
  8. Project_Plan SKILL.md (after rename in Task 3) — same pattern
  9. Project_Implement SKILL.md — update to Implement_{N}_Started / Implement_{N}_Completed
  10. Project_Evaluate SKILL.md — update to Evaluate_{N}_Started / Evaluate_{N}_Completed
  11. Project_Fix SKILL.md — update to Fix_{N}_Started / Fix_{N}_Completed
  12. Project_Check SKILL.md — update to Check_Started / Check_Completed
  13. Project_Extract SKILL.md — same pattern
  14. Project_Complete SKILL.md — same pattern

Cycle number rules:

  • The N in Implement_{N}_Started corresponds to the Plan number being implemented (Plan 1 → Implement_1, Plan 2 → Implement_2)
  • Evaluate and Fix use the same N as the Implement they follow
  • If Fix creates new work that requires re-evaluation, the cycle number increments: Evaluate_1_Completed → Fix_1_Completed → Evaluate_2_Started
  • Phases before Implement (Create through Plan) do not use cycle numbers

Task 2 — Numbered Plans Convention

Plans currently use qualifier names like Plan_Authentication. The standard is always numbered: Plan 1, Plan 2, Plan 3. Even a single plan is Plan 1.

Files to update:

  1. Spec §3.7 (Forge_Project_Spec.md) — replace qualifier-based naming (Plan_{Qualifier}) with numbered naming (Plan_{N}): Plan_1, Plan_2, etc.
  2. Plan_Template.md — change title from {Project} Plan {Qualifier} to {Project} Plan {N}
  3. Project_Plan SKILL.md (after rename in Task 3) — update naming instructions: “Number Plans sequentially: Plan 1, Plan 2, etc. Even a single plan is Plan 1.”
  4. Project_Implement SKILL.md — update State file naming from {Project}_State_{Qualifier} to {Project}_State_{N} matching Plan number
  5. Project_Evaluate SKILL.md — update references from “which Plan to evaluate” to use Plan numbers
  6. State_Template.md — update Related plan link format to use Plan number
  7. Project_Flow SKILL.md — update Phase Detection table references to use Plan numbers

Task 3 — Rename Skills

Two skill renames: Project_Create_Plan → Project_Plan and Archive_Project → Project_Archive.

3a. Rename Project_Create_Plan → Project_Plan

  1. git mv Forge/Skills/Project_Create_Plan Forge/Skills/Project_Plan
  2. Update SKILL.md name field: project-create-plan → project-plan
  3. Update title: Project Create Plan → Project Plan
  4. Update description accordingly
  5. Update sidebar in .internal/astro.config.mjs: slug path and label
  6. Update FORGE.md Skills List: Project_Create_Plan → Project_Plan
  7. Update Spec §11 Required Skills table: Project_Create_Plan → Project_Plan
  8. Update Forge/Skills/index.md

3b. Rename Archive_Project → Project_Archive and Undeprecate

  1. git mv Forge/Skills/Archive_Project Forge/Skills/Project_Archive
  2. Rewrite SKILL.md:
    • Remove deprecated status and messaging
    • Set status: published in frontmatter
    • Title: Project Archive
    • Description: “Use when archiving or unarchiving a project after completion”
    • When to Use: When a completed project needs to be archived or an archived project needs to be restored
    • Procedure: Consolidate the archive logic from Project_Complete (setting status to archived, git mv, sidebar updates, Archived index) plus the existing unarchive procedure
    • Keep the existing unarchiving procedure (it’s already good)
    • Reference: “For completing a project (archive/publish/approve), use Project_Complete first”
  3. Update sidebar in .internal/astro.config.mjs: slug path from archive_project to project_archive, label to Project Archive
  4. Update FORGE.md Skills List: Archive_Project *(deprecated)* → Project_Archive
  5. Update Forge/Skills/index.md
  6. Run cd .internal && npm run build to verify

Task 4 — Update Project_Flow

Three issues: diagram doesn’t include Plan phase, diagram should be Mermaid, Phase Detection table needs reformatted values.

  1. Replace the ASCII lifecycle diagram with a Mermaid diagram that matches the Spec §1 diagram (which correctly includes Plan phase)
  2. Update the Phase Detection table:
    • Use underscored phase values: Create_Started, Plan_Started, Implement_1_Started, etc.
    • Reformat Phase column from 1 (Create) — in progress to 1. Create — in progress
    • Include cycle numbers in Implement/Evaluate/Fix rows
  3. Update the name field from project-create-plan references to project-plan
  4. Run cd .internal && npm run build to verify

Task 5 — Move Learnings Incorporation from Evaluate to Fix

Project_Evaluate currently incorporates Learnings into permanent docs and clears the file. This work belongs in Project_Fix. Evaluate should only note which Learnings need incorporation.

  1. Project_Evaluate SKILL.md:

    • Replace step 7 (“Incorporate Learnings entries into permanent documents per their Destination field, then clear the Learnings file”) with: “Note which Learnings entries need incorporation into permanent documents (per their Destination field). This work is done in Project_Fix.”
    • Remove the rule “Learnings must be cleared by Evaluate”

  2. Project_Fix SKILL.md:

    • Add a new step after implementing fixes: “Incorporate Learnings entries into permanent documents per their Destination field, then clear the Learnings file”
    • Add rule: “Learnings must be cleared by Fix after incorporation — nothing stays in the temporary file”

  3. Spec §6.1 (Forge_Project_Spec.md): Update step 7 of Evaluate to match — note Learnings for incorporation instead of doing the work. Add step in Fix procedure for incorporation.

Task 6 — Update Project_Complete: Add “Approved” Outcome

Project_Complete currently offers only archive or publish. Adding a third option: approved (not published, not archived).

  1. Project_Complete SKILL.md:

    • Update “When to Use” and procedure to include three options
    • Add step for If Approve:
      • Set status: approved on all .md files
      • Keep project in {Dept}/Projects/
    • Update the user confirmation step to present three choices

  2. Spec §7 (Forge_Project_Spec.md): Add “Approve” row to the completion table: | Approve | Set status to approved, keep in Projects/ | Projects that are complete but not yet ready for publication or archiving |

  3. Spec §5 Status values table: Add approved if not already present (it is — Reviewed and accepted)

Task 7 — Update Project_Check: Changes, Plan Threshold, and Deduplication

Three additions to Project_Check: “Change” finding type, Plan creation threshold (>5 items), and deduplication rule.

  1. Project_Check SKILL.md:

    • Add Change to the findings report categories: “Change — user-requested modification that may affect Requirements, Spec, or implementation”
    • Add rule: “If findings exceed 5 items, create a new Plan by default rather than implementing fixes directly”
    • Add deduplication rule: “Deduplicate findings — when the same issue appears as both a Defect/Variance and a Change, report it once under the most specific category. For example, a defect identified by the user as a change is reported as a Change only.”
    • Update user disposition options to include Change-specific handling: Changes may require updating Requirements, Spec, or just implementation

  2. Spec §6.2 (Forge_Project_Spec.md): Update Check evaluation categories to include Change.

Task 8 — Rename “Deviation” → “Variance”

Deviation and Defect both start with “D”, making abbreviations ambiguous. Rename Deviation to Variance throughout.

  1. Project_Check SKILL.md — replace “Deviation” with “Variance”
  2. Project_Evaluate SKILL.md — replace “Deviation” with “Variance”
  3. Spec §6.1 and §6.2 (Forge_Project_Spec.md) — replace all instances
  4. Project_Flow SKILL.md — if referenced
  5. Project_Fix SKILL.md — if referenced

Task 9 — Reorder Project Skills in Sidebar

Project skills in the sidebar are currently alphabetical. They should be in phase order.

Update .internal/astro.config.mjs to reorder the project skill sidebar entries to:

  1. Project Flow
  2. Project Create (with Templates sub-items)
  3. Project Requirements
  4. Project Research
  5. Project Spec
  6. Project Plan (after rename from Project Create Plan)
  7. Project Implement
  8. Project Evaluate
  9. Project Fix
  10. Project Check
  11. Project Extract
  12. Project Complete
  13. Project Archive (after rename from Archive Project)
  14. Project Rename

Run cd .internal && npm run build to verify.

Task 10 — Update Spec and Requirements

Reflect all changes in the Spec and Requirements documents.

  1. Spec (Forge_Project_Spec.md): All changes from Tasks 1–8 that affect the Spec (phase values, numbered plans, Variance rename, Complete outcomes, Check categories, Learnings flow, Required Skills table)
  2. Requirements (Forge_Project_Requirements.md): Update R4 (evaluation protocol) for Variance rename and Learnings flow change. Update R6 (completion) for approved option. Update R7 (skills) for renamed skills (13 skills now: Project_Plan instead of Project_Create_Plan, Project_Archive instead of Archive_Project). Update V6 for 13 skills.

Task 11 — Update FORGE.md and Index

Update the system-level references.

  1. FORGE.md Skills List — update: remove Archive_Project *(deprecated)*, add Project_Archive; rename Project_Create_Plan to Project_Plan
  2. Forge/Skills/index.md — update skill entries for renamed skills
  3. Run cd .internal && npm run build to verify everything

Task 12 — Build Verification and Commit

Final verification that all changes work together.

  1. cd .internal && npm run build — verify no broken slugs
  2. Verify all 13 project skills exist and are internally consistent
  3. Verify sidebar order matches phase order
  4. Verify Spec and Requirements reflect all changes
  5. Commit all changes