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

Forge Project Plan 1 — Templates & Foundation

Scope: Create all 7 document templates, the Project_Flow meta-skill, and the Project_Create skill that scaffolds new projects. Spec: Forge Project Spec


Task 1 — Create Document Templates

Templates encode the document structure from the Spec and give agents a starting point for each document type. They live at Forge/Skills/Project_Create/templates/.

Create the folder Forge/Skills/Project_Create/templates/ and populate it with 7 template files. Each template must include:

  • YAML frontmatter with the 6 required fields (status, visibility, owner, approver, created, updated) using placeholder values
  • The human-readable header table matching §5 of the Spec
  • The document structure from §3 of the Spec, with placeholder content and brief inline instructions in {curly braces}

Templates to create:

  1. Requirements_Template.md — Vision/Problem, Background, numbered Requirements (R1, R2…), Success Criteria table (V1, V2…), Out of Scope. Structure from Spec §3.3.

  2. Research_Template.md — Numbered topics, each with Finding, Options, Recommendation, Decision subsections, “Decided by” attribution. Historical/append-only discipline note. Structure from Spec §3.4.

  3. Spec_Template.md — Summary, links to Requirements and Research, numbered major areas with declarative descriptions. Note that it’s declarative not procedural. Structure from Spec §3.5.

  4. Plan_Template.md — Scope, link to Spec, link to prior plan, numbered Tasks each with context quote and procedural steps. Note about frozen-once-implementation-starts. Structure from Spec §3.6.

  5. State_Template.md — Link to related Plan, checkbox todo list derived from Plan tasks. Uses the checkbox conventions from FORGE.md (no prefix = not started, [STARTED], [UNVERIFIED], [BLOCKED], [x]). Structure from Spec §3.7.

  6. Learnings_Template.md — Numbered entries (L1, L2…), each with Context, Obstacle, Resolution, Destination fields. Note that it’s temporary and cleared during evaluation. Structure from Spec §3.8.

  7. WIP_Template.md — Minimal: frontmatter, heading, append-only bullet list. Note that it’s temporary. Structure from Spec §3.9.


Task 2 — Create the Project_Flow Skill

The meta-skill that describes the overall project lifecycle and helps an agent detect where the user is in the process. This is a reference skill, not an action skill.

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

  • When to Use: When starting work on a project, or when uncertain which phase a project is in.
  • Procedure:
    1. List every lifecycle phase in canonical order (Create through Complete) with one-line descriptions
    2. Point to the matching phase skill based on the Status document
  • Rules: Always detect phase before acting. Never skip phases. User approval required between phases.
  • Include the ASCII lifecycle diagram from Spec §1

Task 3 — Create the Project_Create Skill

Skill for Create. Scaffolds a new project folder with README.md, AGENTS.md, and {Project}_Phase.md as the minimum viable project.

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

  • When to Use: When creating a new project.
  • Inputs: Department name, Project name, Owner (email), brief description
  • Procedure:
    1. Create directory {Dept}/Projects/{Project_Name}/
    2. Create README.md with frontmatter, project title, and brief description placeholder
    3. Create AGENTS.md with frontmatter, project description, and sections for: Related Skills, Documents, Knowledge
    4. Add sidebar entries for the new project folder (README and AGENTS) in .internal/astro.config.mjs
    5. Run cd .internal && npm run build to verify
    6. Commit and push
  • Rules:
    • Folder name uses Title_Case_With_Underscores
    • File names are prefixed with the project folder name (e.g., Forge_Project_Requirements.md) except for README.md and AGENTS.md
    • Both files use the 6-field frontmatter convention
    • The templates folder is at Forge/Skills/Project_Create/templates/ — point there for future phases

Task 4 — Sidebar and Index Registration

All new skills must be registered in the sidebar and skills index.

  1. Add Project_Flow and Project_Create to Forge/Skills/index.md
  2. Add Project_Flow and Project_Create to the Skills List in Forge/Configs/FORGE.md under PERSISTENT KNOWLEDGE (alphabetical order)
  3. Add sidebar entries in .internal/astro.config.mjs for:
    • Forge/Skills/Project_Create/SKILL.md
    • Forge/Skills/Project_Create/templates/* (all 7 templates)
    • Forge/Skills/Project_Flow/SKILL.md
  4. Run cd .internal && npm run build to verify no broken slugs
  5. Commit all files together