# templates/

Templates copied into user projects by `npx @jamie-tam/forge init`, plus schema docs used internally by forge maintainers.

## User-installed templates

Installed into the target project by `npx @jamie-tam/forge init` (or kept in-sync by subsequent updates). These are the files real users of forge see.

- **`manifests/`** — Canonical work-manifest templates, one per work type (`feature.yaml`, `greenfield.yaml`, `bugfix.yaml`, `hotfix.yaml`, `refactor.yaml`). Written to `.forge/work/{type}/{name}/manifest.yaml` when a work command starts. Each manifest is the source of truth for its schema shape — do not duplicate schema documentation elsewhere.
- **`aiwiki/`** — Seed contents for the project's `aiwiki/` directory: the `CLAUDE.md.template` that auto-loads wiki usage rules, plus the `schemas/` folder defining the file shape for conventions, gotchas, architecture, decisions, and sessions.
- **`wiki-html/`** — Single-file HTML pages (e.g. `dreams-list.html`, `dream-detail.html`) used by the wiki review UI surfaced via the forge CLI.

## Legacy

Kept on-disk so older manifests still parse and so `/forge-evolve` can migrate them forward. Not installed into new projects.

- **`manifests/v5/`** — v5 schema (`SCHEMA.md` plus a `feature.yaml` reference). v5 manifests still parse against the v6 reader (see `manifests/v6/SCHEMA.md` §4). v4 manifests also still parse but no template is retained — the reader synthesizes the missing fields.

## Internal

Used by forge maintainers writing the parser/verifier and the migration logic. Not consumed at user runtime.

- **`manifests/v6/SCHEMA.md`** — Source of truth for v6 manifest validation rules. The reader and verifier in `src/work-manifest.ts` implement against this document. v6's delta over v5 is the additive `phase_plan:` block (see §3). Update this file alongside any change to manifest shape or allowed plan-status values.