From 87742e76d866fdb1100b842147ac40695ba21294 Mon Sep 17 00:00:00 2001
From: MerlinH <merlinh221@gmail.com>
Date: Wed, 17 Jun 2026 20:19:36 +0000
Subject: [PATCH] feat: expand Open Game Studio Codex depth

Add OpenSpec-backed catch-up passes for role coverage, workflow catalog, engine references, production templates, role prompt depth, behavioral validation, and project-local customization.

Ship expanded Codex-native scaffolding, role/workflow/template registries, engine reference assets, deterministic validation scenarios, customization pack support, routed Truthmark docs, OpenSpec artifacts, and regression coverage.
---
 .codex/skills/openspec-apply-change/SKILL.md  | 156 +++++++
 .../skills/openspec-archive-change/SKILL.md   | 114 +++++
 .codex/skills/openspec-explore/SKILL.md       | 288 ++++++++++++
 .codex/skills/openspec-propose/SKILL.md       | 110 +++++
 docs/system-verification.md                   |   1 +
 .../engineering/codex/roles-and-workflows.md  |  48 +-
 .../engineering/codex/runtime-and-tasks.md    |  11 +-
 .../contracts/cli-and-validation.md           |  29 +-
 .../projects/project-scaffolding.md           |   4 +-
 .../engineering/repository/overview.md        |   2 +-
 .../truthmark/product/open-game-studio-cli.md |   6 +-
 docs/truthmark/routes/areas/repository.md     |  12 +-
 docs/workflow-validation.md                   |   8 +-
 engine_reference/godot/VERSION.md             |  44 +-
 engine_reference/godot/breaking-changes.md    |  26 ++
 .../godot/current-best-practices.md           |  27 ++
 engine_reference/godot/deprecated-apis.md     |  26 ++
 engine_reference/godot/gameplay.md            |  46 +-
 engine_reference/godot/modules/animation.md   |  26 ++
 engine_reference/godot/modules/audio.md       |  26 ++
 engine_reference/godot/modules/input.md       |  26 ++
 engine_reference/godot/modules/navigation.md  |  26 ++
 engine_reference/godot/modules/networking.md  |  26 ++
 engine_reference/godot/modules/physics.md     |  26 ++
 engine_reference/godot/modules/rendering.md   |  26 ++
 engine_reference/godot/modules/ui.md          |  26 ++
 engine_reference/godot/plugins.md             |  45 +-
 engine_reference/godot/specialist.md          |  41 +-
 engine_reference/unity/VERSION.md             |  41 +-
 engine_reference/unity/breaking-changes.md    |  26 ++
 .../unity/current-best-practices.md           |  27 ++
 engine_reference/unity/deprecated-apis.md     |  26 ++
 engine_reference/unity/gameplay.md            |  46 +-
 engine_reference/unity/modules/animation.md   |  26 ++
 engine_reference/unity/modules/audio.md       |  26 ++
 engine_reference/unity/modules/input.md       |  26 ++
 engine_reference/unity/modules/navigation.md  |  26 ++
 engine_reference/unity/modules/networking.md  |  26 ++
 engine_reference/unity/modules/physics.md     |  26 ++
 engine_reference/unity/modules/rendering.md   |  26 ++
 engine_reference/unity/modules/ui.md          |  26 ++
 engine_reference/unity/plugins.md             |  44 +-
 .../unity/plugins/addressables.md             |  26 ++
 engine_reference/unity/plugins/cinemachine.md |  26 ++
 engine_reference/unity/plugins/dots.md        |  26 ++
 engine_reference/unity/specialist.md          |  41 +-
 engine_reference/unreal/VERSION.md            |  43 +-
 engine_reference/unreal/breaking-changes.md   |  26 ++
 .../unreal/current-best-practices.md          |  27 ++
 engine_reference/unreal/deprecated-apis.md    |  26 ++
 engine_reference/unreal/gameplay.md           |  46 +-
 engine_reference/unreal/modules/animation.md  |  26 ++
 engine_reference/unreal/modules/audio.md      |  26 ++
 engine_reference/unreal/modules/input.md      |  26 ++
 engine_reference/unreal/modules/navigation.md |  26 ++
 engine_reference/unreal/modules/networking.md |  26 ++
 engine_reference/unreal/modules/physics.md    |  26 ++
 engine_reference/unreal/modules/rendering.md  |  26 ++
 engine_reference/unreal/modules/ui.md         |  26 ++
 engine_reference/unreal/plugins.md            |  44 +-
 engine_reference/unreal/plugins/common-ui.md  |  26 ++
 engine_reference/unreal/plugins/gas.md        |  26 ++
 engine_reference/unreal/plugins/pcg.md        |  26 ++
 engine_reference/unreal/specialist.md         |  43 +-
 .../.openspec.yaml                            |   2 +
 .../catch-up-behavioral-evaluation/README.md  |   3 +
 .../catch-up-behavioral-evaluation/design.md  |  32 ++
 .../proposal.md                               |  30 ++
 .../spec.md                                   |  30 ++
 .../catch-up-behavioral-evaluation/tasks.md   |  29 ++
 .../.openspec.yaml                            |   2 +
 .../README.md                                 |   3 +
 .../design.md                                 |  35 ++
 .../proposal.md                               |  30 ++
 .../spec.md                                   |  30 ++
 .../tasks.md                                  |  29 ++
 .../.openspec.yaml                            |   2 +
 .../catch-up-domain-role-coverage/README.md   |   3 +
 .../catch-up-domain-role-coverage/design.md   |  33 ++
 .../catch-up-domain-role-coverage/proposal.md |  29 ++
 .../codex-studio-domain-role-coverage/spec.md |  30 ++
 .../catch-up-domain-role-coverage/tasks.md    |  28 ++
 .../.openspec.yaml                            |   2 +
 .../catch-up-engine-reference-depth/README.md |   3 +
 .../catch-up-engine-reference-depth/design.md |  33 ++
 .../proposal.md                               |  30 ++
 .../spec.md                                   |  30 ++
 .../catch-up-engine-reference-depth/tasks.md  |  29 ++
 .../.openspec.yaml                            |   2 +
 .../catch-up-production-templates/README.md   |   3 +
 .../catch-up-production-templates/design.md   |  33 ++
 .../catch-up-production-templates/proposal.md |  29 ++
 .../spec.md                                   |  30 ++
 .../catch-up-production-templates/tasks.md    |  28 ++
 .../catch-up-role-prompt-depth/.openspec.yaml |   2 +
 .../catch-up-role-prompt-depth/README.md      |   3 +
 .../catch-up-role-prompt-depth/design.md      |  33 ++
 .../catch-up-role-prompt-depth/proposal.md    |  29 ++
 .../codex-studio-role-prompt-depth/spec.md    |  30 ++
 .../catch-up-role-prompt-depth/tasks.md       |  28 ++
 .../.openspec.yaml                            |   2 +
 .../catch-up-workflow-skill-catalog/README.md |   3 +
 .../catch-up-workflow-skill-catalog/design.md |  34 ++
 .../proposal.md                               |  29 ++
 .../codex-studio-workflow-catalog/spec.md     |  30 ++
 .../catch-up-workflow-skill-catalog/tasks.md  |  28 ++
 openspec/config.yaml                          |  20 +
 ...-17-catch-up-behavioral-evaluation-plan.md |  64 +++
 ...-catch-up-customization-ergonomics-plan.md |  64 +++
 ...6-17-catch-up-domain-role-coverage-plan.md |  63 +++
 ...17-catch-up-engine-reference-depth-plan.md |  64 +++
 ...6-17-catch-up-production-templates-plan.md |  63 +++
 ...6-06-17-catch-up-role-prompt-depth-plan.md |  63 +++
 ...17-catch-up-workflow-skill-catalog-plan.md |  63 +++
 src/agents.ts                                 |  25 +-
 src/behavioral-evaluation.ts                  | 213 +++++++++
 src/cli.ts                                    |  41 +-
 src/codex-prompts.ts                          |   5 +-
 src/config.ts                                 |  39 +-
 src/customization.ts                          | 278 +++++++++++
 src/engine-reference.ts                       | 121 ++++-
 src/projects.ts                               |  20 +-
 src/roles.ts                                  | 276 ++++++++++-
 src/runner.ts                                 |  87 +++-
 src/templates.ts                              | 311 +++++++++++--
 src/validation.ts                             |  18 +-
 src/workflows.ts                              | 432 +++++++++++++++---
 .../accessibility_requirements_template.md    |  15 +
 templates/adr_template.md                     |  15 +
 .../architecture_traceability_template.md     |  15 +
 templates/art_bible_template.md               |  15 +
 templates/difficulty_curve_template.md        |  15 +
 templates/economy_model_template.md           |  15 +
 templates/pitch_document_template.md          |  15 +
 templates/player_journey_template.md          |  15 +
 templates/postmortem_template.md              |  15 +
 templates/release_notes_template.md           |  15 +
 templates/risk_register_template.md           |  15 +
 templates/sound_bible_template.md             |  15 +
 templates/sprint_plan_template.md             |  15 +
 templates/technical_design_template.md        |  15 +
 templates/test_evidence_template.md           |  15 +
 templates/test_plan_template.md               |  15 +
 templates/ux_spec_template.md                 |  15 +
 templates/vertical_slice_report_template.md   |  15 +
 tests/agents-templates.test.ts                |  62 ++-
 tests/behavioral-evaluation.test.ts           |  66 +++
 tests/codex-context-files.test.ts             |  17 +
 tests/codex-prompts.test.ts                   |  31 ++
 tests/customization.test.ts                   | 134 ++++++
 tests/engine-system.test.ts                   |  29 +-
 tests/functionality-gap-pass.test.ts          | 169 ++++++-
 tests/roles.test.ts                           |  64 +++
 tests/validation.test.ts                      |  13 +-
 154 files changed, 5882 insertions(+), 516 deletions(-)
 create mode 100644 .codex/skills/openspec-apply-change/SKILL.md
 create mode 100644 .codex/skills/openspec-archive-change/SKILL.md
 create mode 100644 .codex/skills/openspec-explore/SKILL.md
 create mode 100644 .codex/skills/openspec-propose/SKILL.md
 create mode 100644 engine_reference/godot/breaking-changes.md
 create mode 100644 engine_reference/godot/current-best-practices.md
 create mode 100644 engine_reference/godot/deprecated-apis.md
 create mode 100644 engine_reference/godot/modules/animation.md
 create mode 100644 engine_reference/godot/modules/audio.md
 create mode 100644 engine_reference/godot/modules/input.md
 create mode 100644 engine_reference/godot/modules/navigation.md
 create mode 100644 engine_reference/godot/modules/networking.md
 create mode 100644 engine_reference/godot/modules/physics.md
 create mode 100644 engine_reference/godot/modules/rendering.md
 create mode 100644 engine_reference/godot/modules/ui.md
 create mode 100644 engine_reference/unity/breaking-changes.md
 create mode 100644 engine_reference/unity/current-best-practices.md
 create mode 100644 engine_reference/unity/deprecated-apis.md
 create mode 100644 engine_reference/unity/modules/animation.md
 create mode 100644 engine_reference/unity/modules/audio.md
 create mode 100644 engine_reference/unity/modules/input.md
 create mode 100644 engine_reference/unity/modules/navigation.md
 create mode 100644 engine_reference/unity/modules/networking.md
 create mode 100644 engine_reference/unity/modules/physics.md
 create mode 100644 engine_reference/unity/modules/rendering.md
 create mode 100644 engine_reference/unity/modules/ui.md
 create mode 100644 engine_reference/unity/plugins/addressables.md
 create mode 100644 engine_reference/unity/plugins/cinemachine.md
 create mode 100644 engine_reference/unity/plugins/dots.md
 create mode 100644 engine_reference/unreal/breaking-changes.md
 create mode 100644 engine_reference/unreal/current-best-practices.md
 create mode 100644 engine_reference/unreal/deprecated-apis.md
 create mode 100644 engine_reference/unreal/modules/animation.md
 create mode 100644 engine_reference/unreal/modules/audio.md
 create mode 100644 engine_reference/unreal/modules/input.md
 create mode 100644 engine_reference/unreal/modules/navigation.md
 create mode 100644 engine_reference/unreal/modules/networking.md
 create mode 100644 engine_reference/unreal/modules/physics.md
 create mode 100644 engine_reference/unreal/modules/rendering.md
 create mode 100644 engine_reference/unreal/modules/ui.md
 create mode 100644 engine_reference/unreal/plugins/common-ui.md
 create mode 100644 engine_reference/unreal/plugins/gas.md
 create mode 100644 engine_reference/unreal/plugins/pcg.md
 create mode 100644 openspec/changes/catch-up-behavioral-evaluation/.openspec.yaml
 create mode 100644 openspec/changes/catch-up-behavioral-evaluation/README.md
 create mode 100644 openspec/changes/catch-up-behavioral-evaluation/design.md
 create mode 100644 openspec/changes/catch-up-behavioral-evaluation/proposal.md
 create mode 100644 openspec/changes/catch-up-behavioral-evaluation/specs/codex-studio-behavioral-evaluation/spec.md
 create mode 100644 openspec/changes/catch-up-behavioral-evaluation/tasks.md
 create mode 100644 openspec/changes/catch-up-customization-ergonomics/.openspec.yaml
 create mode 100644 openspec/changes/catch-up-customization-ergonomics/README.md
 create mode 100644 openspec/changes/catch-up-customization-ergonomics/design.md
 create mode 100644 openspec/changes/catch-up-customization-ergonomics/proposal.md
 create mode 100644 openspec/changes/catch-up-customization-ergonomics/specs/codex-studio-customization-ergonomics/spec.md
 create mode 100644 openspec/changes/catch-up-customization-ergonomics/tasks.md
 create mode 100644 openspec/changes/catch-up-domain-role-coverage/.openspec.yaml
 create mode 100644 openspec/changes/catch-up-domain-role-coverage/README.md
 create mode 100644 openspec/changes/catch-up-domain-role-coverage/design.md
 create mode 100644 openspec/changes/catch-up-domain-role-coverage/proposal.md
 create mode 100644 openspec/changes/catch-up-domain-role-coverage/specs/codex-studio-domain-role-coverage/spec.md
 create mode 100644 openspec/changes/catch-up-domain-role-coverage/tasks.md
 create mode 100644 openspec/changes/catch-up-engine-reference-depth/.openspec.yaml
 create mode 100644 openspec/changes/catch-up-engine-reference-depth/README.md
 create mode 100644 openspec/changes/catch-up-engine-reference-depth/design.md
 create mode 100644 openspec/changes/catch-up-engine-reference-depth/proposal.md
 create mode 100644 openspec/changes/catch-up-engine-reference-depth/specs/codex-studio-engine-reference-depth/spec.md
 create mode 100644 openspec/changes/catch-up-engine-reference-depth/tasks.md
 create mode 100644 openspec/changes/catch-up-production-templates/.openspec.yaml
 create mode 100644 openspec/changes/catch-up-production-templates/README.md
 create mode 100644 openspec/changes/catch-up-production-templates/design.md
 create mode 100644 openspec/changes/catch-up-production-templates/proposal.md
 create mode 100644 openspec/changes/catch-up-production-templates/specs/codex-studio-production-template-pack/spec.md
 create mode 100644 openspec/changes/catch-up-production-templates/tasks.md
 create mode 100644 openspec/changes/catch-up-role-prompt-depth/.openspec.yaml
 create mode 100644 openspec/changes/catch-up-role-prompt-depth/README.md
 create mode 100644 openspec/changes/catch-up-role-prompt-depth/design.md
 create mode 100644 openspec/changes/catch-up-role-prompt-depth/proposal.md
 create mode 100644 openspec/changes/catch-up-role-prompt-depth/specs/codex-studio-role-prompt-depth/spec.md
 create mode 100644 openspec/changes/catch-up-role-prompt-depth/tasks.md
 create mode 100644 openspec/changes/catch-up-workflow-skill-catalog/.openspec.yaml
 create mode 100644 openspec/changes/catch-up-workflow-skill-catalog/README.md
 create mode 100644 openspec/changes/catch-up-workflow-skill-catalog/design.md
 create mode 100644 openspec/changes/catch-up-workflow-skill-catalog/proposal.md
 create mode 100644 openspec/changes/catch-up-workflow-skill-catalog/specs/codex-studio-workflow-catalog/spec.md
 create mode 100644 openspec/changes/catch-up-workflow-skill-catalog/tasks.md
 create mode 100644 openspec/config.yaml
 create mode 100644 research/2026-06-17-catch-up-behavioral-evaluation-plan.md
 create mode 100644 research/2026-06-17-catch-up-customization-ergonomics-plan.md
 create mode 100644 research/2026-06-17-catch-up-domain-role-coverage-plan.md
 create mode 100644 research/2026-06-17-catch-up-engine-reference-depth-plan.md
 create mode 100644 research/2026-06-17-catch-up-production-templates-plan.md
 create mode 100644 research/2026-06-17-catch-up-role-prompt-depth-plan.md
 create mode 100644 research/2026-06-17-catch-up-workflow-skill-catalog-plan.md
 create mode 100644 src/behavioral-evaluation.ts
 create mode 100644 src/customization.ts
 create mode 100644 templates/accessibility_requirements_template.md
 create mode 100644 templates/adr_template.md
 create mode 100644 templates/architecture_traceability_template.md
 create mode 100644 templates/art_bible_template.md
 create mode 100644 templates/difficulty_curve_template.md
 create mode 100644 templates/economy_model_template.md
 create mode 100644 templates/pitch_document_template.md
 create mode 100644 templates/player_journey_template.md
 create mode 100644 templates/postmortem_template.md
 create mode 100644 templates/release_notes_template.md
 create mode 100644 templates/risk_register_template.md
 create mode 100644 templates/sound_bible_template.md
 create mode 100644 templates/sprint_plan_template.md
 create mode 100644 templates/technical_design_template.md
 create mode 100644 templates/test_evidence_template.md
 create mode 100644 templates/test_plan_template.md
 create mode 100644 templates/ux_spec_template.md
 create mode 100644 templates/vertical_slice_report_template.md
 create mode 100644 tests/behavioral-evaluation.test.ts
 create mode 100644 tests/customization.test.ts

diff --git a/.codex/skills/openspec-apply-change/SKILL.md b/.codex/skills/openspec-apply-change/SKILL.md
new file mode 100644
index 0000000..70fbdb8
--- /dev/null
+++ b/.codex/skills/openspec-apply-change/SKILL.md
@@ -0,0 +1,156 @@
+---
+name: openspec-apply-change
+description: Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+  author: openspec
+  version: "1.0"
+  generatedBy: "1.3.1"
+---
+
+Implement tasks from an OpenSpec change.
+
+**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **Select the change**
+
+   If a name is provided, use it. Otherwise:
+   - Infer from conversation context if the user mentioned a change
+   - Auto-select if only one active change exists
+   - If ambiguous, run `openspec list --json` to get available changes and use the **AskUserQuestion tool** to let the user select
+
+   Always announce: "Using change: <name>" and how to override (e.g., `/opsx:apply <other>`).
+
+2. **Check status to understand the schema**
+   ```bash
+   openspec status --change "<name>" --json
+   ```
+   Parse the JSON to understand:
+   - `schemaName`: The workflow being used (e.g., "spec-driven")
+   - Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others)
+
+3. **Get apply instructions**
+
+   ```bash
+   openspec instructions apply --change "<name>" --json
+   ```
+
+   This returns:
+   - `contextFiles`: artifact ID -> array of concrete file paths (varies by schema - could be proposal/specs/design/tasks or spec/tests/implementation/docs)
+   - Progress (total, complete, remaining)
+   - Task list with status
+   - Dynamic instruction based on current state
+
+   **Handle states:**
+   - If `state: "blocked"` (missing artifacts): show message, suggest using openspec-continue-change
+   - If `state: "all_done"`: congratulate, suggest archive
+   - Otherwise: proceed to implementation
+
+4. **Read context files**
+
+   Read every file path listed under `contextFiles` from the apply instructions output.
+   The files depend on the schema being used:
+   - **spec-driven**: proposal, specs, design, tasks
+   - Other schemas: follow the contextFiles from CLI output
+
+5. **Show current progress**
+
+   Display:
+   - Schema being used
+   - Progress: "N/M tasks complete"
+   - Remaining tasks overview
+   - Dynamic instruction from CLI
+
+6. **Implement tasks (loop until done or blocked)**
+
+   For each pending task:
+   - Show which task is being worked on
+   - Make the code changes required
+   - Keep changes minimal and focused
+   - Mark task complete in the tasks file: `- [ ]` → `- [x]`
+   - Continue to next task
+
+   **Pause if:**
+   - Task is unclear → ask for clarification
+   - Implementation reveals a design issue → suggest updating artifacts
+   - Error or blocker encountered → report and wait for guidance
+   - User interrupts
+
+7. **On completion or pause, show status**
+
+   Display:
+   - Tasks completed this session
+   - Overall progress: "N/M tasks complete"
+   - If all done: suggest archive
+   - If paused: explain why and wait for guidance
+
+**Output During Implementation**
+
+```
+## Implementing: <change-name> (schema: <schema-name>)
+
+Working on task 3/7: <task description>
+[...implementation happening...]
+✓ Task complete
+
+Working on task 4/7: <task description>
+[...implementation happening...]
+✓ Task complete
+```
+
+**Output On Completion**
+
+```
+## Implementation Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 7/7 tasks complete ✓
+
+### Completed This Session
+- [x] Task 1
+- [x] Task 2
+...
+
+All tasks complete! Ready to archive this change.
+```
+
+**Output On Pause (Issue Encountered)**
+
+```
+## Implementation Paused
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 4/7 tasks complete
+
+### Issue Encountered
+<description of the issue>
+
+**Options:**
+1. <option 1>
+2. <option 2>
+3. Other approach
+
+What would you like to do?
+```
+
+**Guardrails**
+- Keep going through tasks until done or blocked
+- Always read context files before starting (from the apply instructions output)
+- If task is ambiguous, pause and ask before implementing
+- If implementation reveals issues, pause and suggest artifact updates
+- Keep code changes minimal and scoped to each task
+- Update task checkbox immediately after completing each task
+- Pause on errors, blockers, or unclear requirements - don't guess
+- Use contextFiles from CLI output, don't assume specific file names
+
+**Fluid Workflow Integration**
+
+This skill supports the "actions on a change" model:
+
+- **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation, interleaved with other actions
+- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly
diff --git a/.codex/skills/openspec-archive-change/SKILL.md b/.codex/skills/openspec-archive-change/SKILL.md
new file mode 100644
index 0000000..12e2f70
--- /dev/null
+++ b/.codex/skills/openspec-archive-change/SKILL.md
@@ -0,0 +1,114 @@
+---
+name: openspec-archive-change
+description: Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+  author: openspec
+  version: "1.0"
+  generatedBy: "1.3.1"
+---
+
+Archive a completed change in the experimental workflow.
+
+**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **If no change name provided, prompt for selection**
+
+   Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+
+   Show only active changes (not already archived).
+   Include the schema used for each change if available.
+
+   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Check artifact completion status**
+
+   Run `openspec status --change "<name>" --json` to check artifact completion.
+
+   Parse the JSON to understand:
+   - `schemaName`: The workflow being used
+   - `artifacts`: List of artifacts with their status (`done` or other)
+
+   **If any artifacts are not `done`:**
+   - Display warning listing incomplete artifacts
+   - Use **AskUserQuestion tool** to confirm user wants to proceed
+   - Proceed if user confirms
+
+3. **Check task completion status**
+
+   Read the tasks file (typically `tasks.md`) to check for incomplete tasks.
+
+   Count tasks marked with `- [ ]` (incomplete) vs `- [x]` (complete).
+
+   **If incomplete tasks found:**
+   - Display warning showing count of incomplete tasks
+   - Use **AskUserQuestion tool** to confirm user wants to proceed
+   - Proceed if user confirms
+
+   **If no tasks file exists:** Proceed without task-related warning.
+
+4. **Assess delta spec sync state**
+
+   Check for delta specs at `openspec/changes/<name>/specs/`. If none exist, proceed without sync prompt.
+
+   **If delta specs exist:**
+   - Compare each delta spec with its corresponding main spec at `openspec/specs/<capability>/spec.md`
+   - Determine what changes would be applied (adds, modifications, removals, renames)
+   - Show a combined summary before prompting
+
+   **Prompt options:**
+   - If changes needed: "Sync now (recommended)", "Archive without syncing"
+   - If already synced: "Archive now", "Sync anyway", "Cancel"
+
+   If user chooses sync, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke openspec-sync-specs for change '<name>'. Delta spec analysis: <include the analyzed delta spec summary>"). Proceed to archive regardless of choice.
+
+5. **Perform the archive**
+
+   Create the archive directory if it doesn't exist:
+   ```bash
+   mkdir -p openspec/changes/archive
+   ```
+
+   Generate target name using current date: `YYYY-MM-DD-<change-name>`
+
+   **Check if target already exists:**
+   - If yes: Fail with error, suggest renaming existing archive or using different date
+   - If no: Move the change directory to archive
+
+   ```bash
+   mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>
+   ```
+
+6. **Display summary**
+
+   Show archive completion summary including:
+   - Change name
+   - Schema that was used
+   - Archive location
+   - Whether specs were synced (if applicable)
+   - Note about any warnings (incomplete artifacts/tasks)
+
+**Output On Success**
+
+```
+## Archive Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Specs:** ✓ Synced to main specs (or "No delta specs" or "Sync skipped")
+
+All artifacts complete. All tasks complete.
+```
+
+**Guardrails**
+- Always prompt for change selection if not provided
+- Use artifact graph (openspec status --json) for completion checking
+- Don't block archive on warnings - just inform and confirm
+- Preserve .openspec.yaml when moving to archive (it moves with the directory)
+- Show clear summary of what happened
+- If sync is requested, use openspec-sync-specs approach (agent-driven)
+- If delta specs exist, always run the sync assessment and show the combined summary before prompting
diff --git a/.codex/skills/openspec-explore/SKILL.md b/.codex/skills/openspec-explore/SKILL.md
new file mode 100644
index 0000000..6858d3f
--- /dev/null
+++ b/.codex/skills/openspec-explore/SKILL.md
@@ -0,0 +1,288 @@
+---
+name: openspec-explore
+description: Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+  author: openspec
+  version: "1.0"
+  generatedBy: "1.3.1"
+---
+
+Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.
+
+**IMPORTANT: Explore mode is for thinking, not implementing.** You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit explore mode first and create a change proposal. You MAY create OpenSpec artifacts (proposals, designs, specs) if the user asks—that's capturing thinking, not implementing.
+
+**This is a stance, not a workflow.** There are no fixed steps, no required sequence, no mandatory outputs. You're a thinking partner helping the user explore.
+
+---
+
+## The Stance
+
+- **Curious, not prescriptive** - Ask questions that emerge naturally, don't follow a script
+- **Open threads, not interrogations** - Surface multiple interesting directions and let the user follow what resonates. Don't funnel them through a single path of questions.
+- **Visual** - Use ASCII diagrams liberally when they'd help clarify thinking
+- **Adaptive** - Follow interesting threads, pivot when new information emerges
+- **Patient** - Don't rush to conclusions, let the shape of the problem emerge
+- **Grounded** - Explore the actual codebase when relevant, don't just theorize
+
+---
+
+## What You Might Do
+
+Depending on what the user brings, you might:
+
+**Explore the problem space**
+- Ask clarifying questions that emerge from what they said
+- Challenge assumptions
+- Reframe the problem
+- Find analogies
+
+**Investigate the codebase**
+- Map existing architecture relevant to the discussion
+- Find integration points
+- Identify patterns already in use
+- Surface hidden complexity
+
+**Compare options**
+- Brainstorm multiple approaches
+- Build comparison tables
+- Sketch tradeoffs
+- Recommend a path (if asked)
+
+**Visualize**
+```
+┌─────────────────────────────────────────┐
+│     Use ASCII diagrams liberally        │
+├─────────────────────────────────────────┤
+│                                         │
+│      ┌────────┐         ┌────────┐      │
+│      │ State  │────────▶│ State  │      │
+│      │   A    │         │   B    │      │
+│      └────────┘         └────────┘      │
+│                                         │
+│   System diagrams, state machines,      │
+│   data flows, architecture sketches,    │
+│   dependency graphs, comparison tables  │
+│                                         │
+└─────────────────────────────────────────┘
+```
+
+**Surface risks and unknowns**
+- Identify what could go wrong
+- Find gaps in understanding
+- Suggest spikes or investigations
+
+---
+
+## OpenSpec Awareness
+
+You have full context of the OpenSpec system. Use it naturally, don't force it.
+
+### Check for context
+
+At the start, quickly check what exists:
+```bash
+openspec list --json
+```
+
+This tells you:
+- If there are active changes
+- Their names, schemas, and status
+- What the user might be working on
+
+### When no change exists
+
+Think freely. When insights crystallize, you might offer:
+
+- "This feels solid enough to start a change. Want me to create a proposal?"
+- Or keep exploring - no pressure to formalize
+
+### When a change exists
+
+If the user mentions a change or you detect one is relevant:
+
+1. **Read existing artifacts for context**
+   - `openspec/changes/<name>/proposal.md`
+   - `openspec/changes/<name>/design.md`
+   - `openspec/changes/<name>/tasks.md`
+   - etc.
+
+2. **Reference them naturally in conversation**
+   - "Your design mentions using Redis, but we just realized SQLite fits better..."
+   - "The proposal scopes this to premium users, but we're now thinking everyone..."
+
+3. **Offer to capture when decisions are made**
+
+    | Insight Type               | Where to Capture               |
+    |----------------------------|--------------------------------|
+    | New requirement discovered | `specs/<capability>/spec.md` |
+    | Requirement changed        | `specs/<capability>/spec.md` |
+    | Design decision made       | `design.md`                  |
+    | Scope changed              | `proposal.md`                |
+    | New work identified        | `tasks.md`                   |
+    | Assumption invalidated     | Relevant artifact              |
+
+   Example offers:
+   - "That's a design decision. Capture it in design.md?"
+   - "This is a new requirement. Add it to specs?"
+   - "This changes scope. Update the proposal?"
+
+4. **The user decides** - Offer and move on. Don't pressure. Don't auto-capture.
+
+---
+
+## What You Don't Have To Do
+
+- Follow a script
+- Ask the same questions every time
+- Produce a specific artifact
+- Reach a conclusion
+- Stay on topic if a tangent is valuable
+- Be brief (this is thinking time)
+
+---
+
+## Handling Different Entry Points
+
+**User brings a vague idea:**
+```
+User: I'm thinking about adding real-time collaboration
+
+You: Real-time collab is a big space. Let me think about this...
+
+      COLLABORATION SPECTRUM
+      ════════════════════════════════════════════
+
+      Awareness          Coordination         Sync
+          │                   │                 │
+          ▼                   ▼                 ▼
+      ┌────────┐         ┌────────┐        ┌────────┐
+      │Presence│         │Cursors │        │  CRDT  │
+      │  "3    │         │ Multi  │        │Conflict│
+      │online" │         │ select │        │  free  │
+      └────────┘         └────────┘        └────────┘
+          │                   │                 │
+       trivial            moderate           complex
+
+      Where's your head at?
+```
+
+**User brings a specific problem:**
+```
+User: The auth system is a mess
+
+You: [reads codebase]
+
+     ┌─────────────────────────────────────────────┐
+     │              CURRENT AUTH FLOW              │
+     └─────────────────────────────────────────────┘
+                        │
+          ┌─────────────┼─────────────┐
+          ▼             ▼             ▼
+     ┌─────────┐  ┌─────────┐  ┌─────────┐
+     │ Google  │  │  GitHub │  │  Email  │
+     │  OAuth  │  │  OAuth  │  │  Magic  │
+     └────┬────┘  └────┬────┘  └────┬────┘
+          │             │             │
+          └─────────────┼─────────────┘
+                        ▼
+                  ┌───────────┐
+                  │  Session  │
+                  └─────┬─────┘
+                        │
+                        ▼
+                  ┌───────────┐
+                  │   Perms   │
+                  └───────────┘
+
+     I see three tangles. Which one's burning?
+```
+
+**User is stuck mid-implementation:**
+```
+User: /opsx:explore add-auth-system
+      The OAuth integration is more complex than expected
+
+You: [reads change artifacts]
+
+     You're on task 4: "Implement OAuth flow"
+
+     Let me trace what's involved...
+
+     [draws diagram, explores options, suggests paths]
+
+     Want to update the design to reflect this?
+     Or add a spike task to investigate?
+```
+
+**User wants to compare options:**
+```
+User: Should we use Postgres or SQLite?
+
+You: Generic answer is boring. What's the context?
+
+User: A CLI tool that tracks local dev environments
+
+You: That changes everything.
+
+     ┌─────────────────────────────────────────────────┐
+     │          CLI TOOL DATA STORAGE                  │
+     └─────────────────────────────────────────────────┘
+
+     Key constraints:
+     • No daemon running
+     • Must work offline
+     • Single user
+
+                  SQLite          Postgres
+     Deployment   embedded ✓      needs server ✗
+     Offline      yes ✓           no ✗
+     Single file  yes ✓           no ✗
+
+     SQLite. Not even close.
+
+     Unless... is there a sync component?
+```
+
+---
+
+## Ending Discovery
+
+There's no required ending. Discovery might:
+
+- **Flow into a proposal**: "Ready to start? I can create a change proposal."
+- **Result in artifact updates**: "Updated design.md with these decisions"
+- **Just provide clarity**: User has what they need, moves on
+- **Continue later**: "We can pick this up anytime"
+
+When it feels like things are crystallizing, you might summarize:
+
+```
+## What We Figured Out
+
+**The problem**: [crystallized understanding]
+
+**The approach**: [if one emerged]
+
+**Open questions**: [if any remain]
+
+**Next steps** (if ready):
+- Create a change proposal
+- Keep exploring: just keep talking
+```
+
+But this summary is optional. Sometimes the thinking IS the value.
+
+---
+
+## Guardrails
+
+- **Don't implement** - Never write code or implement features. Creating OpenSpec artifacts is fine, writing application code is not.
+- **Don't fake understanding** - If something is unclear, dig deeper
+- **Don't rush** - Discovery is thinking time, not task time
+- **Don't force structure** - Let patterns emerge naturally
+- **Don't auto-capture** - Offer to save insights, don't just do it
+- **Do visualize** - A good diagram is worth many paragraphs
+- **Do explore the codebase** - Ground discussions in reality
+- **Do question assumptions** - Including the user's and your own
diff --git a/.codex/skills/openspec-propose/SKILL.md b/.codex/skills/openspec-propose/SKILL.md
new file mode 100644
index 0000000..4b7e204
--- /dev/null
+++ b/.codex/skills/openspec-propose/SKILL.md
@@ -0,0 +1,110 @@
+---
+name: openspec-propose
+description: Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+  author: openspec
+  version: "1.0"
+  generatedBy: "1.3.1"
+---
+
+Propose a new change - create the change and generate all artifacts in one step.
+
+I'll create a change with artifacts:
+- proposal.md (what & why)
+- design.md (how)
+- tasks.md (implementation steps)
+
+When ready to implement, run /opsx:apply
+
+---
+
+**Input**: The user's request should include a change name (kebab-case) OR a description of what they want to build.
+
+**Steps**
+
+1. **If no clear input provided, ask what they want to build**
+
+   Use the **AskUserQuestion tool** (open-ended, no preset options) to ask:
+   > "What change do you want to work on? Describe what you want to build or fix."
+
+   From their description, derive a kebab-case name (e.g., "add user authentication" → `add-user-auth`).
+
+   **IMPORTANT**: Do NOT proceed without understanding what the user wants to build.
+
+2. **Create the change directory**
+   ```bash
+   openspec new change "<name>"
+   ```
+   This creates a scaffolded change at `openspec/changes/<name>/` with `.openspec.yaml`.
+
+3. **Get the artifact build order**
+   ```bash
+   openspec status --change "<name>" --json
+   ```
+   Parse the JSON to get:
+   - `applyRequires`: array of artifact IDs needed before implementation (e.g., `["tasks"]`)
+   - `artifacts`: list of all artifacts with their status and dependencies
+
+4. **Create artifacts in sequence until apply-ready**
+
+   Use the **TodoWrite tool** to track progress through the artifacts.
+
+   Loop through artifacts in dependency order (artifacts with no pending dependencies first):
+
+   a. **For each artifact that is `ready` (dependencies satisfied)**:
+      - Get instructions:
+        ```bash
+        openspec instructions <artifact-id> --change "<name>" --json
+        ```
+      - The instructions JSON includes:
+        - `context`: Project background (constraints for you - do NOT include in output)
+        - `rules`: Artifact-specific rules (constraints for you - do NOT include in output)
+        - `template`: The structure to use for your output file
+        - `instruction`: Schema-specific guidance for this artifact type
+        - `outputPath`: Where to write the artifact
+        - `dependencies`: Completed artifacts to read for context
+      - Read any completed dependency files for context
+      - Create the artifact file using `template` as the structure
+      - Apply `context` and `rules` as constraints - but do NOT copy them into the file
+      - Show brief progress: "Created <artifact-id>"
+
+   b. **Continue until all `applyRequires` artifacts are complete**
+      - After creating each artifact, re-run `openspec status --change "<name>" --json`
+      - Check if every artifact ID in `applyRequires` has `status: "done"` in the artifacts array
+      - Stop when all `applyRequires` artifacts are done
+
+   c. **If an artifact requires user input** (unclear context):
+      - Use **AskUserQuestion tool** to clarify
+      - Then continue with creation
+
+5. **Show final status**
+   ```bash
+   openspec status --change "<name>"
+   ```
+
+**Output**
+
+After completing all artifacts, summarize:
+- Change name and location
+- List of artifacts created with brief descriptions
+- What's ready: "All artifacts created! Ready for implementation."
+- Prompt: "Run `/opsx:apply` or ask me to implement to start working on the tasks."
+
+**Artifact Creation Guidelines**
+
+- Follow the `instruction` field from `openspec instructions` for each artifact type
+- The schema defines what each artifact should contain - follow it
+- Read dependency artifacts for context before creating new ones
+- Use `template` as the structure for your output file - fill in its sections
+- **IMPORTANT**: `context` and `rules` are constraints for YOU, not content for the file
+  - Do NOT copy `<context>`, `<rules>`, `<project_context>` blocks into the artifact
+  - These guide what you write, but should never appear in the output
+
+**Guardrails**
+- Create ALL artifacts needed for implementation (as defined by schema's `apply.requires`)
+- Always read dependency artifacts before creating a new one
+- If context is critically unclear, ask the user - but prefer making reasonable decisions to keep momentum
+- If a change with that name already exists, ask if user wants to continue it or create a new one
+- Verify each artifact file exists after writing before proceeding to next
diff --git a/docs/system-verification.md b/docs/system-verification.md
index 7f3c554..fa8db55 100644
--- a/docs/system-verification.md
+++ b/docs/system-verification.md
@@ -3,6 +3,7 @@
 Required verification:
 
 ```bash
+npm test -- --run tests/behavioral-evaluation.test.ts tests/customization.test.ts
 npm run typecheck
 npm run build
 npm test
diff --git a/docs/truthmark/engineering/codex/roles-and-workflows.md b/docs/truthmark/engineering/codex/roles-and-workflows.md
index da66b59..3a1183a 100644
--- a/docs/truthmark/engineering/codex/roles-and-workflows.md
+++ b/docs/truthmark/engineering/codex/roles-and-workflows.md
@@ -21,25 +21,32 @@ This doc was created from the editable engineering-behavior template at docs/tru
 
 ## Current Implementation Behavior
 
-- The canonical studio role roster is defined by hyphenated Codex-native role IDs such as `producer`, `gameplay-programmer`, `qa-playtester`, and `studio-orchestrator`.
+- The canonical studio role roster is defined by hyphenated Codex-native role IDs such as `producer`, `gameplay-programmer`, `network-programmer`, `audio-director`, `accessibility-specialist`, `qa-playtester`, and `studio-orchestrator`.
+- The canonical studio role roster covers bounded specialist clusters for audio, level/world/content, systems/economy, live ops/community/localization/accessibility, and security/devops/performance/network/AI/UI programming.
 - The canonical studio role roster includes compact engine specialist prompt roles `godot-specialist`, `unity-specialist`, and `unreal-specialist`; generated projects add only the active engine specialist to their project-scoped role roster and active-role list.
-- Each role package contains a display name, system prompt, context strategy, expected outputs, handoff wording, and a review checklist.
-- Generated project role prompts include selected active-engine reference paths and reasons. Relevant programming and technical art roles receive active-engine version/gameplay references, engine/tools roles receive active-engine plugin references, engine specialists receive the matching active-engine specialist reference, and unrelated engine references are excluded by default.
-- Codex session prompts render the role display name, role ID, phase, project root, objective, engine context, sandbox, active write policy when provided, file-edit permission, context files, expected outputs, verification command, review checklist, and completion-report instructions.
+- Each role package contains a display name, system prompt, context strategy, structured responsibilities, expected inputs, expected outputs, optional output schema, quality gates, collaboration notes, stop conditions, shared compact guidance fragments, handoff wording, and a review checklist.
+- Shared role-contract guidance lives in reusable fragments for scope control, verification evidence, write-policy behavior, handoff discipline, and release readiness; role packages select the fragments they need instead of copy-pasting the same prose into every role definition.
+- Generated project role prompts include each role's display name, context strategy, role instructions, structured role-contract sections, selected active-engine reference paths, expected outputs, review checklist, and handoff template. Relevant programming and technical art roles receive active-engine version, current-best-practices, and gameplay references; engine/tools roles receive active-engine plugin references; engine specialists receive the matching active-engine specialist reference; module and plugin references remain task-keyword-selected rather than default prompt payload; unrelated engine references are excluded.
+- Codex session prompts render the role display name, role ID, context strategy, phase, project root, objective, engine context, sandbox, active write policy when provided, file-edit permission, context files, structured role-contract sections, expected outputs, verification command, review checklist, and completion-report instructions.
 - When a caller supplies a context contract, the standard prompt renderer includes a `# Context Contract` section with selected context, context omissions/blockers, project stage, studio mode, phase, write policy, sandbox, and file-edit permission.
 - Workflow prompt rendering computes the same phase and studio-mode eligibility fields used by role runs so the context contract's write policy, sandbox, and file-edit permission remain consistent; render-only plan/review/ship workflows stay read-only, while eligible implement workflows render with matching write permissions.
-- The workflow registry defines vertical-slice, bugfix, playtest, market-analysis, analytics-setup, design-spec, game-feel-tuning, art-direction, ui-ux-review, production-milestone, handoff, review, and ship-check workflow prompts.
-- Selected workflows include CLI aliases for render-only shortcuts, including market, analytics, design-spec, feel-review, art-direction, ui-review, milestone, and handoff.
-- Template selection is task- and role-sensitive; template files are read from package assets and embedded into applicable workflow prompts and role-run prompts.
-- Market analyst, data scientist, game-feel, UI/UX, QA, and release roles have bounded default templates; other additions come from role-specific keyword rules.
+- The workflow registry defines a curated prompt-only catalog across onboarding/discovery, design/architecture, implementation planning, QA/testing, release/hotfix, localization/accessibility, and team coordination categories.
+- Built-in workflow prompts include vertical-slice, bugfix, playtest, market-analysis, analytics-setup, design-spec, game-feel-tuning, art-direction, ui-ux-review, production-milestone, handoff, review, ship-check, onboard, brainstorm, prototype, architecture-decision, architecture-review, create-epics, create-stories, sprint-plan, sprint-status, story-readiness, story-done, qa-plan, regression-suite, security-audit, perf-profile, release-checklist, hotfix, and localization-plan.
+- Selected workflows include CLI aliases for render-only shortcuts, including market, analytics, design-spec, feel-review, art-direction, ui-review, milestone, handoff, start, onboard, brainstorm, prototype, architecture-decision, architecture-review, create-epics, create-stories, sprint-plan, sprint-status, story-readiness, story-done, qa-plan, regression-suite, security-audit, perf-profile, release-checklist, hotfix, and localization-plan.
+- Template selection is task-, workflow-, role-, and project-pack-sensitive; built-in template files are read from package assets, project-local template files are read from `.codex/studio/config.json` references, and selected templates are embedded into applicable workflow prompts and role-run prompts without loading the entire template pack.
+- Behavioral evaluation scenarios cover representative role/workflow prompt contracts by rendering prompts locally and checking required obligations, output-contract fields, selected context categories, relevant templates, forbidden future-only drift, and prompt-size bounds without LLM judges or hosted evaluators.
+- Market analyst, data scientist, game-feel, UI/UX, QA, release, audio, content, systems/economy, accessibility/localization/live-ops/community, and technical specialist roles have bounded default role packages; reusable template selection remains task-specific rather than loading every role or template.
+- Project-local customization packs may add `custom-*` role, workflow, and template IDs through `.codex/studio/config.json`; these overlays are extend-only and cannot replace built-in role/workflow/template IDs.
+- Custom role prompts render the same visible role ID, context strategy, expected outputs, review checklist, write-policy, sandbox, and selected-template sections as built-in role runs, while custom workflow prompts use the generic `workflow <id>` command rather than adding unbounded shortcut commands.
 - Generated workflow files carry deterministic source-input and rendered-body hash metadata that covers workflow definition fields and the owning role display name, expected outputs, and review checklist used in the rendered workflow body.
 
 ## Core Rules
 
 - Unknown role errors must point users toward Codex-native hyphenated role IDs rather than legacy agent names.
-- Prompt rendering must include the role display name and project/session metadata, including explicit sandbox and write-policy context when available, needed by Codex to operate without hidden state.
-- Templates that require Markdown sections must have non-empty required sections; the project config template must parse as JSON.
+- Prompt rendering must include the role display name, project/session metadata, and the bounded structured role contract, including explicit sandbox and write-policy context when available, needed by Codex to operate without hidden state.
+- Templates that require Markdown sections must have non-empty required sections; every built-in template records a description plus role/workflow use hints, and the project config template must parse as JSON.
 - Workflow shortcuts render prompts; they do not imply hidden parallel orchestration or future planner behavior.
+- Customization overlays are extend-only: custom IDs must use the `custom-*` prefix, may reference only project-safe relative paths, and must not replace built-in role/workflow/template IDs.
 - Workflow prompt rendering may append only selected workflow templates and must not load every template.
 - Role prompt rendering may list only selected active-engine reference paths and must not load every engine reference pack by default.
 - Generated project prompt materialization may include only the specialist prompt matching the active project engine.
@@ -47,14 +54,16 @@ This doc was created from the editable engineering-behavior template at docs/tru
 ## Flows And States
 
 - Workflow prompt flow: read project stage, studio mode, and engine from `.codex/studio.json`, select the workflow's declared context files through the path-safe selector, compute phase/studio-mode eligibility, create a Codex studio session for the owning role and phase, render the standard prompt with a context contract, then append any workflow template bodies.
+- Custom workflow prompt flow: resolve the workflow or alias from `.codex/studio/config.json`, validate its custom role and template references, select only declared project-safe context files, render the custom role prompt, then append only the custom workflow's template IDs.
 - Template selection flow: match role and task text against bounded keyword rules and return only matching template IDs.
 
 ## Contracts
 
-- Role IDs are stable strings exported from `src/roles.ts` and reused by config validation, project state, prompt generation, workflow routing, and task creation.
-- Engine reference prompt selection maps role IDs and the active project engine to generated project paths under `docs/engine-reference/<engine>/`.
-- Workflow IDs map to `.codex/workflows/<workflow>.md` files and expected context-file lists.
-- Template IDs map to package template paths, role applicability, tags, and required-section validation. Current reusable templates include GDD, feature spec, handoff, analytics setup, engine setup, market analysis, project config, game-feel tuning, art direction, UI/UX review, production milestone, playtest report, and ship check.
+- Role IDs are stable strings exported from `src/roles.ts` and reused by config validation, project state, prompt generation, workflow routing, and task creation. Role-package structured-contract fields are also rendered into both standard Codex session prompts and generated project role prompts, and generated role-prompt freshness inputs include those fields so stale prompt bodies fail validation.
+- Engine reference prompt selection maps role IDs, optional task/workflow keywords, and the active project engine to generated project paths under `docs/engine-reference/<engine>/`; every engine pack includes version, current best practices, deprecated API, breaking-change, gameplay, specialist, module, and plugin references with seed-review metadata.
+- Workflow IDs map to `.codex/workflows/<workflow>.md` files, expected context-file lists, taxonomy categories, CCGS-derived gap coverage notes, and optional CLI aliases.
+- Behavioral scenario IDs map to representative built-in roles or workflows in `src/behavioral-evaluation.ts`; each scenario declares required phrases, forbidden drift phrases, selected-context categories, and workflow template expectations.
+- Template IDs map to package template paths, project-local template paths, descriptions, role/workflow applicability hints, tags, and required-section validation. Current reusable built-in templates include GDD, feature spec, handoff, analytics setup, engine setup, market analysis, project config, game-feel tuning, art direction, UI/UX review, production milestone, playtest report, ship check, ADR, technical design, architecture traceability, art bible, sound bible, UX spec, accessibility requirements, test plan, test evidence, sprint plan, vertical-slice report, release notes, postmortem, risk register, economy model, difficulty curve, player journey, and pitch document.
 
 ## Product Truth Links
 
@@ -67,6 +76,13 @@ This doc was created from the editable engineering-behavior template at docs/tru
 - Decision (2026-06-13): Workflow prompts use the same context-contract renderer as role-run prompts and include only selected workflow context instead of broad prompt material.
 - Decision (2026-06-14): Add only one specialist role ID per supported engine and keep engine reference prompt selection active-engine scoped.
 - Decision (2026-06-14): Keep engine specialist IDs canonical while scoping generated project specialist prompts and active specialist eligibility to the active engine.
+- Decision (2026-06-17): Expand role coverage through bounded Codex-native specialist clusters rather than mirroring CCGS file-for-file; each new role remains a renderable role package with selected context strategy, expected outputs, and review checklist.
+- Decision (2026-06-17): Expand workflow coverage as a categorized, prompt-only Codex-native catalog with local aliases and generated workflow metadata rather than importing slash-command lifecycle machinery.
+- Decision (2026-06-17): Expand production template depth as package-shipped, metadata-rich templates selected by role/workflow relevance rather than broad prompt loading.
+- Decision (2026-06-17): Expand engine reference depth as package-shipped, metadata-validated active-engine assets with default role references plus task/workflow-keyword-selected module and plugin references.
+- Decision (2026-06-17): Expand role prompt depth through structured compact role contracts and reusable shared fragments rendered in both standard Codex session prompts and generated project role prompts, while keeping role/task context bounded.
+- Decision (2026-06-17): Add representative behavioral-evaluation fixtures as deterministic prompt-contract checks instead of adopting hosted/LLM agent-evaluation infrastructure.
+- Decision (2026-06-17): Add project-local customization as an extend-only overlay so users can define local `custom-*` roles, workflows, and templates while preserving built-in registries and bounded context selection.
 
 ## Rationale
 
@@ -79,8 +95,8 @@ Role and workflow prompt generation is the user-facing contract that turns a gen
 
 ## Maintenance Notes
 
-- Update this doc with changes to `src/roles.ts`, `src/codex-session.ts`, `src/codex-prompts.ts`, `src/workflows.ts`, `src/engine-reference.ts`, `src/templates.ts`, or `templates/**`.
-- Relevant verification includes role, Codex prompt/session, workflow, template, and functionality-gap tests.
+- Update this doc with changes to `src/roles.ts`, `src/codex-session.ts`, `src/codex-prompts.ts`, `src/customization.ts`, `src/workflows.ts`, `src/engine-reference.ts`, `src/templates.ts`, or `templates/**`.
+- Relevant verification includes role, Codex prompt/session, workflow, customization, template, and functionality-gap tests.
 
 ## Source References
 
diff --git a/docs/truthmark/engineering/codex/runtime-and-tasks.md b/docs/truthmark/engineering/codex/runtime-and-tasks.md
index 4599d2d..9559005 100644
--- a/docs/truthmark/engineering/codex/runtime-and-tasks.md
+++ b/docs/truthmark/engineering/codex/runtime-and-tasks.md
@@ -25,7 +25,7 @@ This bounded leaf truth doc owns `run` preparation and execution, Codex command
 
 ## Inputs
 
-- A valid project root with `.codex/studio.json` and the generated role prompt for the requested role.
+- A valid project root with `.codex/studio.json`, `.codex/studio/config.json`, and either a generated built-in role prompt or a project-local custom role prompt for the requested role.
 - A studio role ID or task ID.
 - A non-empty task/objective.
 - Optional included artifacts, verification command/args, review flag, fix flag, and max fix-pass count.
@@ -37,9 +37,10 @@ Runtime execution prepares bounded Codex prompts, evaluates studio write policy
 ## Execution Model
 
 - `prepareRun` resolves the project, reads studio state, inlines the generated project role prompt plus selected package templates, renders a Codex prompt, computes prompt and metadata cache paths, and builds Codex execution commands.
+- When the requested role is a project-local `custom-*` role from `.codex/studio/config.json`, `prepareRun` renders the configured custom prompt file, expected outputs, review checklist, selected project-local templates, and declared context files through the same path-safe selector and studio-policy gates used by built-in roles.
 - `prepareRun` rejects wrong-engine specialist roles before prompt construction; for example, a Godot project may run `godot-specialist` but not `unity-specialist` or `unreal-specialist`.
 - `--print-prompt` and `--dry-run` are inspection-only paths and do not write prompt cache, metadata, task state, or run directories.
-- Runtime prompt preparation uses the path-safe context selector for required role context, included artifacts, and explicitly allowed broad context. The selector rejects absolute paths, traversal, control characters, symlink escapes, secret-like paths, generated/build output, and binary or non-file entries; missing required context is recorded as a context-contract omission instead of widening reads.
+- Runtime prompt preparation uses the path-safe context selector for required role context, task-relevant active-engine reference files, included artifacts, and explicitly allowed broad context. The selector rejects absolute paths, traversal, control characters, symlink escapes, secret-like paths, generated/build output, and binary or non-file entries; missing required context is recorded as a context-contract omission instead of widening reads.
 - Context selection allocates file and character budgets to required entries before optional entries, but required entries cannot bypass path safety, generated-output, binary, per-entry character, total character, or file-count limits.
 - Included artifact file bodies are appended to the rendered prompt only when the artifact entry is selected by the context selector; rejected or omitted artifacts remain visible in context-contract omissions without embedding their contents.
 - `--allow-broad-context` adds only an explicit bounded list of candidate project files such as the GDD, production timeline, and market overview; candidates still pass through the selector and must resolve under the project root.
@@ -57,7 +58,7 @@ Runtime execution prepares bounded Codex prompts, evaluates studio write policy
 ## Steps
 
 1. Validate the requested role/task and project state.
-2. Select path-safe context entries, record missing/omitted/rejected entries for the context contract, and compute the shared studio-run eligibility result.
+2. Select path-safe context entries, including task-relevant active-engine reference files, record missing/omitted/rejected entries for the context contract, and compute the shared studio-run eligibility result.
 3. Block non-dry mutating runs when the eligibility result is not allowed; inspection paths may still render diagnostics.
 4. Render the Codex prompt with the active write policy and sandbox.
 5. For non-dry allowed runs, write the prompt and metadata cache under `.codex/runs/`.
@@ -97,6 +98,8 @@ Runtime execution prepares bounded Codex prompts, evaluates studio write policy
 - Decision (2026-06-13): Route both direct role runs and task runs through the shared eligibility result before mutating side effects, failing closed for unapproved strict-studio mutation.
 - Decision (2026-06-13): Use one shared context-contract renderer for implementation, review, and fix prompts so selected context and write policy are visible without loading broad prompt material.
 - Decision (2026-06-14): Fail wrong-engine specialist role runs before constructing contradictory prompts or writing run metadata.
+- Decision (2026-06-17): Add task-relevant active-engine reference requests to role-run and workflow context contracts so module/plugin depth is selected by role/task relevance instead of broad prompt loading.
+- Decision (2026-06-17): Route project-local custom role runs through the same visible write-policy, sandbox, context-selection, prompt-cache, and template-selection contracts as built-in roles instead of introducing a separate plugin runtime.
 
 ## Rationale
 
@@ -109,7 +112,7 @@ Codex execution is intentionally explicit: users can inspect prompts without sid
 
 ## Maintenance Notes
 
-- Update this doc with changes to `src/runner.ts`, `src/tasks.ts`, `src/context-manifest.ts`, `src/prompt-context.ts`, `src/codex-runtime.ts`, or `src/verification.ts`.
+- Update this doc with changes to `src/runner.ts`, `src/tasks.ts`, `src/customization.ts`, `src/context-manifest.ts`, `src/prompt-context.ts`, `src/codex-runtime.ts`, or `src/verification.ts`.
 - Update this doc with changes to `src/studio-policy.ts` when policy primitive behavior changes.
 - Relevant verification includes studio-policy, runner, task, verification, Codex runtime, and lifecycle-focused tests.
 
diff --git a/docs/truthmark/engineering/contracts/cli-and-validation.md b/docs/truthmark/engineering/contracts/cli-and-validation.md
index 4f36ec0..8827855 100644
--- a/docs/truthmark/engineering/contracts/cli-and-validation.md
+++ b/docs/truthmark/engineering/contracts/cli-and-validation.md
@@ -20,15 +20,19 @@ This bounded leaf truth doc owns the repository CLI command contract, package sc
 ## Current Implementation Behavior
 
 - The repository exposes a package CLI named `opengamestudio` from the built `dist/cli.js` entrypoint.
-- The CLI currently supports project initialization/status, template discovery, role execution, task management, approval-store management, workflow prompt rendering, and validation surfaces.
+- The CLI currently supports project initialization/status, template discovery, project-local customization inspection, role execution, task management, approval-store management, workflow prompt rendering, workflow shortcut aliases, and validation surfaces.
 - Repository validation is executable through `npm run validate`, which builds the package and runs the built CLI validation command.
+- Repository validation includes local deterministic behavioral-evaluation scenarios for representative role and workflow prompt contracts; these subchecks render prompts and inspect obligations without hosted evaluators, telemetry, hidden memory, or LLM calls.
 
 ## Contract Surface
 
 - Package name: `open-gamestudio`.
 - Package bin: `opengamestudio` points to `./dist/cli.js`.
 - Primary scripts include `build`, `typecheck`, `test`, `validate`, `init`, `manage`, and `templates`.
-- Public CLI command groups include initialization/status commands, template discovery, role run execution, file-backed tasks, approval management, and render-only workflow shortcuts.
+- Public CLI command groups include initialization/status commands, template discovery, role run execution, file-backed tasks, approval management, generic workflow prompt rendering, and render-only workflow shortcuts.
+- `opengamestudio templates list --project <path>` and `opengamestudio templates show <template-id> --project <path>` include project-local custom templates from `.codex/studio/config.json` alongside built-in package templates.
+- `opengamestudio workflow <workflow-id> --project <path>` renders either a built-in workflow ID or an extend-only project-local custom workflow ID/alias.
+- Render-only workflow shortcut commands include market, analytics, design-spec, feel-review, art-direction, ui-review, milestone, handoff, review, ship-check, start, onboard, brainstorm, prototype, architecture-decision, architecture-review, create-epics, create-stories, sprint-plan, sprint-status, story-readiness, story-done, qa-plan, regression-suite, security-audit, perf-profile, release-checklist, hotfix, and localization-plan.
 - `opengamestudio init` and `opengamestudio new` accept `--studio-mode fast-prototype|guided-studio|strict-studio`, default to `guided-studio` when omitted, and persist that value as `studioMode` in generated `.codex/studio.json`.
 - `opengamestudio approval grant --project <path> --role <role> --task <id-or-hash> --scope <glob>` appends a scoped approval record when the role is valid, the scope is safe and non-empty, and the task reference is either an existing task ID assigned to the same role or a 64-character SHA-256 objective hash.
 - `opengamestudio approval list --project <path>` prints approval history, including revoked and expired records as visible non-authorizing records.
@@ -41,8 +45,9 @@ This bounded leaf truth doc owns the repository CLI command contract, package sc
 ## Inputs
 
 - CLI options and arguments parsed by Commander in `src/cli.ts`.
-- Repository files checked by validation, including package metadata, source files, templates, generated build output, engine configs, engine reference packs, and optional project paths.
+- Repository files checked by validation, including package metadata, source files, templates, generated build output, engine configs, engine reference packs, deterministic behavioral-evaluation scenarios, and optional project paths.
 - Project validation input when `--project <path>` is supplied.
+- Project-local customization config at `.codex/studio/config.json`, plus any referenced local prompt, context, workflow, and template files.
 
 ## Outputs
 
@@ -50,8 +55,9 @@ This bounded leaf truth doc owns the repository CLI command contract, package sc
 - Approval grant output includes the new approval ID, normalized role, objective/hash information, scopes, and the approval-store path for inspection. The stored record includes baseline metadata as part of the approval store contract.
 - Dry-run role-run output includes eligibility, write policy, Codex sandbox, file-edit permission, approval/override/advisory provenance, project stage, studio mode, diagnostic approval scopes, the current objective hash, matched/no-match status, and per-record authorization reasons such as role, normalized objective, scope, project stage, studio mode, expiry, revocation, and stage mismatches.
 - Validation emits one line per check in `STATUS id: message (path)` shape and exits non-zero when any check fails.
-- Package smoke validation builds and exercises the packed package bin and template loading behavior.
-- Package validation checks representative engine reference assets from Godot, Unity, and Unreal packs are included in `npm pack`.
+- Behavioral evaluation check IDs use `behavioral.scenario.<scenario-id>` and fail when a built-in role/workflow prompt misses required obligations, includes unnegated forbidden future-only drift, exceeds the prompt-size bound, lacks expected selected-context categories, or selects forbidden templates.
+- Package smoke validation builds and exercises the packed package bin and template loading behavior, including all template paths registered in `src/templates.ts`.
+- Package validation checks every engine reference asset registered for Godot, Unity, and Unreal packs is included in `npm pack`.
 
 ## Errors And Diagnostics
 
@@ -59,8 +65,8 @@ This bounded leaf truth doc owns the repository CLI command contract, package sc
 - Approval grant rejects empty scopes, unsafe scopes, broad scopes such as `**`, `**/*`, `*`, or `.` unless `--allow-broad-scope` is supplied, invalid roles, unknown task IDs, existing task IDs assigned to a different role, and malformed canonical expiry timestamps.
 - Approval revoke fails clearly for unknown approval IDs.
 - Unapproved strict-studio mutating `run <role>` and `task run` fail before Codex launch, run metadata writes, or task mutation.
-- Missing package scripts, missing package bin/files, missing source files, unavailable Codex CLI, invalid templates, missing engine reference pack files or reviewer/date/source-link metadata, exposed future surfaces, missing build output, and package smoke failures are validation failures.
-- Project validation fails for invalid `.codex/studio.json` including invalid `studioMode`, missing or malformed `.codex/approvals.json`, missing or malformed `.codex/context-manifest.json` or `.codex/context-manifest.meta.json`, stale context-manifest hashes or stage/mode inputs, missing generated project files, missing any materialized active-engine reference files, missing active-engine specialist prompt files, materialized wrong-engine specialist prompt files, missing workflow/prompt sections, stale or tampered generated-surface metadata, current-renderer mismatches, malformed or incomplete generated-surface metadata markers, forbidden generated surfaces, or read-only command mutations.
+- Missing package scripts, missing package bin/files, missing source files, unavailable Codex CLI, invalid role packages or templates, missing engine reference pack files or reviewer/date/source-link/engine/version-reviewed/tags/roles/workflows metadata, exposed future surfaces, missing build output, and package smoke failures are validation failures.
+- Project validation fails for invalid `.codex/studio.json` including invalid `studioMode`, missing or malformed `.codex/approvals.json`, missing or malformed `.codex/context-manifest.json` or `.codex/context-manifest.meta.json`, stale context-manifest hashes or stage/mode inputs, invalid `.codex/studio/config.json`, custom IDs that override built-ins or omit the `custom-*` prefix, unsafe custom file paths, missing custom prompt/template files, missing custom template sections, custom references to unknown roles/workflows/templates, missing generated project files, missing any materialized active-engine reference files, missing active-engine-specialist prompt files, materialized wrong-engine-specialist prompt files, missing workflow/prompt sections, stale or tampered generated-surface metadata, current-renderer mismatches, malformed or incomplete generated-surface metadata markers, forbidden generated surfaces, or read-only command mutations.
 - Project validation reports generated prompt or workflow files with no generated-surface metadata markers as legacy skip diagnostics that require regeneration before relying on freshness checks.
 
 ## Compatibility Rules
@@ -88,7 +94,10 @@ This bounded leaf truth doc owns the repository CLI command contract, package sc
 - Decision (2026-06-13): Expose approval grant/list/revoke as audit-store management commands and wire approval matching into `run <role>` and `task run` eligibility for mutating execution.
 - Decision (2026-06-13): Expose approval mismatch information through dry-run diagnostics, and fail non-dry unapproved strict-studio mutation before side effects.
 - Decision (2026-06-13): Treat `.codex/context-manifest.json` and `.codex/context-manifest.meta.json` as required generated project contracts and validate manifest schema plus sidecar freshness.
-- Decision (2026-06-14): Validate engine reference packs structurally by seed file presence and seed-review metadata shape, and validate all active-engine materialized reference files in generated projects without judging prose quality.
+- Decision (2026-06-14): Validate engine reference packs structurally by registered file presence and seed-review metadata shape, and validate all active-engine materialized reference files in generated projects without judging prose quality.
+- Decision (2026-06-17): Expose the expanded workflow catalog as render-only CLI shortcut commands while keeping future planner/next, telemetry, parallel orchestration, and ownership-enforcement surfaces hidden.
+- Decision (2026-06-17): Add local deterministic behavioral-evaluation validation subchecks for representative role/workflow prompt contracts rather than hosted evaluators, telemetry, hidden memory, or LLM judges.
+- Decision (2026-06-17): Support project-local customization as an extend-only `custom-*` overlay with schema validation, project-safe paths, generic workflow rendering, and template inspection rather than mutable replacement of built-in registries.
 
 ## Rationale
 
@@ -103,8 +112,8 @@ The CLI is the stable integration boundary for humans, package installs, and gen
 
 ## Maintenance Notes
 
-- Update this doc with changes to `src/cli.ts`, `src/validation.ts`, `src/context-manifest.ts`, `src/engine-reference.ts`, package metadata, README public command claims, or validation check IDs.
-- Relevant verification includes `npm run validate`, CLI help smoke checks, validation tests, package dry-run/smoke checks, and future-surface guard tests.
+- Update this doc with changes to `src/cli.ts`, `src/validation.ts`, `src/customization.ts`, `src/behavioral-evaluation.ts`, `src/context-manifest.ts`, `src/engine-reference.ts`, package metadata, README public command claims, or validation check IDs.
+- Relevant verification includes `npm run validate`, CLI help smoke checks, customization tests, behavioral-evaluation tests, validation tests, package dry-run/smoke checks, and future-surface guard tests.
 
 ## Source References
 
diff --git a/docs/truthmark/engineering/projects/project-scaffolding.md b/docs/truthmark/engineering/projects/project-scaffolding.md
index e8d53cc..2c9317b 100644
--- a/docs/truthmark/engineering/projects/project-scaffolding.md
+++ b/docs/truthmark/engineering/projects/project-scaffolding.md
@@ -25,6 +25,7 @@ This doc was created from the editable engineering-behavior template at docs/tru
 - Initialization writes projects under `projects/<slug>/`, rejects an existing target path, and checks same-parent slug and Unreal class-name collisions before writing.
 - Project state is written to `.codex/studio.json` with schema version 1, product `codex-game-studio`, project summary fields, lifecycle `mode`, policy `studioMode`, the project-scoped role roster, mode-active roles plus the active engine specialist, and all workflow IDs.
 - Initialization writes an empty versioned `.codex/approvals.json` approval store alongside `.codex/studio.json`.
+- Initialization writes `.codex/studio/config.json` as a schema-versioned, extend-only customization pack seed. The default file contains no local roles, workflows, or templates; projects can add `custom-*` IDs without overriding built-in role/workflow/template IDs.
 - Initialization writes `.codex/context-manifest.json` and `.codex/context-manifest.meta.json`. The manifest records selected context entries with source path, reason, required flag, budget metadata, safety classification, and selection status; freshness hashes and inputs live only in the metadata sidecar.
 - Initialization materializes only the active engine reference pack under `docs/engine-reference/<engine>/` from packaged `engine_reference/<engine>/` assets before writing the context manifest.
 - Context selection rejects unsafe, secret-like, generated/build-output, binary, and non-file paths before budget allocation. Existing required entries receive budget priority over optional entries, but required entries must still fit the file count, per-entry character, and total character budgets.
@@ -47,7 +48,7 @@ This doc was created from the editable engineering-behavior template at docs/tru
 
 ## Flows And States
 
-- Initialization flow: parse options, normalize engine, derive slug, reject collisions, create engine files, create `.codex/runs`, write the empty approval store, write studio state, write metadata-bearing workflow files, write starter docs, materialize the active engine reference pack, materialize metadata-bearing role prompts, and write the context manifest plus sidecar metadata.
+- Initialization flow: parse options, normalize engine, derive slug, reject collisions, create engine files, create `.codex/runs`, write the empty approval store, write studio state, write the default extend-only customization config, write metadata-bearing workflow files, write starter docs, materialize the active engine reference pack, materialize metadata-bearing role prompts, and write the context manifest plus sidecar metadata.
 - Project status states are `active`, `frozen`, and `inactive`; `freeze` is the only current CLI path that mutates status.
 
 ## Contracts
@@ -68,6 +69,7 @@ This doc was created from the editable engineering-behavior template at docs/tru
 - Decision (2026-06-13): Generate context manifest freshness metadata as a sidecar so the manifest body remains stable JSON describing selected context, while stale project-stage or studio-mode inputs are detected separately.
 - Decision (2026-06-14): Materialize packaged engine references only for the active engine and select prompt/context entries by relevance instead of loading all engine packs.
 - Decision (2026-06-14): Materialize generated project specialist prompts only for the active project engine while keeping all specialist IDs in the canonical role catalog.
+- Decision (2026-06-17): Initialize a project-local `.codex/studio/config.json` customization pack as an extend-only overlay so users can add `custom-*` roles, workflows, and templates without replacing generated built-ins.
 
 ## Rationale
 
diff --git a/docs/truthmark/engineering/repository/overview.md b/docs/truthmark/engineering/repository/overview.md
index 39e8598..a13e00a 100644
--- a/docs/truthmark/engineering/repository/overview.md
+++ b/docs/truthmark/engineering/repository/overview.md
@@ -25,7 +25,7 @@ This bounded leaf truth doc summarizes the repository-level behavior surface. Mo
 - Generated projects contain `.codex/studio.json`, role prompt files, workflow markdown, starter design/production/market documents, engine-specific project markers, and a Codex-native `AGENTS.md` instruction surface.
 - Role run commands render deterministic Codex prompts and, unless in inspection mode, execute Codex with optional verification, review, and bounded fix passes.
 - Workflow shortcut commands are render-only prompt surfaces and do not imply hidden planner, parallel orchestration, telemetry, or ownership enforcement behavior.
-- Validation checks package metadata, source and template presence, role/workflow rendering, future-surface guardrails, build output, and package install smoke behavior.
+- Validation checks package metadata, source and template presence, role/workflow rendering, behavioral-evaluation scenarios, project-local customization packs, future-surface guardrails, build output, and package install smoke behavior.
 
 ## Core Rules
 
diff --git a/docs/truthmark/product/open-game-studio-cli.md b/docs/truthmark/product/open-game-studio-cli.md
index 12176ba..e3a1808 100644
--- a/docs/truthmark/product/open-game-studio-cli.md
+++ b/docs/truthmark/product/open-game-studio-cli.md
@@ -24,13 +24,13 @@ This capability excludes game-engine functionality, hosted orchestration, backgr
 
 Open Game Studio exposes npm package scripts and a built CLI for initialization, management, template listing, validation, and Codex-oriented role execution. Generated projects use `AGENTS.md` and `.codex/**` surfaces rather than legacy `CODEX.md` contracts. Direct Codex execution through `opengamestudio run <role>` is the default runtime path; `--dry-run` and `--print-prompt` remain inspection-only paths.
 
-The current repository also includes engine reference material for Godot, Unity, and Unreal, context-manifest generation, project task state, approval-store behavior, role/workflow registries, and validation coverage for package assets and generated surfaces.
+The current repository also includes metadata-validated engine reference material for Godot, Unity, and Unreal, context-manifest generation, project task state, approval-store behavior, role/workflow registries, deterministic behavioral-evaluation scenarios, project-local customization packs, and validation coverage for package assets and generated surfaces. Built-in role prompts use bounded structured contracts for responsibilities, expected inputs, output formats, quality gates, collaboration notes, and stop conditions instead of cloning broad external agent bodies. Project-local customization uses `.codex/studio/config.json` as an extend-only overlay for `custom-*` roles, workflows, and templates, with path-safe validation and generic workflow rendering rather than built-in registry replacement. Engine reference depth is packaged as active-engine version, best-practice, deprecated API, breaking-change, module, and plugin files selected by role/task relevance rather than loaded wholesale. The workflow catalog is a curated prompt-only game-development surface across onboarding/discovery, design/architecture, implementation planning, QA/testing, release/hotfix, localization/accessibility, and team coordination rather than a hidden lifecycle controller. The production template pack covers design, architecture, art, audio, UX, accessibility, QA, release, production-risk, economy, difficulty, player-journey, and pitch artifacts as package-shipped assets selected by relevance.
 
 ## Acceptance Criteria
 
 - Developers can initialize and manage project scaffolds through the package CLI while generated project files remain reviewable in the repository.
 - Role and workflow execution stays Codex-native by default and does not require a hosted service, daemon, or alternate agent runtime.
-- Prompt and context materialization selects relevant roles, workflows, templates, and engine references instead of loading every available agent or template for a single task.
+- Prompt and context materialization selects relevant roles, workflows, templates, engine references, and project-local customization pack entries instead of loading every available agent or template for a single task.
 - Mutating runtime behavior is visible and policy-gated; dry-run and print-prompt paths do not mutate project state.
 - Generated project contracts use `AGENTS.md` and `.codex/**`; stale generated-project compatibility surfaces are not reintroduced without an explicit boundary change.
 - Validation commands and tests cover public CLI/package behavior, generated surfaces, engine references, and future-only surfaces remaining absent until implemented.
@@ -42,6 +42,7 @@ The current repository also includes engine reference material for Godot, Unity,
 - 2026-06-13: Generated project instruction contracts use `AGENTS.md` and `.codex/**`, not `CODEX.md` or legacy compatibility shims.
 - 2026-06-13: Planner/next, telemetry, parallel orchestration, hard ownership enforcement, and similar future-only surfaces must remain absent until implementation, tests, and docs exist.
 - 2026-06-13: Truthmark-backed docs guard repository truth in this checkout, but Truthmark workflow mechanics are not Open Game Studio product features.
+- 2026-06-17: Project-local customization is an extend-only, file-backed overlay for `custom-*` roles, workflows, and templates; it must remain Codex-native, reviewable, path-safe, and non-hosted.
 
 ## Engineering Realization Links
 
@@ -75,6 +76,7 @@ The current repository also includes engine reference material for Godot, Unity,
 - ../../../src/projects.ts
 - ../../../src/roles.ts
 - ../../../src/workflows.ts
+- ../../../src/customization.ts
 - ../../../src/runner.ts
 - ../../../src/validation.ts
 - ../../../tests/functionality-gap-pass.test.ts
diff --git a/docs/truthmark/routes/areas/repository.md b/docs/truthmark/routes/areas/repository.md
index 149bd94..26a4060 100644
--- a/docs/truthmark/routes/areas/repository.md
+++ b/docs/truthmark/routes/areas/repository.md
@@ -32,6 +32,7 @@ Code surface:
 - src/roles.ts
 - src/workflows.ts
 - src/runner.ts
+- src/customization.ts
 - src/validation.ts
 - engine_reference/**
 - templates/**
@@ -64,6 +65,7 @@ Code surface:
 - src/context-manifest.ts
 - src/engine-reference.ts
 - src/generated-surfaces.ts
+- src/customization.ts
 - src/paths.ts
 - engine_configs/**
 - engine_reference/**
@@ -92,6 +94,8 @@ Code surface:
 - src/roles.ts
 - src/codex-session.ts
 - src/codex-prompts.ts
+- src/behavioral-evaluation.ts
+- src/customization.ts
 - src/prompt-context.ts
 - src/workflows.ts
 - src/engine-reference.ts
@@ -101,10 +105,12 @@ Code surface:
 - tests/roles.test.ts
 - tests/codex-session.test.ts
 - tests/codex-prompts.test.ts
+- tests/behavioral-evaluation.test.ts
+- tests/customization.test.ts
 - tests/functionality-gap-pass.test.ts
 
 Update truth when:
-- studio role IDs, role contracts, workflow registry entries, prompt rendering, engine reference prompt selection, context strategies, or template selection rules change
+- studio role IDs, custom role IDs, role contracts, workflow registry entries, prompt rendering, engine reference prompt selection, context strategies, or template selection rules change
 - Codex-native workflow shortcuts or generated workflow prompt contents change
 
 ## Runtime And Task Execution
@@ -123,6 +129,7 @@ Code surface:
 - src/runner.ts
 - src/studio-policy.ts
 - src/context.ts
+- src/customization.ts
 - src/context-manifest.ts
 - src/prompt-context.ts
 - src/tasks.ts
@@ -172,6 +179,7 @@ truth_documents:
 Code surface:
 - src/cli.ts
 - src/validation.ts
+- src/customization.ts
 - src/context-manifest.ts
 - src/engine-reference.ts
 - src/generated-surfaces.ts
@@ -180,5 +188,5 @@ Code surface:
 - tests/functionality-gap-pass.test.ts
 
 Update truth when:
-- public CLI commands, package scripts/bin/files, validation check IDs, engine reference package checks, documentation claims, or package dependency contracts change
+- public CLI commands, package scripts/bin/files, validation check IDs, project-local customization checks, engine reference package checks, documentation claims, or package dependency contracts change
 - future-only surfaces become exposed or are intentionally kept hidden
diff --git a/docs/workflow-validation.md b/docs/workflow-validation.md
index 3d7c615..1ac705e 100644
--- a/docs/workflow-validation.md
+++ b/docs/workflow-validation.md
@@ -2,9 +2,9 @@
 
 Validation exits nonzero when any check fails.
 
-Repo validation checks package scripts, build output, package assets, engine configs, expanded role rendering, canonical workflow rendering, templates, package packing, installed-bin asset loading, future-only CLI surfaces, and Codex CLI readiness.
+Repo validation checks package scripts, build output, package assets, engine configs, expanded role rendering, canonical workflow rendering, deterministic behavioral-evaluation scenarios, templates, package packing, installed-bin asset loading, future-only CLI surfaces, and Codex CLI readiness.
 
-Project validation checks `.codex/studio.json` full `roles`, mode-specific `activeRoles`, registry-derived `workflows`, `AGENTS.md`, generated project-specific role prompts, workflow files, engine source files, starter docs, timeline sections, forbidden legacy artifacts, and read-only `status`/`resume` behavior.
+Project validation checks `.codex/studio.json` full `roles`, mode-specific `activeRoles`, registry-derived `workflows`, `.codex/studio/config.json` customization packs, `AGENTS.md`, generated project-specific role prompts, workflow files, engine source files, starter docs, timeline sections, forbidden legacy artifacts, and read-only `status`/`resume` behavior.
 
 CLI surface checks:
 
@@ -15,4 +15,8 @@ npm exec opengamestudio -- run --help | grep -- "--dry-run"
 
 Workflow shortcut commands such as `market`, `analytics`, `design-spec`, `feel-review`, `art-direction`, `ui-review`, `milestone`, and `handoff` render prompts only. They do not launch Codex or create run records.
 
+Behavioral evaluation scenarios are local deterministic validation subchecks. They render built-in role and workflow prompts, assert required prompt obligations, selected context categories, relevant templates, output-contract coverage, and forbidden future-only drift. They do not call hosted evaluators, telemetry, hidden memory, or LLM judges.
+
+Project-local customization uses `.codex/studio/config.json` as an extend-only overlay. Custom role, workflow, and template IDs must use `custom-*`, must not override built-ins, and all referenced prompt/context/template paths must remain inside the project root.
+
 No generated `CODEX.md`, `.gamestudio/runs`, or `project_orchestrator.md` is required or produced.
diff --git a/engine_reference/godot/VERSION.md b/engine_reference/godot/VERSION.md
index 2e36fb2..54fe0f1 100644
--- a/engine_reference/godot/VERSION.md
+++ b/engine_reference/godot/VERSION.md
@@ -1,36 +1,26 @@
 reviewer: Open Game Studio seed review
-date: 2026-06-14
-source-link: https://docs.godotengine.org/
+date: 2026-06-17
+source-link: https://docs.godotengine.org/en/stable/
+engine: godot
+version-reviewed: 4.4
+tags: godot,VERSION
+roles: gameplay-programmer,engine-programmer,tools-programmer,technical-artist
+workflows: prototype,bugfix,architecture-review,qa-plan
 
 # Godot Version Reference
 
-version-applicability: Godot 4.x projects unless project files state otherwise.
+## Purpose
 
-## Prefer
+Use this file to confirm the reviewed engine version, official documentation root, and version-sensitive assumptions before making implementation claims.
 
-- Use scene composition, typed GDScript where present, and signal-based communication for gameplay events.
-- Keep engine-specific checks tied to the active project version.
+## Guidance
 
-## Avoid
+- Match generated project engine version against this reviewed baseline.
+- Prefer official docs for version-specific APIs.
+- Record any project-local engine version drift in the handoff.
 
-- Do not assume Godot 3.x APIs when the project targets Godot 4.x.
-- Do not rewrite imported assets or generated import metadata without an explicit task reason.
+## Validation
 
-## Pitfalls
-
-- Node paths, autoload names, and signal signatures are easy to drift during refactors.
-- Physics behavior can depend on project settings as much as script code.
-
-## Verification Notes
-
-- Run the configured Godot command or a documented editor smoke check.
-- Report scene paths, script paths, and any ProjectSettings changes.
-
-## Role Notes
-
-- Gameplay programmers should cite the scene/script touched.
-- Tools and engine programmers should name editor plugin or export changes.
-
-## Official Links
-
-- https://docs.godotengine.org/
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/godot/breaking-changes.md b/engine_reference/godot/breaking-changes.md
new file mode 100644
index 0000000..6fc739e
--- /dev/null
+++ b/engine_reference/godot/breaking-changes.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.godotengine.org/en/stable/
+engine: godot
+version-reviewed: 4.4
+tags: godot,breaking,changes
+roles: gameplay-programmer,engine-programmer,qa-playtester,release-manager
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Godot Breaking Changes
+
+## Purpose
+
+Surface version upgrade and compatibility risks before relying on engine behavior.
+
+## Guidance
+
+- Call out migration-sensitive APIs, package versions, serialization formats, and build settings.
+- Separate confirmed breaking changes from speculative compatibility risks.
+- Include rollback or compatibility notes for risky changes.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/godot/current-best-practices.md b/engine_reference/godot/current-best-practices.md
new file mode 100644
index 0000000..fba813e
--- /dev/null
+++ b/engine_reference/godot/current-best-practices.md
@@ -0,0 +1,27 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.godotengine.org/en/stable/
+engine: godot
+version-reviewed: 4.4
+tags: godot,current,best,practices
+roles: gameplay-programmer,engine-programmer,tools-programmer,technical-artist
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Godot Current Best Practices
+
+## Purpose
+
+Apply current engine-native defaults without turning the task into broad process ceremony.
+
+## Guidance
+
+- Prefer engine-native composition and asset workflows.
+- Keep edits scoped to the requested role/task.
+- Mention scene, prefab, resource, project-setting, or asset-import changes explicitly.
+- Use local validation evidence before claiming readiness.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/godot/deprecated-apis.md b/engine_reference/godot/deprecated-apis.md
new file mode 100644
index 0000000..02161a6
--- /dev/null
+++ b/engine_reference/godot/deprecated-apis.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.godotengine.org/en/stable/
+engine: godot
+version-reviewed: 4.4
+tags: godot,deprecated,apis
+roles: gameplay-programmer,engine-programmer,qa-playtester,performance-analyst
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Godot Deprecated APIs
+
+## Purpose
+
+Avoid stale APIs and migration traps when editing or reviewing engine code.
+
+## Guidance
+
+- Check version-specific deprecations before copying older snippets.
+- Prefer supported APIs and document unavoidable legacy use.
+- Treat deprecated APIs as warnings unless the task is a migration or compatibility fix.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/godot/gameplay.md b/engine_reference/godot/gameplay.md
index faef843..cc27845 100644
--- a/engine_reference/godot/gameplay.md
+++ b/engine_reference/godot/gameplay.md
@@ -1,36 +1,26 @@
 reviewer: Open Game Studio seed review
-date: 2026-06-14
-source-link: https://docs.godotengine.org/en/stable/tutorials/scripting/index.html
+date: 2026-06-17
+source-link: https://docs.godotengine.org/en/stable/
+engine: godot
+version-reviewed: 4.4
+tags: godot,gameplay
+roles: gameplay-programmer,engine-programmer,tools-programmer,technical-artist
+workflows: prototype,bugfix,architecture-review,qa-plan
 
-# Godot Gameplay Reference
+# Godot Gameplay Implementation Reference
 
-version-applicability: Godot 4.x gameplay scripts and scenes.
+## Purpose
 
-## Prefer
+Guide gameplay code with engine-native runtime patterns and verification evidence.
 
-- Keep behavior near the scene nodes that own it.
-- Use exported properties for tunables that designers should inspect.
+## Guidance
 
-## Avoid
+- Keep gameplay state deterministic where practical.
+- Separate authored content from generated/runtime data.
+- Prefer small feature slices with direct playtest or automated validation.
 
-- Avoid broad singleton state for feature-local behavior.
-- Avoid hard-coded node paths when a typed exported reference is clearer.
+## Validation
 
-## Pitfalls
-
-- `_process` and `_physics_process` serve different timing needs.
-- InputMap entries must exist before gameplay code can rely on them.
-
-## Verification Notes
-
-- Exercise the scene that owns the changed script.
-- Include manual input and physics checks when no automated test exists.
-
-## Role Notes
-
-- Gameplay programmers receive this reference by default for Godot projects.
-- Technical artists should use it when visual scripts or scene materials affect runtime behavior.
-
-## Official Links
-
-- https://docs.godotengine.org/en/stable/tutorials/scripting/index.html
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/godot/modules/animation.md b/engine_reference/godot/modules/animation.md
new file mode 100644
index 0000000..7dc421e
--- /dev/null
+++ b/engine_reference/godot/modules/animation.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.godotengine.org/en/stable/
+engine: godot
+version-reviewed: 4.4
+tags: godot,animation,state-machine,blend,timeline
+roles: gameplay-programmer,technical-artist,senior-game-artist,game-feel-designer
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Godot Animation Module Reference
+
+## Purpose
+
+Animation graphs, timelines, clips, blending, events, and animation-state debugging.
+
+## Guidance
+
+- Select this file only for animation-related tasks.
+- Keep implementation guidance scoped to Godot project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/godot/modules/audio.md b/engine_reference/godot/modules/audio.md
new file mode 100644
index 0000000..e74b411
--- /dev/null
+++ b/engine_reference/godot/modules/audio.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.godotengine.org/en/stable/
+engine: godot
+version-reviewed: 4.4
+tags: godot,audio,sound,music,sfx
+roles: audio-director,sound-designer,gameplay-programmer
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Godot Audio Module Reference
+
+## Purpose
+
+Music, SFX, voice, routing, mixers, spatial audio, and subtitle/accessibility coordination.
+
+## Guidance
+
+- Select this file only for audio-related tasks.
+- Keep implementation guidance scoped to Godot project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/godot/modules/input.md b/engine_reference/godot/modules/input.md
new file mode 100644
index 0000000..b8c2c38
--- /dev/null
+++ b/engine_reference/godot/modules/input.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.godotengine.org/en/stable/
+engine: godot
+version-reviewed: 4.4
+tags: godot,input,controls,accessibility,remap
+roles: gameplay-programmer,ui-programmer,accessibility-specialist,game-feel-designer
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Godot Input Module Reference
+
+## Purpose
+
+Input actions, rebinding, devices, accessibility, and control-scheme validation.
+
+## Guidance
+
+- Select this file only for input-related tasks.
+- Keep implementation guidance scoped to Godot project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/godot/modules/navigation.md b/engine_reference/godot/modules/navigation.md
new file mode 100644
index 0000000..c52d2f0
--- /dev/null
+++ b/engine_reference/godot/modules/navigation.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.godotengine.org/en/stable/
+engine: godot
+version-reviewed: 4.4
+tags: godot,navigation,navmesh,pathfinding,ai
+roles: ai-programmer,gameplay-programmer,level-designer
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Godot Navigation Module Reference
+
+## Purpose
+
+Navigation meshes, pathfinding, AI agents, steering, and level-authoring constraints.
+
+## Guidance
+
+- Select this file only for navigation-related tasks.
+- Keep implementation guidance scoped to Godot project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/godot/modules/networking.md b/engine_reference/godot/modules/networking.md
new file mode 100644
index 0000000..ed948d5
--- /dev/null
+++ b/engine_reference/godot/modules/networking.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.godotengine.org/en/stable/
+engine: godot
+version-reviewed: 4.4
+tags: godot,networking,multiplayer,replication,rollback
+roles: network-programmer,gameplay-programmer,qa-playtester
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Godot Networking Module Reference
+
+## Purpose
+
+Replication, rollback, authority, synchronization, server/client boundaries, and multiplayer test risk.
+
+## Guidance
+
+- Select this file only for networking-related tasks.
+- Keep implementation guidance scoped to Godot project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/godot/modules/physics.md b/engine_reference/godot/modules/physics.md
new file mode 100644
index 0000000..2d9028e
--- /dev/null
+++ b/engine_reference/godot/modules/physics.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.godotengine.org/en/stable/
+engine: godot
+version-reviewed: 4.4
+tags: godot,physics,collision,simulation,game-feel
+roles: gameplay-programmer,game-feel-designer,qa-playtester
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Godot Physics Module Reference
+
+## Purpose
+
+Collision, rigid bodies, physics queries, deterministic simulation risks, and game-feel tuning.
+
+## Guidance
+
+- Select this file only for physics-related tasks.
+- Keep implementation guidance scoped to Godot project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/godot/modules/rendering.md b/engine_reference/godot/modules/rendering.md
new file mode 100644
index 0000000..bf18fc9
--- /dev/null
+++ b/engine_reference/godot/modules/rendering.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.godotengine.org/en/stable/
+engine: godot
+version-reviewed: 4.4
+tags: godot,rendering,materials,lighting,performance
+roles: technical-artist,engine-programmer,performance-analyst
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Godot Rendering Module Reference
+
+## Purpose
+
+Materials, lighting, render pipelines, shaders, post-processing, and performance evidence.
+
+## Guidance
+
+- Select this file only for rendering-related tasks.
+- Keep implementation guidance scoped to Godot project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/godot/modules/ui.md b/engine_reference/godot/modules/ui.md
new file mode 100644
index 0000000..786465e
--- /dev/null
+++ b/engine_reference/godot/modules/ui.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.godotengine.org/en/stable/
+engine: godot
+version-reviewed: 4.4
+tags: godot,ui,ux,hud,accessibility
+roles: ui-programmer,ui-ux-designer,accessibility-specialist
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Godot UI Module Reference
+
+## Purpose
+
+HUDs, menus, widgets, focus, navigation, accessibility, and platform UI constraints.
+
+## Guidance
+
+- Select this file only for ui-related tasks.
+- Keep implementation guidance scoped to Godot project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/godot/plugins.md b/engine_reference/godot/plugins.md
index a06a3d5..70d9b3f 100644
--- a/engine_reference/godot/plugins.md
+++ b/engine_reference/godot/plugins.md
@@ -1,35 +1,26 @@
 reviewer: Open Game Studio seed review
-date: 2026-06-14
-source-link: https://docs.godotengine.org/en/stable/tutorials/plugins/editor/index.html
+date: 2026-06-17
+source-link: https://docs.godotengine.org/en/stable/
+engine: godot
+version-reviewed: 4.4
+tags: godot,plugins
+roles: tools-programmer,engine-programmer,godot-specialist
+workflows: prototype,bugfix,architecture-review,qa-plan
 
-# Godot Plugin Reference
+# Godot Plugin And Package Reference
 
-version-applicability: Godot 4.x editor plugins and export tooling.
+## Purpose
 
-## Prefer
+Guide plugin/package use without adding hidden runtime dependencies.
 
-- Keep editor plugins isolated under addon-style folders.
-- Document any editor restart or enablement step.
+## Guidance
 
-## Avoid
+- Prefer package-manager or marketplace sources that are reviewable in the project.
+- Record plugin version, install surface, and rollback risk.
+- Avoid requiring plugins for lightweight prototypes unless explicitly justified.
 
-- Avoid plugin side effects outside the active project.
-- Avoid relying on local editor-only absolute paths.
+## Validation
 
-## Pitfalls
-
-- Plugin activation state can differ between machines.
-- Export presets may hide missing resources until build time.
-
-## Verification Notes
-
-- Open the editor or run a documented export check after plugin changes.
-- Record plugin enablement and export preset changes.
-
-## Role Notes
-
-- Tools programmers and engine programmers receive this when relevant.
-
-## Official Links
-
-- https://docs.godotengine.org/en/stable/tutorials/plugins/editor/index.html
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/godot/specialist.md b/engine_reference/godot/specialist.md
index 584d5bc..8a9ae41 100644
--- a/engine_reference/godot/specialist.md
+++ b/engine_reference/godot/specialist.md
@@ -1,33 +1,26 @@
 reviewer: Open Game Studio seed review
-date: 2026-06-14
+date: 2026-06-17
 source-link: https://docs.godotengine.org/en/stable/
+engine: godot
+version-reviewed: 4.4
+tags: godot,specialist
+roles: godot-specialist
+workflows: prototype,bugfix,architecture-review,qa-plan
 
-# Godot Specialist Reference
+# Godot Engine Specialist Reference
 
-version-applicability: Godot 4.x specialist review and implementation.
+## Purpose
 
-## Prefer
+Guide the active engine specialist role with bounded, engine-specific review context.
 
-- Anchor advice in scenes, nodes, resources, signals, and ProjectSettings.
-- Keep generated guidance compact and task-specific.
+## Guidance
 
-## Avoid
+- Review engine idioms, project layout, version risks, plugins/packages, and validation commands.
+- Do not load references for other engines.
+- Escalate engine-version uncertainty instead of guessing.
 
-- Avoid Unity or Unreal terminology unless comparing a migration decision.
-- Avoid broad engine tutorials in prompts.
+## Validation
 
-## Pitfalls
-
-- Scene ownership, resource reuse, and autoload state can interact in subtle ways.
-
-## Verification Notes
-
-- Name the exact Godot editor/runtime command or manual check used.
-
-## Role Notes
-
-- `godot-specialist` should use this as the role-specific seed reference.
-
-## Official Links
-
-- https://docs.godotengine.org/en/stable/
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unity/VERSION.md b/engine_reference/unity/VERSION.md
index ddb42a8..a3369b6 100644
--- a/engine_reference/unity/VERSION.md
+++ b/engine_reference/unity/VERSION.md
@@ -1,35 +1,26 @@
 reviewer: Open Game Studio seed review
-date: 2026-06-14
+date: 2026-06-17
 source-link: https://docs.unity3d.com/Manual/index.html
+engine: unity
+version-reviewed: 6000.0
+tags: unity,VERSION
+roles: gameplay-programmer,engine-programmer,tools-programmer,technical-artist
+workflows: prototype,bugfix,architecture-review,qa-plan
 
 # Unity Version Reference
 
-version-applicability: Unity 2022 LTS and Unity 6 style projects unless project files state otherwise.
+## Purpose
 
-## Prefer
+Use this file to confirm the reviewed engine version, official documentation root, and version-sensitive assumptions before making implementation claims.
 
-- Use component-oriented scripts and keep serialized fields inspectable.
-- Treat ProjectSettings and package manifest changes as reviewable engine changes.
+## Guidance
 
-## Avoid
+- Match generated project engine version against this reviewed baseline.
+- Prefer official docs for version-specific APIs.
+- Record any project-local engine version drift in the handoff.
 
-- Do not edit Library or other generated Unity cache folders.
-- Do not assume package APIs without checking the manifest.
+## Validation
 
-## Pitfalls
-
-- Scene and prefab YAML changes can be noisy and order-sensitive.
-- Assembly definitions and packages can change compile boundaries.
-
-## Verification Notes
-
-- Run the configured Unity command or document an editor play-mode smoke check.
-- Report scenes, prefabs, scripts, packages, and settings touched.
-
-## Role Notes
-
-- Programmers should distinguish runtime script changes from editor or package changes.
-
-## Official Links
-
-- https://docs.unity3d.com/Manual/index.html
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unity/breaking-changes.md b/engine_reference/unity/breaking-changes.md
new file mode 100644
index 0000000..d49e40d
--- /dev/null
+++ b/engine_reference/unity/breaking-changes.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.unity3d.com/Manual/index.html
+engine: unity
+version-reviewed: 6000.0
+tags: unity,breaking,changes
+roles: gameplay-programmer,engine-programmer,qa-playtester,release-manager
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unity Breaking Changes
+
+## Purpose
+
+Surface version upgrade and compatibility risks before relying on engine behavior.
+
+## Guidance
+
+- Call out migration-sensitive APIs, package versions, serialization formats, and build settings.
+- Separate confirmed breaking changes from speculative compatibility risks.
+- Include rollback or compatibility notes for risky changes.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unity/current-best-practices.md b/engine_reference/unity/current-best-practices.md
new file mode 100644
index 0000000..6808b54
--- /dev/null
+++ b/engine_reference/unity/current-best-practices.md
@@ -0,0 +1,27 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.unity3d.com/Manual/index.html
+engine: unity
+version-reviewed: 6000.0
+tags: unity,current,best,practices
+roles: gameplay-programmer,engine-programmer,tools-programmer,technical-artist
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unity Current Best Practices
+
+## Purpose
+
+Apply current engine-native defaults without turning the task into broad process ceremony.
+
+## Guidance
+
+- Prefer engine-native composition and asset workflows.
+- Keep edits scoped to the requested role/task.
+- Mention scene, prefab, resource, project-setting, or asset-import changes explicitly.
+- Use local validation evidence before claiming readiness.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unity/deprecated-apis.md b/engine_reference/unity/deprecated-apis.md
new file mode 100644
index 0000000..7ee3299
--- /dev/null
+++ b/engine_reference/unity/deprecated-apis.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.unity3d.com/Manual/index.html
+engine: unity
+version-reviewed: 6000.0
+tags: unity,deprecated,apis
+roles: gameplay-programmer,engine-programmer,qa-playtester,performance-analyst
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unity Deprecated APIs
+
+## Purpose
+
+Avoid stale APIs and migration traps when editing or reviewing engine code.
+
+## Guidance
+
+- Check version-specific deprecations before copying older snippets.
+- Prefer supported APIs and document unavoidable legacy use.
+- Treat deprecated APIs as warnings unless the task is a migration or compatibility fix.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unity/gameplay.md b/engine_reference/unity/gameplay.md
index d18e22a..075d683 100644
--- a/engine_reference/unity/gameplay.md
+++ b/engine_reference/unity/gameplay.md
@@ -1,36 +1,26 @@
 reviewer: Open Game Studio seed review
-date: 2026-06-14
-source-link: https://docs.unity3d.com/Manual/CreatingAndUsingScripts.html
+date: 2026-06-17
+source-link: https://docs.unity3d.com/Manual/index.html
+engine: unity
+version-reviewed: 6000.0
+tags: unity,gameplay
+roles: gameplay-programmer,engine-programmer,tools-programmer,technical-artist
+workflows: prototype,bugfix,architecture-review,qa-plan
 
-# Unity Gameplay Reference
+# Unity Gameplay Implementation Reference
 
-version-applicability: Unity gameplay scripts, scenes, prefabs, and play-mode checks.
+## Purpose
 
-## Prefer
+Guide gameplay code with engine-native runtime patterns and verification evidence.
 
-- Keep MonoBehaviour responsibilities small and visible through serialized fields.
-- Use prefabs and scenes as explicit context when code depends on hierarchy.
+## Guidance
 
-## Avoid
+- Keep gameplay state deterministic where practical.
+- Separate authored content from generated/runtime data.
+- Prefer small feature slices with direct playtest or automated validation.
 
-- Avoid hidden scene-object lookup chains when dependencies can be assigned.
-- Avoid editing generated project caches.
+## Validation
 
-## Pitfalls
-
-- Script execution order and physics timestep can affect gameplay behavior.
-- Prefab overrides may not be obvious from script diffs alone.
-
-## Verification Notes
-
-- Run available edit-mode or play-mode tests, or document a play-mode check.
-- Name the scene or prefab used for manual verification.
-
-## Role Notes
-
-- Gameplay programmers receive this reference by default for Unity projects.
-- Technical artists should cite material, shader, or prefab runtime impact.
-
-## Official Links
-
-- https://docs.unity3d.com/Manual/CreatingAndUsingScripts.html
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unity/modules/animation.md b/engine_reference/unity/modules/animation.md
new file mode 100644
index 0000000..62638b0
--- /dev/null
+++ b/engine_reference/unity/modules/animation.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.unity3d.com/Manual/index.html
+engine: unity
+version-reviewed: 6000.0
+tags: unity,animation,state-machine,blend,timeline
+roles: gameplay-programmer,technical-artist,senior-game-artist,game-feel-designer
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unity Animation Module Reference
+
+## Purpose
+
+Animation graphs, timelines, clips, blending, events, and animation-state debugging.
+
+## Guidance
+
+- Select this file only for animation-related tasks.
+- Keep implementation guidance scoped to Unity project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unity/modules/audio.md b/engine_reference/unity/modules/audio.md
new file mode 100644
index 0000000..8b67734
--- /dev/null
+++ b/engine_reference/unity/modules/audio.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.unity3d.com/Manual/index.html
+engine: unity
+version-reviewed: 6000.0
+tags: unity,audio,sound,music,sfx
+roles: audio-director,sound-designer,gameplay-programmer
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unity Audio Module Reference
+
+## Purpose
+
+Music, SFX, voice, routing, mixers, spatial audio, and subtitle/accessibility coordination.
+
+## Guidance
+
+- Select this file only for audio-related tasks.
+- Keep implementation guidance scoped to Unity project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unity/modules/input.md b/engine_reference/unity/modules/input.md
new file mode 100644
index 0000000..c1fdecb
--- /dev/null
+++ b/engine_reference/unity/modules/input.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.unity3d.com/Manual/index.html
+engine: unity
+version-reviewed: 6000.0
+tags: unity,input,controls,accessibility,remap
+roles: gameplay-programmer,ui-programmer,accessibility-specialist,game-feel-designer
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unity Input Module Reference
+
+## Purpose
+
+Input actions, rebinding, devices, accessibility, and control-scheme validation.
+
+## Guidance
+
+- Select this file only for input-related tasks.
+- Keep implementation guidance scoped to Unity project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unity/modules/navigation.md b/engine_reference/unity/modules/navigation.md
new file mode 100644
index 0000000..c4fb238
--- /dev/null
+++ b/engine_reference/unity/modules/navigation.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.unity3d.com/Manual/index.html
+engine: unity
+version-reviewed: 6000.0
+tags: unity,navigation,navmesh,pathfinding,ai
+roles: ai-programmer,gameplay-programmer,level-designer
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unity Navigation Module Reference
+
+## Purpose
+
+Navigation meshes, pathfinding, AI agents, steering, and level-authoring constraints.
+
+## Guidance
+
+- Select this file only for navigation-related tasks.
+- Keep implementation guidance scoped to Unity project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unity/modules/networking.md b/engine_reference/unity/modules/networking.md
new file mode 100644
index 0000000..99f4490
--- /dev/null
+++ b/engine_reference/unity/modules/networking.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.unity3d.com/Manual/index.html
+engine: unity
+version-reviewed: 6000.0
+tags: unity,networking,multiplayer,replication,rollback
+roles: network-programmer,gameplay-programmer,qa-playtester
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unity Networking Module Reference
+
+## Purpose
+
+Replication, rollback, authority, synchronization, server/client boundaries, and multiplayer test risk.
+
+## Guidance
+
+- Select this file only for networking-related tasks.
+- Keep implementation guidance scoped to Unity project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unity/modules/physics.md b/engine_reference/unity/modules/physics.md
new file mode 100644
index 0000000..e285d5f
--- /dev/null
+++ b/engine_reference/unity/modules/physics.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.unity3d.com/Manual/index.html
+engine: unity
+version-reviewed: 6000.0
+tags: unity,physics,collision,simulation,game-feel
+roles: gameplay-programmer,game-feel-designer,qa-playtester
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unity Physics Module Reference
+
+## Purpose
+
+Collision, rigid bodies, physics queries, deterministic simulation risks, and game-feel tuning.
+
+## Guidance
+
+- Select this file only for physics-related tasks.
+- Keep implementation guidance scoped to Unity project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unity/modules/rendering.md b/engine_reference/unity/modules/rendering.md
new file mode 100644
index 0000000..4698bbf
--- /dev/null
+++ b/engine_reference/unity/modules/rendering.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.unity3d.com/Manual/index.html
+engine: unity
+version-reviewed: 6000.0
+tags: unity,rendering,materials,lighting,performance
+roles: technical-artist,engine-programmer,performance-analyst
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unity Rendering Module Reference
+
+## Purpose
+
+Materials, lighting, render pipelines, shaders, post-processing, and performance evidence.
+
+## Guidance
+
+- Select this file only for rendering-related tasks.
+- Keep implementation guidance scoped to Unity project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unity/modules/ui.md b/engine_reference/unity/modules/ui.md
new file mode 100644
index 0000000..5cc9100
--- /dev/null
+++ b/engine_reference/unity/modules/ui.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.unity3d.com/Manual/index.html
+engine: unity
+version-reviewed: 6000.0
+tags: unity,ui,ux,hud,accessibility
+roles: ui-programmer,ui-ux-designer,accessibility-specialist
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unity UI Module Reference
+
+## Purpose
+
+HUDs, menus, widgets, focus, navigation, accessibility, and platform UI constraints.
+
+## Guidance
+
+- Select this file only for ui-related tasks.
+- Keep implementation guidance scoped to Unity project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unity/plugins.md b/engine_reference/unity/plugins.md
index 4f43307..042ac27 100644
--- a/engine_reference/unity/plugins.md
+++ b/engine_reference/unity/plugins.md
@@ -1,34 +1,26 @@
 reviewer: Open Game Studio seed review
-date: 2026-06-14
-source-link: https://docs.unity3d.com/Manual/Packages.html
+date: 2026-06-17
+source-link: https://docs.unity3d.com/Manual/index.html
+engine: unity
+version-reviewed: 6000.0
+tags: unity,plugins
+roles: tools-programmer,engine-programmer,unity-specialist
+workflows: prototype,bugfix,architecture-review,qa-plan
 
-# Unity Package And Plugin Reference
+# Unity Plugin And Package Reference
 
-version-applicability: Unity package manifest, editor tooling, and plugin integrations.
+## Purpose
 
-## Prefer
+Guide plugin/package use without adding hidden runtime dependencies.
 
-- Keep package changes explicit in `Packages/manifest.json`.
-- Separate editor-only code from runtime assemblies.
+## Guidance
 
-## Avoid
+- Prefer package-manager or marketplace sources that are reviewable in the project.
+- Record plugin version, install surface, and rollback risk.
+- Avoid requiring plugins for lightweight prototypes unless explicitly justified.
 
-- Avoid machine-local package paths unless the task explicitly requires them.
-- Avoid broad editor automation that mutates unrelated assets.
+## Validation
 
-## Pitfalls
-
-- Package resolution can differ across Unity versions.
-- Editor scripts can run during import and produce unexpected asset changes.
-
-## Verification Notes
-
-- Report package manifest diffs and any editor menu or importer smoke check.
-
-## Role Notes
-
-- Tools programmers and engine programmers receive this when package or editor work is relevant.
-
-## Official Links
-
-- https://docs.unity3d.com/Manual/Packages.html
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unity/plugins/addressables.md b/engine_reference/unity/plugins/addressables.md
new file mode 100644
index 0000000..67911ba
--- /dev/null
+++ b/engine_reference/unity/plugins/addressables.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.unity3d.com/Manual/index.html
+engine: unity
+version-reviewed: 6000.0
+tags: unity,addressables,assets,content
+roles: tools-programmer,engine-programmer,technical-artist,unity-specialist
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unity Unity Addressables Reference
+
+## Purpose
+
+Addressables asset loading, groups, labels, profiles, content updates, and runtime memory risk.
+
+## Guidance
+
+- Select this reference only when the task names or clearly implies Addressables.
+- Identify package/plugin version, project files changed, and validation evidence.
+- Avoid making this plugin mandatory for unrelated lightweight prototype work.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unity/plugins/cinemachine.md b/engine_reference/unity/plugins/cinemachine.md
new file mode 100644
index 0000000..93bf086
--- /dev/null
+++ b/engine_reference/unity/plugins/cinemachine.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.unity3d.com/Manual/index.html
+engine: unity
+version-reviewed: 6000.0
+tags: unity,cinemachine,camera,game-feel
+roles: gameplay-programmer,technical-artist,game-feel-designer,unity-specialist
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unity Unity Cinemachine Reference
+
+## Purpose
+
+Camera rigs, follow/look-at targets, confiners, camera blending, and game-feel validation.
+
+## Guidance
+
+- Select this reference only when the task names or clearly implies Cinemachine.
+- Identify package/plugin version, project files changed, and validation evidence.
+- Avoid making this plugin mandatory for unrelated lightweight prototype work.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unity/plugins/dots.md b/engine_reference/unity/plugins/dots.md
new file mode 100644
index 0000000..c2a96be
--- /dev/null
+++ b/engine_reference/unity/plugins/dots.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://docs.unity3d.com/Manual/index.html
+engine: unity
+version-reviewed: 6000.0
+tags: unity,dots,ecs,performance
+roles: engine-programmer,performance-analyst,unity-specialist
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unity Unity DOTS Reference
+
+## Purpose
+
+Entities, Jobs, Burst, data-oriented design, and profiling gates for ECS-style work.
+
+## Guidance
+
+- Select this reference only when the task names or clearly implies DOTS.
+- Identify package/plugin version, project files changed, and validation evidence.
+- Avoid making this plugin mandatory for unrelated lightweight prototype work.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unity/specialist.md b/engine_reference/unity/specialist.md
index 36c7bf0..2b9d305 100644
--- a/engine_reference/unity/specialist.md
+++ b/engine_reference/unity/specialist.md
@@ -1,33 +1,26 @@
 reviewer: Open Game Studio seed review
-date: 2026-06-14
+date: 2026-06-17
 source-link: https://docs.unity3d.com/Manual/index.html
+engine: unity
+version-reviewed: 6000.0
+tags: unity,specialist
+roles: unity-specialist
+workflows: prototype,bugfix,architecture-review,qa-plan
 
-# Unity Specialist Reference
+# Unity Engine Specialist Reference
 
-version-applicability: Unity specialist review and implementation across runtime and editor surfaces.
+## Purpose
 
-## Prefer
+Guide the active engine specialist role with bounded, engine-specific review context.
 
-- Anchor advice in scenes, prefabs, packages, assembly definitions, and ProjectSettings.
-- Keep recommendations aligned with the active Unity version.
+## Guidance
 
-## Avoid
+- Review engine idioms, project layout, version risks, plugins/packages, and validation commands.
+- Do not load references for other engines.
+- Escalate engine-version uncertainty instead of guessing.
 
-- Avoid Unreal or Godot concepts unless the task is migration-oriented.
-- Avoid loading all engine docs into general gameplay prompts.
+## Validation
 
-## Pitfalls
-
-- YAML asset diffs can hide meaningful prefab or scene overrides.
-
-## Verification Notes
-
-- Name editor, play-mode, package, or build validation used.
-
-## Role Notes
-
-- `unity-specialist` should use this as the role-specific seed reference.
-
-## Official Links
-
-- https://docs.unity3d.com/Manual/index.html
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unreal/VERSION.md b/engine_reference/unreal/VERSION.md
index f1f1f67..7a54281 100644
--- a/engine_reference/unreal/VERSION.md
+++ b/engine_reference/unreal/VERSION.md
@@ -1,35 +1,26 @@
 reviewer: Open Game Studio seed review
-date: 2026-06-14
-source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine
+date: 2026-06-17
+source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine/
+engine: unreal
+version-reviewed: 5.5
+tags: unreal,VERSION
+roles: gameplay-programmer,engine-programmer,tools-programmer,technical-artist
+workflows: prototype,bugfix,architecture-review,qa-plan
 
 # Unreal Version Reference
 
-version-applicability: Unreal Engine 5.x projects unless project files state otherwise.
+## Purpose
 
-## Prefer
+Use this file to confirm the reviewed engine version, official documentation root, and version-sensitive assumptions before making implementation claims.
 
-- Keep C++, Blueprint, module, and plugin changes explicit in handoff notes.
-- Treat `.uproject`, `.uplugin`, and build file edits as engine-level changes.
+## Guidance
 
-## Avoid
+- Match generated project engine version against this reviewed baseline.
+- Prefer official docs for version-specific APIs.
+- Record any project-local engine version drift in the handoff.
 
-- Do not edit DerivedDataCache, Intermediate, or Saved outputs.
-- Do not assume Blueprint behavior from C++ diffs alone.
+## Validation
 
-## Pitfalls
-
-- Reflection macros, module dependencies, and asset references can fail late.
-- Blueprint assets may need editor validation even after C++ compiles.
-
-## Verification Notes
-
-- Run the configured Unreal build/test command or document an editor smoke check.
-- Report maps, Blueprints, modules, plugins, and config files touched.
-
-## Role Notes
-
-- Programmers should identify whether changes affect runtime, editor, or build tooling.
-
-## Official Links
-
-- https://dev.epicgames.com/documentation/en-us/unreal-engine
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unreal/breaking-changes.md b/engine_reference/unreal/breaking-changes.md
new file mode 100644
index 0000000..39beacf
--- /dev/null
+++ b/engine_reference/unreal/breaking-changes.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine/
+engine: unreal
+version-reviewed: 5.5
+tags: unreal,breaking,changes
+roles: gameplay-programmer,engine-programmer,qa-playtester,release-manager
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unreal Breaking Changes
+
+## Purpose
+
+Surface version upgrade and compatibility risks before relying on engine behavior.
+
+## Guidance
+
+- Call out migration-sensitive APIs, package versions, serialization formats, and build settings.
+- Separate confirmed breaking changes from speculative compatibility risks.
+- Include rollback or compatibility notes for risky changes.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unreal/current-best-practices.md b/engine_reference/unreal/current-best-practices.md
new file mode 100644
index 0000000..688a6d6
--- /dev/null
+++ b/engine_reference/unreal/current-best-practices.md
@@ -0,0 +1,27 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine/
+engine: unreal
+version-reviewed: 5.5
+tags: unreal,current,best,practices
+roles: gameplay-programmer,engine-programmer,tools-programmer,technical-artist
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unreal Current Best Practices
+
+## Purpose
+
+Apply current engine-native defaults without turning the task into broad process ceremony.
+
+## Guidance
+
+- Prefer engine-native composition and asset workflows.
+- Keep edits scoped to the requested role/task.
+- Mention scene, prefab, resource, project-setting, or asset-import changes explicitly.
+- Use local validation evidence before claiming readiness.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unreal/deprecated-apis.md b/engine_reference/unreal/deprecated-apis.md
new file mode 100644
index 0000000..27a8ff0
--- /dev/null
+++ b/engine_reference/unreal/deprecated-apis.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine/
+engine: unreal
+version-reviewed: 5.5
+tags: unreal,deprecated,apis
+roles: gameplay-programmer,engine-programmer,qa-playtester,performance-analyst
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unreal Deprecated APIs
+
+## Purpose
+
+Avoid stale APIs and migration traps when editing or reviewing engine code.
+
+## Guidance
+
+- Check version-specific deprecations before copying older snippets.
+- Prefer supported APIs and document unavoidable legacy use.
+- Treat deprecated APIs as warnings unless the task is a migration or compatibility fix.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unreal/gameplay.md b/engine_reference/unreal/gameplay.md
index 536f9ef..27d2c77 100644
--- a/engine_reference/unreal/gameplay.md
+++ b/engine_reference/unreal/gameplay.md
@@ -1,36 +1,26 @@
 reviewer: Open Game Studio seed review
-date: 2026-06-14
-source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine/programming-with-cplusplus-in-unreal-engine
+date: 2026-06-17
+source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine/
+engine: unreal
+version-reviewed: 5.5
+tags: unreal,gameplay
+roles: gameplay-programmer,engine-programmer,tools-programmer,technical-artist
+workflows: prototype,bugfix,architecture-review,qa-plan
 
-# Unreal Gameplay Reference
+# Unreal Gameplay Implementation Reference
 
-version-applicability: Unreal Engine 5.x gameplay C++, Blueprints, maps, and input setup.
+## Purpose
 
-## Prefer
+Guide gameplay code with engine-native runtime patterns and verification evidence.
 
-- Keep gameplay state ownership clear across Actors, Components, Pawns, and GameMode.
-- Mention Blueprint dependencies when C++ behavior expects asset wiring.
+## Guidance
 
-## Avoid
+- Keep gameplay state deterministic where practical.
+- Separate authored content from generated/runtime data.
+- Prefer small feature slices with direct playtest or automated validation.
 
-- Avoid unreviewed changes to generated project files or caches.
-- Avoid broad asset edits without naming the map or Blueprint.
+## Validation
 
-## Pitfalls
-
-- UPROPERTY and UFUNCTION metadata affects editor and Blueprint behavior.
-- Enhanced Input setup may live in assets as well as code.
-
-## Verification Notes
-
-- Run available automation or document PIE/editor smoke checks.
-- Include compile, map load, and input checks where relevant.
-
-## Role Notes
-
-- Gameplay programmers receive this reference by default for Unreal projects.
-- Technical artists should cite material, Blueprint, or asset pipeline effects.
-
-## Official Links
-
-- https://dev.epicgames.com/documentation/en-us/unreal-engine/programming-with-cplusplus-in-unreal-engine
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unreal/modules/animation.md b/engine_reference/unreal/modules/animation.md
new file mode 100644
index 0000000..91d99e0
--- /dev/null
+++ b/engine_reference/unreal/modules/animation.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine/
+engine: unreal
+version-reviewed: 5.5
+tags: unreal,animation,state-machine,blend,timeline
+roles: gameplay-programmer,technical-artist,senior-game-artist,game-feel-designer
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unreal Animation Module Reference
+
+## Purpose
+
+Animation graphs, timelines, clips, blending, events, and animation-state debugging.
+
+## Guidance
+
+- Select this file only for animation-related tasks.
+- Keep implementation guidance scoped to Unreal project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unreal/modules/audio.md b/engine_reference/unreal/modules/audio.md
new file mode 100644
index 0000000..cf508fb
--- /dev/null
+++ b/engine_reference/unreal/modules/audio.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine/
+engine: unreal
+version-reviewed: 5.5
+tags: unreal,audio,sound,music,sfx
+roles: audio-director,sound-designer,gameplay-programmer
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unreal Audio Module Reference
+
+## Purpose
+
+Music, SFX, voice, routing, mixers, spatial audio, and subtitle/accessibility coordination.
+
+## Guidance
+
+- Select this file only for audio-related tasks.
+- Keep implementation guidance scoped to Unreal project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unreal/modules/input.md b/engine_reference/unreal/modules/input.md
new file mode 100644
index 0000000..dcf2518
--- /dev/null
+++ b/engine_reference/unreal/modules/input.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine/
+engine: unreal
+version-reviewed: 5.5
+tags: unreal,input,controls,accessibility,remap
+roles: gameplay-programmer,ui-programmer,accessibility-specialist,game-feel-designer
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unreal Input Module Reference
+
+## Purpose
+
+Input actions, rebinding, devices, accessibility, and control-scheme validation.
+
+## Guidance
+
+- Select this file only for input-related tasks.
+- Keep implementation guidance scoped to Unreal project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unreal/modules/navigation.md b/engine_reference/unreal/modules/navigation.md
new file mode 100644
index 0000000..b125ceb
--- /dev/null
+++ b/engine_reference/unreal/modules/navigation.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine/
+engine: unreal
+version-reviewed: 5.5
+tags: unreal,navigation,navmesh,pathfinding,ai
+roles: ai-programmer,gameplay-programmer,level-designer
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unreal Navigation Module Reference
+
+## Purpose
+
+Navigation meshes, pathfinding, AI agents, steering, and level-authoring constraints.
+
+## Guidance
+
+- Select this file only for navigation-related tasks.
+- Keep implementation guidance scoped to Unreal project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unreal/modules/networking.md b/engine_reference/unreal/modules/networking.md
new file mode 100644
index 0000000..2be0f8e
--- /dev/null
+++ b/engine_reference/unreal/modules/networking.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine/
+engine: unreal
+version-reviewed: 5.5
+tags: unreal,networking,multiplayer,replication,rollback
+roles: network-programmer,gameplay-programmer,qa-playtester
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unreal Networking Module Reference
+
+## Purpose
+
+Replication, rollback, authority, synchronization, server/client boundaries, and multiplayer test risk.
+
+## Guidance
+
+- Select this file only for networking-related tasks.
+- Keep implementation guidance scoped to Unreal project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unreal/modules/physics.md b/engine_reference/unreal/modules/physics.md
new file mode 100644
index 0000000..aebf8ea
--- /dev/null
+++ b/engine_reference/unreal/modules/physics.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine/
+engine: unreal
+version-reviewed: 5.5
+tags: unreal,physics,collision,simulation,game-feel
+roles: gameplay-programmer,game-feel-designer,qa-playtester
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unreal Physics Module Reference
+
+## Purpose
+
+Collision, rigid bodies, physics queries, deterministic simulation risks, and game-feel tuning.
+
+## Guidance
+
+- Select this file only for physics-related tasks.
+- Keep implementation guidance scoped to Unreal project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unreal/modules/rendering.md b/engine_reference/unreal/modules/rendering.md
new file mode 100644
index 0000000..439e4d5
--- /dev/null
+++ b/engine_reference/unreal/modules/rendering.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine/
+engine: unreal
+version-reviewed: 5.5
+tags: unreal,rendering,materials,lighting,performance
+roles: technical-artist,engine-programmer,performance-analyst
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unreal Rendering Module Reference
+
+## Purpose
+
+Materials, lighting, render pipelines, shaders, post-processing, and performance evidence.
+
+## Guidance
+
+- Select this file only for rendering-related tasks.
+- Keep implementation guidance scoped to Unreal project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unreal/modules/ui.md b/engine_reference/unreal/modules/ui.md
new file mode 100644
index 0000000..10e5ba7
--- /dev/null
+++ b/engine_reference/unreal/modules/ui.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine/
+engine: unreal
+version-reviewed: 5.5
+tags: unreal,ui,ux,hud,accessibility
+roles: ui-programmer,ui-ux-designer,accessibility-specialist
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unreal UI Module Reference
+
+## Purpose
+
+HUDs, menus, widgets, focus, navigation, accessibility, and platform UI constraints.
+
+## Guidance
+
+- Select this file only for ui-related tasks.
+- Keep implementation guidance scoped to Unreal project files and validation commands.
+- Include performance, accessibility, and content-pipeline risks when they apply.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unreal/plugins.md b/engine_reference/unreal/plugins.md
index 1023444..cef418d 100644
--- a/engine_reference/unreal/plugins.md
+++ b/engine_reference/unreal/plugins.md
@@ -1,34 +1,26 @@
 reviewer: Open Game Studio seed review
-date: 2026-06-14
-source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine/plugins-in-unreal-engine
+date: 2026-06-17
+source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine/
+engine: unreal
+version-reviewed: 5.5
+tags: unreal,plugins
+roles: tools-programmer,engine-programmer,unreal-specialist
+workflows: prototype,bugfix,architecture-review,qa-plan
 
-# Unreal Plugin Reference
+# Unreal Plugin And Package Reference
 
-version-applicability: Unreal Engine 5.x plugins, modules, and editor tooling.
+## Purpose
 
-## Prefer
+Guide plugin/package use without adding hidden runtime dependencies.
 
-- Keep plugin descriptors, module rules, and dependencies explicit.
-- Separate editor modules from runtime modules.
+## Guidance
 
-## Avoid
+- Prefer package-manager or marketplace sources that are reviewable in the project.
+- Record plugin version, install surface, and rollback risk.
+- Avoid requiring plugins for lightweight prototypes unless explicitly justified.
 
-- Avoid plugin changes that require global engine installation edits.
-- Avoid generated binary or intermediate outputs.
+## Validation
 
-## Pitfalls
-
-- Module loading phases and dependency lists can break packaged builds.
-- Editor-only APIs can leak into runtime modules.
-
-## Verification Notes
-
-- Report build target, editor startup, and plugin enablement checks.
-
-## Role Notes
-
-- Tools programmers and engine programmers receive this when plugin or module work is relevant.
-
-## Official Links
-
-- https://dev.epicgames.com/documentation/en-us/unreal-engine/plugins-in-unreal-engine
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unreal/plugins/common-ui.md b/engine_reference/unreal/plugins/common-ui.md
new file mode 100644
index 0000000..b317914
--- /dev/null
+++ b/engine_reference/unreal/plugins/common-ui.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine/
+engine: unreal
+version-reviewed: 5.5
+tags: unreal,common-ui,ui,input
+roles: ui-programmer,ui-ux-designer,accessibility-specialist,unreal-specialist
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unreal Unreal Common UI Reference
+
+## Purpose
+
+Common UI activatable widgets, input routing, platform prompts, and menu-stack behavior.
+
+## Guidance
+
+- Select this reference only when the task names or clearly implies Common.
+- Identify package/plugin version, project files changed, and validation evidence.
+- Avoid making this plugin mandatory for unrelated lightweight prototype work.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unreal/plugins/gas.md b/engine_reference/unreal/plugins/gas.md
new file mode 100644
index 0000000..6d70d95
--- /dev/null
+++ b/engine_reference/unreal/plugins/gas.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine/
+engine: unreal
+version-reviewed: 5.5
+tags: unreal,gas,abilities,networking
+roles: gameplay-programmer,systems-designer,network-programmer,unreal-specialist
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unreal Unreal GAS Reference
+
+## Purpose
+
+Gameplay Ability System abilities, attributes, effects, tags, prediction, and replication risk.
+
+## Guidance
+
+- Select this reference only when the task names or clearly implies GAS.
+- Identify package/plugin version, project files changed, and validation evidence.
+- Avoid making this plugin mandatory for unrelated lightweight prototype work.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unreal/plugins/pcg.md b/engine_reference/unreal/plugins/pcg.md
new file mode 100644
index 0000000..08c144a
--- /dev/null
+++ b/engine_reference/unreal/plugins/pcg.md
@@ -0,0 +1,26 @@
+reviewer: Open Game Studio seed review
+date: 2026-06-17
+source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine/
+engine: unreal
+version-reviewed: 5.5
+tags: unreal,pcg,procedural,level-design
+roles: level-designer,technical-artist,tools-programmer,unreal-specialist
+workflows: prototype,bugfix,architecture-review,qa-plan
+
+# Unreal Unreal PCG Reference
+
+## Purpose
+
+Procedural Content Generation graphs, volumes, data flow, generation bounds, and artist review.
+
+## Guidance
+
+- Select this reference only when the task names or clearly implies PCG.
+- Identify package/plugin version, project files changed, and validation evidence.
+- Avoid making this plugin mandatory for unrelated lightweight prototype work.
+
+## Validation
+
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/engine_reference/unreal/specialist.md b/engine_reference/unreal/specialist.md
index c910d2c..d012290 100644
--- a/engine_reference/unreal/specialist.md
+++ b/engine_reference/unreal/specialist.md
@@ -1,33 +1,26 @@
 reviewer: Open Game Studio seed review
-date: 2026-06-14
-source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine
+date: 2026-06-17
+source-link: https://dev.epicgames.com/documentation/en-us/unreal-engine/
+engine: unreal
+version-reviewed: 5.5
+tags: unreal,specialist
+roles: unreal-specialist
+workflows: prototype,bugfix,architecture-review,qa-plan
 
-# Unreal Specialist Reference
+# Unreal Engine Specialist Reference
 
-version-applicability: Unreal Engine 5.x specialist review and implementation.
+## Purpose
 
-## Prefer
+Guide the active engine specialist role with bounded, engine-specific review context.
 
-- Anchor advice in modules, Actors, Components, Blueprints, maps, plugins, and config.
-- Keep guidance tied to the active project and role.
+## Guidance
 
-## Avoid
+- Review engine idioms, project layout, version risks, plugins/packages, and validation commands.
+- Do not load references for other engines.
+- Escalate engine-version uncertainty instead of guessing.
 
-- Avoid Godot or Unity terminology unless the task is migration-oriented.
-- Avoid including Unreal-only docs in non-Unreal prompts by default.
+## Validation
 
-## Pitfalls
-
-- Blueprint/editor state can make code-only review incomplete.
-
-## Verification Notes
-
-- Name build, automation, PIE, map-load, or packaging checks used.
-
-## Role Notes
-
-- `unreal-specialist` should use this as the role-specific seed reference.
-
-## Official Links
-
-- https://dev.epicgames.com/documentation/en-us/unreal-engine
+- Prefer project-local engine commands and Open Game Studio project validation before readiness claims.
+- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
+- Keep this reference selected by relevance; do not load every engine reference for one task.
diff --git a/openspec/changes/catch-up-behavioral-evaluation/.openspec.yaml b/openspec/changes/catch-up-behavioral-evaluation/.openspec.yaml
new file mode 100644
index 0000000..3ac681e
--- /dev/null
+++ b/openspec/changes/catch-up-behavioral-evaluation/.openspec.yaml
@@ -0,0 +1,2 @@
+schema: spec-driven
+created: 2026-06-17
diff --git a/openspec/changes/catch-up-behavioral-evaluation/README.md b/openspec/changes/catch-up-behavioral-evaluation/README.md
new file mode 100644
index 0000000..d74bc4a
--- /dev/null
+++ b/openspec/changes/catch-up-behavioral-evaluation/README.md
@@ -0,0 +1,3 @@
+# catch-up-behavioral-evaluation
+
+Plan Open Game Studio improvements for catch-up-behavioral-evaluation relative to CCGS within the Codex-native product boundary
diff --git a/openspec/changes/catch-up-behavioral-evaluation/design.md b/openspec/changes/catch-up-behavioral-evaluation/design.md
new file mode 100644
index 0000000..1bd0301
--- /dev/null
+++ b/openspec/changes/catch-up-behavioral-evaluation/design.md
@@ -0,0 +1,32 @@
+# Behavioral Evaluation Catch-Up Design
+
+## Architecture
+Add a lightweight, local, deterministic behavioral evaluation framework for OGS roles/workflows/templates that catches weak prompt contracts without requiring hosted evaluators or telemetry. The implementation should extend the existing TypeScript registries and renderers instead of introducing a separate orchestration platform. Built-in depth belongs in package-shipped registries/assets; project-specific depth belongs in explicit reviewable local files.
+
+## Current Gap Evidence
+Open Game Studio validates CLI and generated-surface mechanics, but CCGS includes a skill/agent testing framework and rubrics that evaluate workflow and prompt behavior more directly.
+
+## Key Decisions
+1. Preserve Open Game Studio's local-first, Codex-native runtime.
+2. Make added depth discoverable and validated, but do not force it into every prompt.
+3. Select context by role/workflow/task relevance; never load all roles, all workflows, all templates, or all engine references for one run.
+4. Keep implementation tasks test-first and package-smoke verified where package assets change.
+
+## Data And Surface Contracts
+- `tests/`
+- `src/validation.ts`
+- `src/codex-prompts.ts`
+- `src/workflows.ts`
+- `docs/system-verification.md`
+- `docs/workflow-validation.md`
+- `package.json`
+
+## Alternatives Rejected
+- Directly copying CCGS `.claude/**` files into generated projects: rejected because OGS is Codex-native and uses `AGENTS.md` / `.codex/**`.
+- Adding a general agent orchestrator or background controller: rejected by product boundary.
+- Adding broad prompt bundles that include every reference file: rejected because depth must come from selected context.
+
+## Risks And Mitigations
+- Prompt bloat: add renderer tests and selected-context assertions.
+- Registry drift: update validation to fail when a registry entry lacks materialized/generated/package coverage.
+- Product-boundary drift: keep future-only/deferred surfaces absent and add negative tests when relevant.
diff --git a/openspec/changes/catch-up-behavioral-evaluation/proposal.md b/openspec/changes/catch-up-behavioral-evaluation/proposal.md
new file mode 100644
index 0000000..dbd3843
--- /dev/null
+++ b/openspec/changes/catch-up-behavioral-evaluation/proposal.md
@@ -0,0 +1,30 @@
+# Behavioral Evaluation Catch-Up Proposal
+
+## Why
+Open Game Studio validates CLI and generated-surface mechanics, but CCGS includes a skill/agent testing framework and rubrics that evaluate workflow and prompt behavior more directly.
+
+Current comparison baseline:
+- Open Game Studio: 20 roles, 13 workflow prompt shortcuts, 13 templates, 12 engine-reference files, TypeScript CLI/package, Codex-native run path, validation gate.
+- Claude Code Game Studios: 49 agents, 73 skills, 40 templates, 46 engine-reference files, richer authored specialist prompts and skill/testing framework.
+- Explicitly ignored/deferred for Open Game Studio: telemetry, planner/next, parallel orchestration, hard output-ownership enforcement, hosted service/daemon/background controller, hidden memory/checkpoints, non-Codex runtime replacements, mandatory heavyweight lifecycle.
+
+
+## What Changes
+- Define an evaluation fixture format for role/workflow scenarios with expected prompt obligations and forbidden drift.
+- Add static behavior checks for required sections, relevant templates, selected context, forbidden future-only surfaces, and output contract coverage.
+- Add representative scenarios for core workflows and new catch-up roles.
+- Expose evaluation through npm scripts or validation subchecks only if it stays local and deterministic.
+- Document how to add a scenario when a role/workflow is added.
+
+## Product Boundary Check
+- Improves: Add a lightweight, local, deterministic behavioral evaluation framework for OGS roles/workflows/templates that catches weak prompt contracts without requiring hosted evaluators or telemetry.
+- In-scope surfaces: tests/, src/validation.ts, src/codex-prompts.ts, src/workflows.ts, docs/system-verification.md, docs/workflow-validation.md, package.json
+- Lightweight prototype use: preserved; new depth is opt-in and selected by role/workflow relevance.
+- Codex-native contract: preserved; built around `AGENTS.md`, `.codex/**`, npm package assets, and `opengamestudio` commands.
+- Reviewable evidence: source files, generated project files, tests, validation output, and OpenSpec artifacts.
+- Explicit non-goals: no telemetry, planner/next, parallel orchestration, hosted daemon, hidden memory, non-Codex runtime replacement, or mandatory heavyweight lifecycle.
+
+## Impact
+- Source: tests/, src/validation.ts, src/codex-prompts.ts, src/workflows.ts, docs/system-verification.md, docs/workflow-validation.md, package.json
+- Tests: focused Vitest suites plus `npm run validate`.
+- Docs/truth: update routed Truthmark engineering/product docs only when implementation changes behavior; this proposal itself is planning-only.
diff --git a/openspec/changes/catch-up-behavioral-evaluation/specs/codex-studio-behavioral-evaluation/spec.md b/openspec/changes/catch-up-behavioral-evaluation/specs/codex-studio-behavioral-evaluation/spec.md
new file mode 100644
index 0000000..ff00b7e
--- /dev/null
+++ b/openspec/changes/catch-up-behavioral-evaluation/specs/codex-studio-behavioral-evaluation/spec.md
@@ -0,0 +1,30 @@
+# Behavioral Evaluation Catch-Up Specification
+
+## ADDED Requirements
+
+### Requirement: Local deterministic evals
+Behavioral evaluations SHALL run locally without hosted services, telemetry, hidden memory, or LLM calls by default.
+
+#### Scenario: A ship-check workflow scenario runs
+- **GIVEN** a ship-check workflow scenario runs
+- **WHEN** the relevant CLI, renderer, validation, or test path is exercised
+- **THEN** the expected behavior is observable through local files or deterministic output
+
+
+### Requirement: Scenario fixtures
+Each behavioral scenario SHALL name a role or workflow, inputs, required prompt obligations, forbidden prompt drift, and expected selected context categories.
+
+#### Scenario: A role prompt starts loading all templates
+- **GIVEN** a role prompt starts loading all templates
+- **WHEN** the relevant CLI, renderer, validation, or test path is exercised
+- **THEN** the expected behavior is observable through local files or deterministic output
+
+
+### Requirement: Validation integration
+The repository gate SHALL include a bounded behavioral-evaluation command or validation subcheck that fails on missing contracts for built-in roles/workflows.
+
+#### Scenario: A new workflow is added without a behavioral scenario
+- **GIVEN** a new workflow is added without a behavioral scenario
+- **WHEN** the relevant CLI, renderer, validation, or test path is exercised
+- **THEN** the expected behavior is observable through local files or deterministic output
+
diff --git a/openspec/changes/catch-up-behavioral-evaluation/tasks.md b/openspec/changes/catch-up-behavioral-evaluation/tasks.md
new file mode 100644
index 0000000..49f66e2
--- /dev/null
+++ b/openspec/changes/catch-up-behavioral-evaluation/tasks.md
@@ -0,0 +1,29 @@
+# Behavioral Evaluation Catch-Up Tasks
+
+## Implementation Checklist
+- [x] Read `AGENTS.md` and `docs/architecture/product-boundary.md`; confirm the plan still stays inside the product boundary.
+- [x] Add or update the smallest focused tests for the first behavior slice.
+- [x] Run the focused failing test and confirm it fails for the expected reason.
+- [x] Implement the minimal registry/renderer/asset change for that slice.
+- [x] Re-run the focused test and confirm it passes.
+- [x] Repeat the TDD loop for each remaining slice in this plan.
+- [x] Define an evaluation fixture format for role/workflow scenarios with expected prompt obligations and forbidden drift.
+- [x] Add static behavior checks for required sections, relevant templates, selected context, forbidden future-only surfaces, and output contract coverage.
+- [x] Add representative scenarios for core workflows and new catch-up roles.
+- [x] Expose evaluation through npm scripts or validation subchecks only if it stays local and deterministic.
+- [x] Document how to add a scenario when a role/workflow is added.
+- [x] Update generated-surface/package validation expectations where assets or commands change.
+- [x] Run `git diff --check`.
+- [x] Run focused tests for touched areas.
+- [x] Run `npm run validate` before any parity or readiness claim.
+- [x] If functional behavior changed, update routed Truthmark docs and run `npx truthmark check --json` and `npx truthmark index --json`.
+
+## Suggested Focused Commands
+- `npm test -- --run tests/roles.test.ts tests/codex-prompts.test.ts tests/functionality-gap-pass.test.ts`
+- `npm test -- --run tests/project-workflow.test.ts tests/validation.test.ts`
+- `npm run validate`
+
+## Acceptance Criteria
+- OpenSpec validation for this change passes.
+- The new or changed OGS surfaces are locally reviewable and package-aware.
+- No explicit deferred/future-only feature becomes a user-facing command or required behavior.
diff --git a/openspec/changes/catch-up-customization-ergonomics/.openspec.yaml b/openspec/changes/catch-up-customization-ergonomics/.openspec.yaml
new file mode 100644
index 0000000..3ac681e
--- /dev/null
+++ b/openspec/changes/catch-up-customization-ergonomics/.openspec.yaml
@@ -0,0 +1,2 @@
+schema: spec-driven
+created: 2026-06-17
diff --git a/openspec/changes/catch-up-customization-ergonomics/README.md b/openspec/changes/catch-up-customization-ergonomics/README.md
new file mode 100644
index 0000000..5a9602c
--- /dev/null
+++ b/openspec/changes/catch-up-customization-ergonomics/README.md
@@ -0,0 +1,3 @@
+# catch-up-customization-ergonomics
+
+Plan Open Game Studio improvements for catch-up-customization-ergonomics relative to CCGS within the Codex-native product boundary
diff --git a/openspec/changes/catch-up-customization-ergonomics/design.md b/openspec/changes/catch-up-customization-ergonomics/design.md
new file mode 100644
index 0000000..264b6b6
--- /dev/null
+++ b/openspec/changes/catch-up-customization-ergonomics/design.md
@@ -0,0 +1,35 @@
+# Customization Ergonomics Catch-Up Design
+
+## Architecture
+Add project-local customization packs for roles, workflows, templates, and studio policy that are schema-validated, visible in the repo, and safely merged with built-ins without becoming a general plugin/orchestrator platform. The implementation should extend the existing TypeScript registries and renderers instead of introducing a separate orchestration platform. Built-in depth belongs in package-shipped registries/assets; project-specific depth belongs in explicit reviewable local files.
+
+## Current Gap Evidence
+CCGS users can edit `.claude/agents`, `.claude/skills`, `.claude/rules`, and hooks directly. OGS is cleaner as a package but less no-code/custom-pack friendly because built-ins live primarily in TypeScript registries.
+
+## Key Decisions
+1. Preserve Open Game Studio's local-first, Codex-native runtime.
+2. Make added depth discoverable and validated, but do not force it into every prompt.
+3. Select context by role/workflow/task relevance; never load all roles, all workflows, all templates, or all engine references for one run.
+4. Keep implementation tasks test-first and package-smoke verified where package assets change.
+
+## Data And Surface Contracts
+- `src/config.ts`
+- `src/roles.ts`
+- `src/workflows.ts`
+- `src/templates.ts`
+- `src/validation.ts`
+- `src/projects.ts`
+- `tests/validation.test.ts`
+- `tests/project-workflow.test.ts`
+- `docs/setup.md`
+- `docs/examples.md`
+
+## Alternatives Rejected
+- Directly copying CCGS `.claude/**` files into generated projects: rejected because OGS is Codex-native and uses `AGENTS.md` / `.codex/**`.
+- Adding a general agent orchestrator or background controller: rejected by product boundary.
+- Adding broad prompt bundles that include every reference file: rejected because depth must come from selected context.
+
+## Risks And Mitigations
+- Prompt bloat: add renderer tests and selected-context assertions.
+- Registry drift: update validation to fail when a registry entry lacks materialized/generated/package coverage.
+- Product-boundary drift: keep future-only/deferred surfaces absent and add negative tests when relevant.
diff --git a/openspec/changes/catch-up-customization-ergonomics/proposal.md b/openspec/changes/catch-up-customization-ergonomics/proposal.md
new file mode 100644
index 0000000..b28b390
--- /dev/null
+++ b/openspec/changes/catch-up-customization-ergonomics/proposal.md
@@ -0,0 +1,30 @@
+# Customization Ergonomics Catch-Up Proposal
+
+## Why
+CCGS users can edit `.claude/agents`, `.claude/skills`, `.claude/rules`, and hooks directly. OGS is cleaner as a package but less no-code/custom-pack friendly because built-ins live primarily in TypeScript registries.
+
+Current comparison baseline:
+- Open Game Studio: 20 roles, 13 workflow prompt shortcuts, 13 templates, 12 engine-reference files, TypeScript CLI/package, Codex-native run path, validation gate.
+- Claude Code Game Studios: 49 agents, 73 skills, 40 templates, 46 engine-reference files, richer authored specialist prompts and skill/testing framework.
+- Explicitly ignored/deferred for Open Game Studio: telemetry, planner/next, parallel orchestration, hard output-ownership enforcement, hosted service/daemon/background controller, hidden memory/checkpoints, non-Codex runtime replacements, mandatory heavyweight lifecycle.
+
+
+## What Changes
+- Design `opengamestudio.config.json` or `.codex/studio/config.json` extension points for project-local role/workflow/template packs.
+- Define schema rules for custom role ids, workflow ids, template metadata, path containment, override/extend behavior, and conflict diagnostics.
+- Update init/validate/status/templates list/run prompt paths to load validated local packs.
+- Add tests for valid custom packs, duplicate ids, unsafe paths, missing template files, and built-in override policy.
+- Document examples that edit local pack files instead of editing package source.
+
+## Product Boundary Check
+- Improves: Add project-local customization packs for roles, workflows, templates, and studio policy that are schema-validated, visible in the repo, and safely merged with built-ins without becoming a general plugin/orchestrator platform.
+- In-scope surfaces: src/config.ts, src/roles.ts, src/workflows.ts, src/templates.ts, src/validation.ts, src/projects.ts, tests/validation.test.ts, tests/project-workflow.test.ts, docs/setup.md, docs/examples.md
+- Lightweight prototype use: preserved; new depth is opt-in and selected by role/workflow relevance.
+- Codex-native contract: preserved; built around `AGENTS.md`, `.codex/**`, npm package assets, and `opengamestudio` commands.
+- Reviewable evidence: source files, generated project files, tests, validation output, and OpenSpec artifacts.
+- Explicit non-goals: no telemetry, planner/next, parallel orchestration, hosted daemon, hidden memory, non-Codex runtime replacement, or mandatory heavyweight lifecycle.
+
+## Impact
+- Source: src/config.ts, src/roles.ts, src/workflows.ts, src/templates.ts, src/validation.ts, src/projects.ts, tests/validation.test.ts, tests/project-workflow.test.ts, docs/setup.md, docs/examples.md
+- Tests: focused Vitest suites plus `npm run validate`.
+- Docs/truth: update routed Truthmark engineering/product docs only when implementation changes behavior; this proposal itself is planning-only.
diff --git a/openspec/changes/catch-up-customization-ergonomics/specs/codex-studio-customization-ergonomics/spec.md b/openspec/changes/catch-up-customization-ergonomics/specs/codex-studio-customization-ergonomics/spec.md
new file mode 100644
index 0000000..1dabf2e
--- /dev/null
+++ b/openspec/changes/catch-up-customization-ergonomics/specs/codex-studio-customization-ergonomics/spec.md
@@ -0,0 +1,30 @@
+# Customization Ergonomics Catch-Up Specification
+
+## ADDED Requirements
+
+### Requirement: Project-local packs
+OGS SHALL support project-local role, workflow, and template pack metadata stored in reviewable repository files.
+
+#### Scenario: A project defines a custom role pack with a safe prompt file
+- **GIVEN** a project defines a custom role pack with a safe prompt file
+- **WHEN** the relevant CLI, renderer, validation, or test path is exercised
+- **THEN** the expected behavior is observable through local files or deterministic output
+
+
+### Requirement: Safe merge semantics
+Custom packs SHALL be schema-validated, path-contained, and merged with built-ins using explicit conflict diagnostics.
+
+#### Scenario: A custom template points outside the project root
+- **GIVEN** a custom template points outside the project root
+- **WHEN** the relevant CLI, renderer, validation, or test path is exercised
+- **THEN** the expected behavior is observable through local files or deterministic output
+
+
+### Requirement: No plugin-platform drift
+Customization SHALL NOT introduce hosted plugins, arbitrary code execution, background hooks, or non-Codex runtime replacement behavior.
+
+#### Scenario: A custom role duplicates a built-in id without explicit override policy
+- **GIVEN** a custom role duplicates a built-in id without explicit override policy
+- **WHEN** the relevant CLI, renderer, validation, or test path is exercised
+- **THEN** the expected behavior is observable through local files or deterministic output
+
diff --git a/openspec/changes/catch-up-customization-ergonomics/tasks.md b/openspec/changes/catch-up-customization-ergonomics/tasks.md
new file mode 100644
index 0000000..3863fe5
--- /dev/null
+++ b/openspec/changes/catch-up-customization-ergonomics/tasks.md
@@ -0,0 +1,29 @@
+# Customization Ergonomics Catch-Up Tasks
+
+## Implementation Checklist
+- [x] Read `AGENTS.md` and `docs/architecture/product-boundary.md`; confirm the plan still stays inside the product boundary.
+- [x] Add or update the smallest focused tests for the first behavior slice.
+- [x] Run the focused failing test and confirm it fails for the expected reason.
+- [x] Implement the minimal registry/renderer/asset change for that slice.
+- [x] Re-run the focused test and confirm it passes.
+- [x] Repeat the TDD loop for each remaining slice in this plan.
+- [x] Design `opengamestudio.config.json` or `.codex/studio/config.json` extension points for project-local role/workflow/template packs.
+- [x] Define schema rules for custom role ids, workflow ids, template metadata, path containment, override/extend behavior, and conflict diagnostics.
+- [x] Update init/validate/status/templates list/run prompt paths to load validated local packs.
+- [x] Add tests for valid custom packs, duplicate ids, unsafe paths, missing template files, and built-in override policy.
+- [x] Document examples that edit local pack files instead of editing package source.
+- [x] Update generated-surface/package validation expectations where assets or commands change.
+- [x] Run `git diff --check`.
+- [x] Run focused tests for touched areas.
+- [x] Run `npm run validate` before any parity or readiness claim.
+- [x] If functional behavior changed, update routed Truthmark docs and run `npx truthmark check --json` and `npx truthmark index --json`.
+
+## Suggested Focused Commands
+- `npm test -- --run tests/roles.test.ts tests/codex-prompts.test.ts tests/functionality-gap-pass.test.ts`
+- `npm test -- --run tests/project-workflow.test.ts tests/validation.test.ts`
+- `npm run validate`
+
+## Acceptance Criteria
+- OpenSpec validation for this change passes.
+- The new or changed OGS surfaces are locally reviewable and package-aware.
+- No explicit deferred/future-only feature becomes a user-facing command or required behavior.
diff --git a/openspec/changes/catch-up-domain-role-coverage/.openspec.yaml b/openspec/changes/catch-up-domain-role-coverage/.openspec.yaml
new file mode 100644
index 0000000..3ac681e
--- /dev/null
+++ b/openspec/changes/catch-up-domain-role-coverage/.openspec.yaml
@@ -0,0 +1,2 @@
+schema: spec-driven
+created: 2026-06-17
diff --git a/openspec/changes/catch-up-domain-role-coverage/README.md b/openspec/changes/catch-up-domain-role-coverage/README.md
new file mode 100644
index 0000000..486aace
--- /dev/null
+++ b/openspec/changes/catch-up-domain-role-coverage/README.md
@@ -0,0 +1,3 @@
+# catch-up-domain-role-coverage
+
+Plan Open Game Studio improvements for catch-up-domain-role-coverage relative to CCGS within the Codex-native product boundary
diff --git a/openspec/changes/catch-up-domain-role-coverage/design.md b/openspec/changes/catch-up-domain-role-coverage/design.md
new file mode 100644
index 0000000..933b498
--- /dev/null
+++ b/openspec/changes/catch-up-domain-role-coverage/design.md
@@ -0,0 +1,33 @@
+# Domain Role Coverage Catch-Up Design
+
+## Architecture
+Expand Open Game Studio role coverage across game-development specialties while preserving bounded Codex prompts and the AGENTS.md/.codex generated-surface contract. The implementation should extend the existing TypeScript registries and renderers instead of introducing a separate orchestration platform. Built-in depth belongs in package-shipped registries/assets; project-specific depth belongs in explicit reviewable local files.
+
+## Current Gap Evidence
+Open Game Studio has 20 roles while CCGS has 49 agents. The missing value is not raw count; it is specialist coverage for production domains that a game developer reasonably expects.
+
+## Key Decisions
+1. Preserve Open Game Studio's local-first, Codex-native runtime.
+2. Make added depth discoverable and validated, but do not force it into every prompt.
+3. Select context by role/workflow/task relevance; never load all roles, all workflows, all templates, or all engine references for one run.
+4. Keep implementation tasks test-first and package-smoke verified where package assets change.
+
+## Data And Surface Contracts
+- `src/roles.ts`
+- `src/codex-prompts.ts`
+- `src/projects.ts`
+- `src/validation.ts`
+- `tests/roles.test.ts`
+- `tests/codex-prompts.test.ts`
+- `tests/functionality-gap-pass.test.ts`
+- `docs/truthmark/engineering/codex/roles-and-workflows.md`
+
+## Alternatives Rejected
+- Directly copying CCGS `.claude/**` files into generated projects: rejected because OGS is Codex-native and uses `AGENTS.md` / `.codex/**`.
+- Adding a general agent orchestrator or background controller: rejected by product boundary.
+- Adding broad prompt bundles that include every reference file: rejected because depth must come from selected context.
+
+## Risks And Mitigations
+- Prompt bloat: add renderer tests and selected-context assertions.
+- Registry drift: update validation to fail when a registry entry lacks materialized/generated/package coverage.
+- Product-boundary drift: keep future-only/deferred surfaces absent and add negative tests when relevant.
diff --git a/openspec/changes/catch-up-domain-role-coverage/proposal.md b/openspec/changes/catch-up-domain-role-coverage/proposal.md
new file mode 100644
index 0000000..f194ec0
--- /dev/null
+++ b/openspec/changes/catch-up-domain-role-coverage/proposal.md
@@ -0,0 +1,29 @@
+# Domain Role Coverage Catch-Up Proposal
+
+## Why
+Open Game Studio has 20 roles while CCGS has 49 agents. The missing value is not raw count; it is specialist coverage for production domains that a game developer reasonably expects.
+
+Current comparison baseline:
+- Open Game Studio: 20 roles, 13 workflow prompt shortcuts, 13 templates, 12 engine-reference files, TypeScript CLI/package, Codex-native run path, validation gate.
+- Claude Code Game Studios: 49 agents, 73 skills, 40 templates, 46 engine-reference files, richer authored specialist prompts and skill/testing framework.
+- Explicitly ignored/deferred for Open Game Studio: telemetry, planner/next, parallel orchestration, hard output-ownership enforcement, hosted service/daemon/background controller, hidden memory/checkpoints, non-Codex runtime replacements, mandatory heavyweight lifecycle.
+
+
+## What Changes
+- Add domain clusters for audio, level/world/content, systems/economy, live ops/community/localization/accessibility, security/devops/performance/network/AI/UI programming.
+- Add only roles with clear game-studio outputs and selected context strategies; do not add a role just to mirror a CCGS name.
+- Update role package rendering and generated project prompt materialization for every new role.
+- Add validation coverage that all role packages render and no single role run loads all roles.
+
+## Product Boundary Check
+- Improves: Expand Open Game Studio role coverage across game-development specialties while preserving bounded Codex prompts and the AGENTS.md/.codex generated-surface contract.
+- In-scope surfaces: src/roles.ts, src/codex-prompts.ts, src/projects.ts, src/validation.ts, tests/roles.test.ts, tests/codex-prompts.test.ts, tests/functionality-gap-pass.test.ts, docs/truthmark/engineering/codex/roles-and-workflows.md
+- Lightweight prototype use: preserved; new depth is opt-in and selected by role/workflow relevance.
+- Codex-native contract: preserved; built around `AGENTS.md`, `.codex/**`, npm package assets, and `opengamestudio` commands.
+- Reviewable evidence: source files, generated project files, tests, validation output, and OpenSpec artifacts.
+- Explicit non-goals: no telemetry, planner/next, parallel orchestration, hosted daemon, hidden memory, non-Codex runtime replacement, or mandatory heavyweight lifecycle.
+
+## Impact
+- Source: src/roles.ts, src/codex-prompts.ts, src/projects.ts, src/validation.ts, tests/roles.test.ts, tests/codex-prompts.test.ts, tests/functionality-gap-pass.test.ts, docs/truthmark/engineering/codex/roles-and-workflows.md
+- Tests: focused Vitest suites plus `npm run validate`.
+- Docs/truth: update routed Truthmark engineering/product docs only when implementation changes behavior; this proposal itself is planning-only.
diff --git a/openspec/changes/catch-up-domain-role-coverage/specs/codex-studio-domain-role-coverage/spec.md b/openspec/changes/catch-up-domain-role-coverage/specs/codex-studio-domain-role-coverage/spec.md
new file mode 100644
index 0000000..3f8cd39
--- /dev/null
+++ b/openspec/changes/catch-up-domain-role-coverage/specs/codex-studio-domain-role-coverage/spec.md
@@ -0,0 +1,30 @@
+# Domain Role Coverage Catch-Up Specification
+
+## ADDED Requirements
+
+### Requirement: Specialist role clusters
+The role registry SHALL expose specialist roles in bounded domain clusters that cover CCGS-derived gaps without requiring prompt-time loading of unrelated roles.
+
+#### Scenario: A project initialized by the cli
+- **GIVEN** a project initialized by the CLI
+- **WHEN** the relevant CLI, renderer, validation, or test path is exercised
+- **THEN** the expected behavior is observable through local files or deterministic output
+
+
+### Requirement: Role package renderability
+Every built-in role SHALL render a package with system prompt, expected outputs, context strategy, and review checklist.
+
+#### Scenario: A user runs a single specialist role
+- **GIVEN** a user runs a single specialist role
+- **WHEN** the relevant CLI, renderer, validation, or test path is exercised
+- **THEN** the expected behavior is observable through local files or deterministic output
+
+
+### Requirement: Generated project freshness
+Project initialization SHALL materialize prompt files for all built-in roles and validation SHALL fail when generated role surfaces are stale.
+
+#### Scenario: A role is added to the registry
+- **GIVEN** a role is added to the registry
+- **WHEN** the relevant CLI, renderer, validation, or test path is exercised
+- **THEN** the expected behavior is observable through local files or deterministic output
+
diff --git a/openspec/changes/catch-up-domain-role-coverage/tasks.md b/openspec/changes/catch-up-domain-role-coverage/tasks.md
new file mode 100644
index 0000000..df94e30
--- /dev/null
+++ b/openspec/changes/catch-up-domain-role-coverage/tasks.md
@@ -0,0 +1,28 @@
+# Domain Role Coverage Catch-Up Tasks
+
+## Implementation Checklist
+- [x] Read `AGENTS.md` and `docs/architecture/product-boundary.md`; confirm the plan still stays inside the product boundary.
+- [x] Add or update the smallest focused tests for the first behavior slice.
+- [x] Run the focused failing test and confirm it fails for the expected reason.
+- [x] Implement the minimal registry/renderer/asset change for that slice.
+- [x] Re-run the focused test and confirm it passes.
+- [x] Repeat the TDD loop for each remaining slice in this plan.
+- [x] Add domain clusters for audio, level/world/content, systems/economy, live ops/community/localization/accessibility, security/devops/performance/network/AI/UI programming.
+- [x] Add only roles with clear game-studio outputs and selected context strategies; do not add a role just to mirror a CCGS name.
+- [x] Update role package rendering and generated project prompt materialization for every new role.
+- [x] Add validation coverage that all role packages render and no single role run loads all roles.
+- [x] Update generated-surface/package validation expectations where assets or commands change.
+- [x] Run `git diff --check`.
+- [x] Run focused tests for touched areas.
+- [x] Run `npm run validate` before any parity or readiness claim.
+- [x] If functional behavior changed, update routed Truthmark docs and run `npx truthmark check --json` and `npx truthmark index --json`.
+
+## Suggested Focused Commands
+- `npm test -- --run tests/roles.test.ts tests/codex-prompts.test.ts tests/functionality-gap-pass.test.ts`
+- `npm test -- --run tests/project-workflow.test.ts tests/validation.test.ts`
+- `npm run validate`
+
+## Acceptance Criteria
+- OpenSpec validation for this change passes.
+- The new or changed OGS surfaces are locally reviewable and package-aware.
+- No explicit deferred/future-only feature becomes a user-facing command or required behavior.
diff --git a/openspec/changes/catch-up-engine-reference-depth/.openspec.yaml b/openspec/changes/catch-up-engine-reference-depth/.openspec.yaml
new file mode 100644
index 0000000..3ac681e
--- /dev/null
+++ b/openspec/changes/catch-up-engine-reference-depth/.openspec.yaml
@@ -0,0 +1,2 @@
+schema: spec-driven
+created: 2026-06-17
diff --git a/openspec/changes/catch-up-engine-reference-depth/README.md b/openspec/changes/catch-up-engine-reference-depth/README.md
new file mode 100644
index 0000000..1fcdfd8
--- /dev/null
+++ b/openspec/changes/catch-up-engine-reference-depth/README.md
@@ -0,0 +1,3 @@
+# catch-up-engine-reference-depth
+
+Plan Open Game Studio improvements for catch-up-engine-reference-depth relative to CCGS within the Codex-native product boundary
diff --git a/openspec/changes/catch-up-engine-reference-depth/design.md b/openspec/changes/catch-up-engine-reference-depth/design.md
new file mode 100644
index 0000000..5917d2c
--- /dev/null
+++ b/openspec/changes/catch-up-engine-reference-depth/design.md
@@ -0,0 +1,33 @@
+# Engine Reference Depth Catch-Up Design
+
+## Architecture
+Deepen packaged engine references for Godot, Unity, and Unreal with module-level and plugin-level files that can be selected by relevance without bloating every prompt. The implementation should extend the existing TypeScript registries and renderers instead of introducing a separate orchestration platform. Built-in depth belongs in package-shipped registries/assets; project-specific depth belongs in explicit reviewable local files.
+
+## Current Gap Evidence
+Open Game Studio ships 12 compact engine-reference files while CCGS ships roughly 46 files with modules, plugins, deprecated APIs, breaking changes, and best-practice guidance for Godot, Unity, and Unreal.
+
+## Key Decisions
+1. Preserve Open Game Studio's local-first, Codex-native runtime.
+2. Make added depth discoverable and validated, but do not force it into every prompt.
+3. Select context by role/workflow/task relevance; never load all roles, all workflows, all templates, or all engine references for one run.
+4. Keep implementation tasks test-first and package-smoke verified where package assets change.
+
+## Data And Surface Contracts
+- `engine_reference/`
+- `src/engine-reference.ts`
+- `src/engines.ts`
+- `src/prompt-context.ts`
+- `src/validation.ts`
+- `tests/engine-system.test.ts`
+- `tests/codex-context-files.test.ts`
+- `docs/truthmark/engineering/codex/runtime-and-tasks.md`
+
+## Alternatives Rejected
+- Directly copying CCGS `.claude/**` files into generated projects: rejected because OGS is Codex-native and uses `AGENTS.md` / `.codex/**`.
+- Adding a general agent orchestrator or background controller: rejected by product boundary.
+- Adding broad prompt bundles that include every reference file: rejected because depth must come from selected context.
+
+## Risks And Mitigations
+- Prompt bloat: add renderer tests and selected-context assertions.
+- Registry drift: update validation to fail when a registry entry lacks materialized/generated/package coverage.
+- Product-boundary drift: keep future-only/deferred surfaces absent and add negative tests when relevant.
diff --git a/openspec/changes/catch-up-engine-reference-depth/proposal.md b/openspec/changes/catch-up-engine-reference-depth/proposal.md
new file mode 100644
index 0000000..56618f0
--- /dev/null
+++ b/openspec/changes/catch-up-engine-reference-depth/proposal.md
@@ -0,0 +1,30 @@
+# Engine Reference Depth Catch-Up Proposal
+
+## Why
+Open Game Studio ships 12 compact engine-reference files while CCGS ships roughly 46 files with modules, plugins, deprecated APIs, breaking changes, and best-practice guidance for Godot, Unity, and Unreal.
+
+Current comparison baseline:
+- Open Game Studio: 20 roles, 13 workflow prompt shortcuts, 13 templates, 12 engine-reference files, TypeScript CLI/package, Codex-native run path, validation gate.
+- Claude Code Game Studios: 49 agents, 73 skills, 40 templates, 46 engine-reference files, richer authored specialist prompts and skill/testing framework.
+- Explicitly ignored/deferred for Open Game Studio: telemetry, planner/next, parallel orchestration, hard output-ownership enforcement, hosted service/daemon/background controller, hidden memory/checkpoints, non-Codex runtime replacements, mandatory heavyweight lifecycle.
+
+
+## What Changes
+- Add per-engine `current-best-practices.md`, `deprecated-apis.md`, `breaking-changes.md`, and module files for animation, audio, input, navigation, networking, physics, rendering, UI.
+- Add plugin references for Unity Addressables/Cinemachine/DOTS and Unreal GAS/Common UI/PCG where in-scope.
+- Add reference metadata: engine, version reviewed, source/review date, tags, applicable roles/workflows.
+- Update context selection so engine-specialist prompts select only relevant module/plugin references.
+- Validate package shipping and temp-cwd installed-bin access.
+
+## Product Boundary Check
+- Improves: Deepen packaged engine references for Godot, Unity, and Unreal with module-level and plugin-level files that can be selected by relevance without bloating every prompt.
+- In-scope surfaces: engine_reference/, src/engine-reference.ts, src/engines.ts, src/prompt-context.ts, src/validation.ts, tests/engine-system.test.ts, tests/codex-context-files.test.ts, docs/truthmark/engineering/codex/runtime-and-tasks.md
+- Lightweight prototype use: preserved; new depth is opt-in and selected by role/workflow relevance.
+- Codex-native contract: preserved; built around `AGENTS.md`, `.codex/**`, npm package assets, and `opengamestudio` commands.
+- Reviewable evidence: source files, generated project files, tests, validation output, and OpenSpec artifacts.
+- Explicit non-goals: no telemetry, planner/next, parallel orchestration, hosted daemon, hidden memory, non-Codex runtime replacement, or mandatory heavyweight lifecycle.
+
+## Impact
+- Source: engine_reference/, src/engine-reference.ts, src/engines.ts, src/prompt-context.ts, src/validation.ts, tests/engine-system.test.ts, tests/codex-context-files.test.ts, docs/truthmark/engineering/codex/runtime-and-tasks.md
+- Tests: focused Vitest suites plus `npm run validate`.
+- Docs/truth: update routed Truthmark engineering/product docs only when implementation changes behavior; this proposal itself is planning-only.
diff --git a/openspec/changes/catch-up-engine-reference-depth/specs/codex-studio-engine-reference-depth/spec.md b/openspec/changes/catch-up-engine-reference-depth/specs/codex-studio-engine-reference-depth/spec.md
new file mode 100644
index 0000000..07bd28a
--- /dev/null
+++ b/openspec/changes/catch-up-engine-reference-depth/specs/codex-studio-engine-reference-depth/spec.md
@@ -0,0 +1,30 @@
+# Engine Reference Depth Catch-Up Specification
+
+## ADDED Requirements
+
+### Requirement: Engine reference taxonomy
+Each supported engine SHALL have version, best-practice, deprecated API, breaking-change, module, and plugin reference categories.
+
+#### Scenario: A godot networking task is rendered
+- **GIVEN** a Godot networking task is rendered
+- **WHEN** the relevant CLI, renderer, validation, or test path is exercised
+- **THEN** the expected behavior is observable through local files or deterministic output
+
+
+### Requirement: Reference metadata
+Every engine-reference file SHALL include review metadata sufficient for validation and future refresh work.
+
+#### Scenario: A new engine reference lacks metadata
+- **GIVEN** a new engine reference lacks metadata
+- **WHEN** the relevant CLI, renderer, validation, or test path is exercised
+- **THEN** the expected behavior is observable through local files or deterministic output
+
+
+### Requirement: Selected-context loading
+Role and workflow prompts SHALL select engine-reference files by engine and task relevance instead of loading all engine references.
+
+#### Scenario: Package smoke validation runs
+- **GIVEN** package smoke validation runs
+- **WHEN** the relevant CLI, renderer, validation, or test path is exercised
+- **THEN** the expected behavior is observable through local files or deterministic output
+
diff --git a/openspec/changes/catch-up-engine-reference-depth/tasks.md b/openspec/changes/catch-up-engine-reference-depth/tasks.md
new file mode 100644
index 0000000..2c3a1a4
--- /dev/null
+++ b/openspec/changes/catch-up-engine-reference-depth/tasks.md
@@ -0,0 +1,29 @@
+# Engine Reference Depth Catch-Up Tasks
+
+## Implementation Checklist
+- [x] Read `AGENTS.md` and `docs/architecture/product-boundary.md`; confirm the plan still stays inside the product boundary.
+- [x] Add or update the smallest focused tests for the first behavior slice.
+- [x] Run the focused failing test and confirm it fails for the expected reason.
+- [x] Implement the minimal registry/renderer/asset change for that slice.
+- [x] Re-run the focused test and confirm it passes.
+- [x] Repeat the TDD loop for each remaining slice in this plan.
+- [x] Add per-engine `current-best-practices.md`, `deprecated-apis.md`, `breaking-changes.md`, and module files for animation, audio, input, navigation, networking, physics, rendering, UI.
+- [x] Add plugin references for Unity Addressables/Cinemachine/DOTS and Unreal GAS/Common UI/PCG where in-scope.
+- [x] Add reference metadata: engine, version reviewed, source/review date, tags, applicable roles/workflows.
+- [x] Update context selection so engine-specialist prompts select only relevant module/plugin references.
+- [x] Validate package shipping and temp-cwd installed-bin access.
+- [x] Update generated-surface/package validation expectations where assets or commands change.
+- [x] Run `git diff --check`.
+- [x] Run focused tests for touched areas.
+- [x] Run `npm run validate` before any parity or readiness claim.
+- [x] If functional behavior changed, update routed Truthmark docs and run `npx truthmark check --json` and `npx truthmark index --json`.
+
+## Suggested Focused Commands
+- `npm test -- --run tests/roles.test.ts tests/codex-prompts.test.ts tests/functionality-gap-pass.test.ts`
+- `npm test -- --run tests/project-workflow.test.ts tests/validation.test.ts`
+- `npm run validate`
+
+## Acceptance Criteria
+- OpenSpec validation for this change passes.
+- The new or changed OGS surfaces are locally reviewable and package-aware.
+- No explicit deferred/future-only feature becomes a user-facing command or required behavior.
diff --git a/openspec/changes/catch-up-production-templates/.openspec.yaml b/openspec/changes/catch-up-production-templates/.openspec.yaml
new file mode 100644
index 0000000..3ac681e
--- /dev/null
+++ b/openspec/changes/catch-up-production-templates/.openspec.yaml
@@ -0,0 +1,2 @@
+schema: spec-driven
+created: 2026-06-17
diff --git a/openspec/changes/catch-up-production-templates/README.md b/openspec/changes/catch-up-production-templates/README.md
new file mode 100644
index 0000000..edd5ee4
--- /dev/null
+++ b/openspec/changes/catch-up-production-templates/README.md
@@ -0,0 +1,3 @@
+# catch-up-production-templates
+
+Plan Open Game Studio improvements for catch-up-production-templates relative to CCGS within the Codex-native product boundary
diff --git a/openspec/changes/catch-up-production-templates/design.md b/openspec/changes/catch-up-production-templates/design.md
new file mode 100644
index 0000000..398db14
--- /dev/null
+++ b/openspec/changes/catch-up-production-templates/design.md
@@ -0,0 +1,33 @@
+# Production Template Depth Catch-Up Design
+
+## Architecture
+Add a richer built-in template pack for game production artifacts while keeping templates package-shipped, listed, selected by workflow relevance, and validated through npm pack smoke tests. The implementation should extend the existing TypeScript registries and renderers instead of introducing a separate orchestration platform. Built-in depth belongs in package-shipped registries/assets; project-specific depth belongs in explicit reviewable local files.
+
+## Current Gap Evidence
+Open Game Studio has 13 templates while CCGS has roughly 40 production templates spanning design, architecture, QA, release, UX, audio, art, risk, and postmortem artifacts.
+
+## Key Decisions
+1. Preserve Open Game Studio's local-first, Codex-native runtime.
+2. Make added depth discoverable and validated, but do not force it into every prompt.
+3. Select context by role/workflow/task relevance; never load all roles, all workflows, all templates, or all engine references for one run.
+4. Keep implementation tasks test-first and package-smoke verified where package assets change.
+
+## Data And Surface Contracts
+- `templates/`
+- `src/templates.ts`
+- `src/prompt-context.ts`
+- `src/validation.ts`
+- `tests/agents-templates.test.ts`
+- `tests/functionality-gap-pass.test.ts`
+- `tests/validation.test.ts`
+- `package.json`
+
+## Alternatives Rejected
+- Directly copying CCGS `.claude/**` files into generated projects: rejected because OGS is Codex-native and uses `AGENTS.md` / `.codex/**`.
+- Adding a general agent orchestrator or background controller: rejected by product boundary.
+- Adding broad prompt bundles that include every reference file: rejected because depth must come from selected context.
+
+## Risks And Mitigations
+- Prompt bloat: add renderer tests and selected-context assertions.
+- Registry drift: update validation to fail when a registry entry lacks materialized/generated/package coverage.
+- Product-boundary drift: keep future-only/deferred surfaces absent and add negative tests when relevant.
diff --git a/openspec/changes/catch-up-production-templates/proposal.md b/openspec/changes/catch-up-production-templates/proposal.md
new file mode 100644
index 0000000..1931a86
--- /dev/null
+++ b/openspec/changes/catch-up-production-templates/proposal.md
@@ -0,0 +1,29 @@
+# Production Template Depth Catch-Up Proposal
+
+## Why
+Open Game Studio has 13 templates while CCGS has roughly 40 production templates spanning design, architecture, QA, release, UX, audio, art, risk, and postmortem artifacts.
+
+Current comparison baseline:
+- Open Game Studio: 20 roles, 13 workflow prompt shortcuts, 13 templates, 12 engine-reference files, TypeScript CLI/package, Codex-native run path, validation gate.
+- Claude Code Game Studios: 49 agents, 73 skills, 40 templates, 46 engine-reference files, richer authored specialist prompts and skill/testing framework.
+- Explicitly ignored/deferred for Open Game Studio: telemetry, planner/next, parallel orchestration, hard output-ownership enforcement, hosted service/daemon/background controller, hidden memory/checkpoints, non-Codex runtime replacements, mandatory heavyweight lifecycle.
+
+
+## What Changes
+- Add production templates for ADR, technical design, architecture traceability, art bible, sound bible, UX spec, accessibility requirements, test plan, test evidence, sprint plan, vertical-slice report, release notes, postmortem, risk register, economy model, difficulty curve, player journey, pitch document.
+- Represent each template in the template registry with category, path, short description, and relevant workflow/role hints.
+- Update package files and pack/install smoke checks so installed CLI can load the new templates from a temp cwd.
+- Add relevance-selection tests that a workflow includes only its mapped templates, not the whole pack.
+
+## Product Boundary Check
+- Improves: Add a richer built-in template pack for game production artifacts while keeping templates package-shipped, listed, selected by workflow relevance, and validated through npm pack smoke tests.
+- In-scope surfaces: templates/, src/templates.ts, src/prompt-context.ts, src/validation.ts, tests/agents-templates.test.ts, tests/functionality-gap-pass.test.ts, tests/validation.test.ts, package.json
+- Lightweight prototype use: preserved; new depth is opt-in and selected by role/workflow relevance.
+- Codex-native contract: preserved; built around `AGENTS.md`, `.codex/**`, npm package assets, and `opengamestudio` commands.
+- Reviewable evidence: source files, generated project files, tests, validation output, and OpenSpec artifacts.
+- Explicit non-goals: no telemetry, planner/next, parallel orchestration, hosted daemon, hidden memory, non-Codex runtime replacement, or mandatory heavyweight lifecycle.
+
+## Impact
+- Source: templates/, src/templates.ts, src/prompt-context.ts, src/validation.ts, tests/agents-templates.test.ts, tests/functionality-gap-pass.test.ts, tests/validation.test.ts, package.json
+- Tests: focused Vitest suites plus `npm run validate`.
+- Docs/truth: update routed Truthmark engineering/product docs only when implementation changes behavior; this proposal itself is planning-only.
diff --git a/openspec/changes/catch-up-production-templates/specs/codex-studio-production-template-pack/spec.md b/openspec/changes/catch-up-production-templates/specs/codex-studio-production-template-pack/spec.md
new file mode 100644
index 0000000..d22eb3a
--- /dev/null
+++ b/openspec/changes/catch-up-production-templates/specs/codex-studio-production-template-pack/spec.md
@@ -0,0 +1,30 @@
+# Production Template Depth Catch-Up Specification
+
+## ADDED Requirements
+
+### Requirement: Template registry metadata
+Every built-in template SHALL have id, category, path, description, and selected-use hints for workflows and roles.
+
+#### Scenario: The installed package runs from a temp directory
+- **GIVEN** the installed package runs from a temp directory
+- **WHEN** the relevant CLI, renderer, validation, or test path is exercised
+- **THEN** the expected behavior is observable through local files or deterministic output
+
+
+### Requirement: Package-shipped templates
+All built-in templates SHALL be included in package files and verified by pack/install smoke tests.
+
+#### Scenario: A ui review workflow is rendered
+- **GIVEN** a UI review workflow is rendered
+- **WHEN** the relevant CLI, renderer, validation, or test path is exercised
+- **THEN** the expected behavior is observable through local files or deterministic output
+
+
+### Requirement: Bounded template selection
+Prompt rendering SHALL include only selected templates relevant to the current role or workflow.
+
+#### Scenario: A template file is missing from package files
+- **GIVEN** a template file is missing from package files
+- **WHEN** the relevant CLI, renderer, validation, or test path is exercised
+- **THEN** the expected behavior is observable through local files or deterministic output
+
diff --git a/openspec/changes/catch-up-production-templates/tasks.md b/openspec/changes/catch-up-production-templates/tasks.md
new file mode 100644
index 0000000..7806f6b
--- /dev/null
+++ b/openspec/changes/catch-up-production-templates/tasks.md
@@ -0,0 +1,28 @@
+# Production Template Depth Catch-Up Tasks
+
+## Implementation Checklist
+- [x] Read `AGENTS.md` and `docs/architecture/product-boundary.md`; confirm the plan still stays inside the product boundary.
+- [x] Add or update the smallest focused tests for the first behavior slice.
+- [x] Run the focused failing test and confirm it fails for the expected reason.
+- [x] Implement the minimal registry/renderer/asset change for that slice.
+- [x] Re-run the focused test and confirm it passes.
+- [x] Repeat the TDD loop for each remaining slice in this plan.
+- [x] Add production templates for ADR, technical design, architecture traceability, art bible, sound bible, UX spec, accessibility requirements, test plan, test evidence, sprint plan, vertical-slice report, release notes, postmortem, risk register, economy model, difficulty curve, player journey, pitch document.
+- [x] Represent each template in the template registry with category, path, short description, and relevant workflow/role hints.
+- [x] Update package files and pack/install smoke checks so installed CLI can load the new templates from a temp cwd.
+- [x] Add relevance-selection tests that a workflow includes only its mapped templates, not the whole pack.
+- [x] Update generated-surface/package validation expectations where assets or commands change.
+- [x] Run `git diff --check`.
+- [x] Run focused tests for touched areas.
+- [x] Run `npm run validate` before any parity or readiness claim.
+- [x] If functional behavior changed, update routed Truthmark docs and run `npx truthmark check --json` and `npx truthmark index --json`.
+
+## Suggested Focused Commands
+- `npm test -- --run tests/roles.test.ts tests/codex-prompts.test.ts tests/functionality-gap-pass.test.ts`
+- `npm test -- --run tests/project-workflow.test.ts tests/validation.test.ts`
+- `npm run validate`
+
+## Acceptance Criteria
+- OpenSpec validation for this change passes.
+- The new or changed OGS surfaces are locally reviewable and package-aware.
+- No explicit deferred/future-only feature becomes a user-facing command or required behavior.
diff --git a/openspec/changes/catch-up-role-prompt-depth/.openspec.yaml b/openspec/changes/catch-up-role-prompt-depth/.openspec.yaml
new file mode 100644
index 0000000..3ac681e
--- /dev/null
+++ b/openspec/changes/catch-up-role-prompt-depth/.openspec.yaml
@@ -0,0 +1,2 @@
+schema: spec-driven
+created: 2026-06-17
diff --git a/openspec/changes/catch-up-role-prompt-depth/README.md b/openspec/changes/catch-up-role-prompt-depth/README.md
new file mode 100644
index 0000000..f695085
--- /dev/null
+++ b/openspec/changes/catch-up-role-prompt-depth/README.md
@@ -0,0 +1,3 @@
+# catch-up-role-prompt-depth
+
+Plan Open Game Studio improvements for catch-up-role-prompt-depth relative to CCGS within the Codex-native product boundary
diff --git a/openspec/changes/catch-up-role-prompt-depth/design.md b/openspec/changes/catch-up-role-prompt-depth/design.md
new file mode 100644
index 0000000..29ab0d2
--- /dev/null
+++ b/openspec/changes/catch-up-role-prompt-depth/design.md
@@ -0,0 +1,33 @@
+# Role Prompt Sophistication Catch-Up Design
+
+## Architecture
+Upgrade built-in role packages from compact prompts into richer structured role contracts while preventing prompt bloat and preserving Codex-native single-role execution. The implementation should extend the existing TypeScript registries and renderers instead of introducing a separate orchestration platform. Built-in depth belongs in package-shipped registries/assets; project-specific depth belongs in explicit reviewable local files.
+
+## Current Gap Evidence
+Open Game Studio roles are compact and maintainable, but CCGS agents include richer responsibilities, collaboration protocol, delegation guidance, output formats, domain standards, and quality gates.
+
+## Key Decisions
+1. Preserve Open Game Studio's local-first, Codex-native runtime.
+2. Make added depth discoverable and validated, but do not force it into every prompt.
+3. Select context by role/workflow/task relevance; never load all roles, all workflows, all templates, or all engine references for one run.
+4. Keep implementation tasks test-first and package-smoke verified where package assets change.
+
+## Data And Surface Contracts
+- `src/roles.ts`
+- `src/codex-prompts.ts`
+- `src/agents.ts`
+- `src/generated-surfaces.ts`
+- `tests/codex-prompts.test.ts`
+- `tests/roles.test.ts`
+- `tests/agents-templates.test.ts`
+- `docs/truthmark/engineering/codex/roles-and-workflows.md`
+
+## Alternatives Rejected
+- Directly copying CCGS `.claude/**` files into generated projects: rejected because OGS is Codex-native and uses `AGENTS.md` / `.codex/**`.
+- Adding a general agent orchestrator or background controller: rejected by product boundary.
+- Adding broad prompt bundles that include every reference file: rejected because depth must come from selected context.
+
+## Risks And Mitigations
+- Prompt bloat: add renderer tests and selected-context assertions.
+- Registry drift: update validation to fail when a registry entry lacks materialized/generated/package coverage.
+- Product-boundary drift: keep future-only/deferred surfaces absent and add negative tests when relevant.
diff --git a/openspec/changes/catch-up-role-prompt-depth/proposal.md b/openspec/changes/catch-up-role-prompt-depth/proposal.md
new file mode 100644
index 0000000..2616545
--- /dev/null
+++ b/openspec/changes/catch-up-role-prompt-depth/proposal.md
@@ -0,0 +1,29 @@
+# Role Prompt Sophistication Catch-Up Proposal
+
+## Why
+Open Game Studio roles are compact and maintainable, but CCGS agents include richer responsibilities, collaboration protocol, delegation guidance, output formats, domain standards, and quality gates.
+
+Current comparison baseline:
+- Open Game Studio: 20 roles, 13 workflow prompt shortcuts, 13 templates, 12 engine-reference files, TypeScript CLI/package, Codex-native run path, validation gate.
+- Claude Code Game Studios: 49 agents, 73 skills, 40 templates, 46 engine-reference files, richer authored specialist prompts and skill/testing framework.
+- Explicitly ignored/deferred for Open Game Studio: telemetry, planner/next, parallel orchestration, hard output-ownership enforcement, hosted service/daemon/background controller, hidden memory/checkpoints, non-Codex runtime replacements, mandatory heavyweight lifecycle.
+
+
+## What Changes
+- Extend the role package model with optional structured sections: responsibilities, inputs to inspect, outputs, quality gates, collaboration notes, stop conditions, and handoff format.
+- Move repeated guidance into shared compact fragments rendered only when relevant.
+- Add role-specific output schemas/checklists for high-value roles before expanding every role.
+- Add tests that rendered role prompts include required sections and remain under explicit size/breadth limits.
+
+## Product Boundary Check
+- Improves: Upgrade built-in role packages from compact prompts into richer structured role contracts while preventing prompt bloat and preserving Codex-native single-role execution.
+- In-scope surfaces: src/roles.ts, src/codex-prompts.ts, src/agents.ts, src/generated-surfaces.ts, tests/codex-prompts.test.ts, tests/roles.test.ts, tests/agents-templates.test.ts, docs/truthmark/engineering/codex/roles-and-workflows.md
+- Lightweight prototype use: preserved; new depth is opt-in and selected by role/workflow relevance.
+- Codex-native contract: preserved; built around `AGENTS.md`, `.codex/**`, npm package assets, and `opengamestudio` commands.
+- Reviewable evidence: source files, generated project files, tests, validation output, and OpenSpec artifacts.
+- Explicit non-goals: no telemetry, planner/next, parallel orchestration, hosted daemon, hidden memory, non-Codex runtime replacement, or mandatory heavyweight lifecycle.
+
+## Impact
+- Source: src/roles.ts, src/codex-prompts.ts, src/agents.ts, src/generated-surfaces.ts, tests/codex-prompts.test.ts, tests/roles.test.ts, tests/agents-templates.test.ts, docs/truthmark/engineering/codex/roles-and-workflows.md
+- Tests: focused Vitest suites plus `npm run validate`.
+- Docs/truth: update routed Truthmark engineering/product docs only when implementation changes behavior; this proposal itself is planning-only.
diff --git a/openspec/changes/catch-up-role-prompt-depth/specs/codex-studio-role-prompt-depth/spec.md b/openspec/changes/catch-up-role-prompt-depth/specs/codex-studio-role-prompt-depth/spec.md
new file mode 100644
index 0000000..4958ddb
--- /dev/null
+++ b/openspec/changes/catch-up-role-prompt-depth/specs/codex-studio-role-prompt-depth/spec.md
@@ -0,0 +1,30 @@
+# Role Prompt Sophistication Catch-Up Specification
+
+## ADDED Requirements
+
+### Requirement: Structured role contracts
+Built-in role prompts SHALL expose responsibilities, expected inputs, expected outputs, quality gates, and stop conditions in a consistent compact shape.
+
+#### Scenario: A release-manager role run is rendered
+- **GIVEN** a release-manager role run is rendered
+- **WHEN** the relevant CLI, renderer, validation, or test path is exercised
+- **THEN** the expected behavior is observable through local files or deterministic output
+
+
+### Requirement: Shared fragments
+Repeated guidance SHALL be shared through renderer fragments instead of copy-pasted across role definitions.
+
+#### Scenario: Shared write-policy wording changes
+- **GIVEN** shared write-policy wording changes
+- **WHEN** the relevant CLI, renderer, validation, or test path is exercised
+- **THEN** the expected behavior is observable through local files or deterministic output
+
+
+### Requirement: Prompt budget guard
+Role rendering tests SHALL enforce that a single role prompt does not include unrelated role bodies, all templates, or all engine references.
+
+#### Scenario: A role prompt grows beyond the configured budget
+- **GIVEN** a role prompt grows beyond the configured budget
+- **WHEN** the relevant CLI, renderer, validation, or test path is exercised
+- **THEN** the expected behavior is observable through local files or deterministic output
+
diff --git a/openspec/changes/catch-up-role-prompt-depth/tasks.md b/openspec/changes/catch-up-role-prompt-depth/tasks.md
new file mode 100644
index 0000000..f827939
--- /dev/null
+++ b/openspec/changes/catch-up-role-prompt-depth/tasks.md
@@ -0,0 +1,28 @@
+# Role Prompt Sophistication Catch-Up Tasks
+
+## Implementation Checklist
+- [x] Read `AGENTS.md` and `docs/architecture/product-boundary.md`; confirm the plan still stays inside the product boundary.
+- [x] Add or update the smallest focused tests for the first behavior slice.
+- [x] Run the focused failing test and confirm it fails for the expected reason.
+- [x] Implement the minimal registry/renderer/asset change for that slice.
+- [x] Re-run the focused test and confirm it passes.
+- [x] Repeat the TDD loop for each remaining slice in this plan.
+- [x] Extend the role package model with optional structured sections: responsibilities, inputs to inspect, outputs, quality gates, collaboration notes, stop conditions, and handoff format.
+- [x] Move repeated guidance into shared compact fragments rendered only when relevant.
+- [x] Add role-specific output schemas/checklists for high-value roles before expanding every role.
+- [x] Add tests that rendered role prompts include required sections and remain under explicit size/breadth limits.
+- [x] Update generated-surface/package validation expectations where assets or commands change.
+- [x] Run `git diff --check`.
+- [x] Run focused tests for touched areas.
+- [x] Run `npm run validate` before any parity or readiness claim.
+- [x] If functional behavior changed, update routed Truthmark docs and run `npx truthmark check --json` and `npx truthmark index --json`.
+
+## Suggested Focused Commands
+- `npm test -- --run tests/roles.test.ts tests/codex-prompts.test.ts tests/functionality-gap-pass.test.ts`
+- `npm test -- --run tests/project-workflow.test.ts tests/validation.test.ts`
+- `npm run validate`
+
+## Acceptance Criteria
+- OpenSpec validation for this change passes.
+- The new or changed OGS surfaces are locally reviewable and package-aware.
+- No explicit deferred/future-only feature becomes a user-facing command or required behavior.
diff --git a/openspec/changes/catch-up-workflow-skill-catalog/.openspec.yaml b/openspec/changes/catch-up-workflow-skill-catalog/.openspec.yaml
new file mode 100644
index 0000000..3ac681e
--- /dev/null
+++ b/openspec/changes/catch-up-workflow-skill-catalog/.openspec.yaml
@@ -0,0 +1,2 @@
+schema: spec-driven
+created: 2026-06-17
diff --git a/openspec/changes/catch-up-workflow-skill-catalog/README.md b/openspec/changes/catch-up-workflow-skill-catalog/README.md
new file mode 100644
index 0000000..01c86cd
--- /dev/null
+++ b/openspec/changes/catch-up-workflow-skill-catalog/README.md
@@ -0,0 +1,3 @@
+# catch-up-workflow-skill-catalog
+
+Plan Open Game Studio improvements for catch-up-workflow-skill-catalog relative to CCGS within the Codex-native product boundary
diff --git a/openspec/changes/catch-up-workflow-skill-catalog/design.md b/openspec/changes/catch-up-workflow-skill-catalog/design.md
new file mode 100644
index 0000000..a488f2f
--- /dev/null
+++ b/openspec/changes/catch-up-workflow-skill-catalog/design.md
@@ -0,0 +1,34 @@
+# Workflow And Skill Catalog Catch-Up Design
+
+## Architecture
+Expand workflow coverage into a curated Codex-native catalog of game-development actions without importing CCGS slash-command ceremony or turning OGS into a general task manager. The implementation should extend the existing TypeScript registries and renderers instead of introducing a separate orchestration platform. Built-in depth belongs in package-shipped registries/assets; project-specific depth belongs in explicit reviewable local files.
+
+## Current Gap Evidence
+Open Game Studio has 13 workflow shortcuts while CCGS exposes 73 skills across onboarding, design, QA, testing, release, sprint, team, localization, hotfix, and review workflows.
+
+## Key Decisions
+1. Preserve Open Game Studio's local-first, Codex-native runtime.
+2. Make added depth discoverable and validated, but do not force it into every prompt.
+3. Select context by role/workflow/task relevance; never load all roles, all workflows, all templates, or all engine references for one run.
+4. Keep implementation tasks test-first and package-smoke verified where package assets change.
+
+## Data And Surface Contracts
+- `src/workflows.ts`
+- `src/cli.ts`
+- `src/templates.ts`
+- `src/projects.ts`
+- `src/validation.ts`
+- `tests/functionality-gap-pass.test.ts`
+- `tests/cli-prompt-surface.test.ts`
+- `tests/project-workflow.test.ts`
+- `templates/`
+
+## Alternatives Rejected
+- Directly copying CCGS `.claude/**` files into generated projects: rejected because OGS is Codex-native and uses `AGENTS.md` / `.codex/**`.
+- Adding a general agent orchestrator or background controller: rejected by product boundary.
+- Adding broad prompt bundles that include every reference file: rejected because depth must come from selected context.
+
+## Risks And Mitigations
+- Prompt bloat: add renderer tests and selected-context assertions.
+- Registry drift: update validation to fail when a registry entry lacks materialized/generated/package coverage.
+- Product-boundary drift: keep future-only/deferred surfaces absent and add negative tests when relevant.
diff --git a/openspec/changes/catch-up-workflow-skill-catalog/proposal.md b/openspec/changes/catch-up-workflow-skill-catalog/proposal.md
new file mode 100644
index 0000000..00b8f93
--- /dev/null
+++ b/openspec/changes/catch-up-workflow-skill-catalog/proposal.md
@@ -0,0 +1,29 @@
+# Workflow And Skill Catalog Catch-Up Proposal
+
+## Why
+Open Game Studio has 13 workflow shortcuts while CCGS exposes 73 skills across onboarding, design, QA, testing, release, sprint, team, localization, hotfix, and review workflows.
+
+Current comparison baseline:
+- Open Game Studio: 20 roles, 13 workflow prompt shortcuts, 13 templates, 12 engine-reference files, TypeScript CLI/package, Codex-native run path, validation gate.
+- Claude Code Game Studios: 49 agents, 73 skills, 40 templates, 46 engine-reference files, richer authored specialist prompts and skill/testing framework.
+- Explicitly ignored/deferred for Open Game Studio: telemetry, planner/next, parallel orchestration, hard output-ownership enforcement, hosted service/daemon/background controller, hidden memory/checkpoints, non-Codex runtime replacements, mandatory heavyweight lifecycle.
+
+
+## What Changes
+- Create a workflow taxonomy: onboarding/discovery, design/architecture, implementation planning, QA/testing, release/hotfix, localization/accessibility, and team coordination.
+- Add high-value workflow prompt shortcuts before low-value aliases: start/onboard, brainstorm, prototype, architecture-decision, architecture-review, create-epics, create-stories, sprint-plan, sprint-status, story-readiness, story-done, qa-plan, regression-suite, security-audit, perf-profile, release-checklist, hotfix, localization-plan.
+- Keep workflow output prompt-only unless an existing CLI surface already owns state changes.
+- Add tests for command help, workflow rendering, aliases, and project materialization.
+
+## Product Boundary Check
+- Improves: Expand workflow coverage into a curated Codex-native catalog of game-development actions without importing CCGS slash-command ceremony or turning OGS into a general task manager.
+- In-scope surfaces: src/workflows.ts, src/cli.ts, src/templates.ts, src/projects.ts, src/validation.ts, tests/functionality-gap-pass.test.ts, tests/cli-prompt-surface.test.ts, tests/project-workflow.test.ts, templates/
+- Lightweight prototype use: preserved; new depth is opt-in and selected by role/workflow relevance.
+- Codex-native contract: preserved; built around `AGENTS.md`, `.codex/**`, npm package assets, and `opengamestudio` commands.
+- Reviewable evidence: source files, generated project files, tests, validation output, and OpenSpec artifacts.
+- Explicit non-goals: no telemetry, planner/next, parallel orchestration, hosted daemon, hidden memory, non-Codex runtime replacement, or mandatory heavyweight lifecycle.
+
+## Impact
+- Source: src/workflows.ts, src/cli.ts, src/templates.ts, src/projects.ts, src/validation.ts, tests/functionality-gap-pass.test.ts, tests/cli-prompt-surface.test.ts, tests/project-workflow.test.ts, templates/
+- Tests: focused Vitest suites plus `npm run validate`.
+- Docs/truth: update routed Truthmark engineering/product docs only when implementation changes behavior; this proposal itself is planning-only.
diff --git a/openspec/changes/catch-up-workflow-skill-catalog/specs/codex-studio-workflow-catalog/spec.md b/openspec/changes/catch-up-workflow-skill-catalog/specs/codex-studio-workflow-catalog/spec.md
new file mode 100644
index 0000000..6010432
--- /dev/null
+++ b/openspec/changes/catch-up-workflow-skill-catalog/specs/codex-studio-workflow-catalog/spec.md
@@ -0,0 +1,30 @@
+# Workflow And Skill Catalog Catch-Up Specification
+
+## ADDED Requirements
+
+### Requirement: Curated workflow taxonomy
+The workflow registry SHALL group built-in workflows by game-development intent and SHALL document which CCGS-derived gaps each group covers.
+
+#### Scenario: A user asks for release readiness
+- **GIVEN** a user asks for release readiness
+- **WHEN** the relevant CLI, renderer, validation, or test path is exercised
+- **THEN** the expected behavior is observable through local files or deterministic output
+
+
+### Requirement: Prompt-only default
+New workflow shortcuts SHALL render bounded prompts by default and SHALL NOT create hidden lifecycle state unless explicitly routed through existing task or approval commands.
+
+#### Scenario: A new workflow id is added
+- **GIVEN** a new workflow id is added
+- **WHEN** the relevant CLI, renderer, validation, or test path is exercised
+- **THEN** the expected behavior is observable through local files or deterministic output
+
+
+### Requirement: CLI discoverability
+The CLI SHALL make built-in workflows discoverable through help output and validation SHALL prove each registered workflow renders.
+
+#### Scenario: A prototype project uses a workflow
+- **GIVEN** a prototype project uses a workflow
+- **WHEN** the relevant CLI, renderer, validation, or test path is exercised
+- **THEN** the expected behavior is observable through local files or deterministic output
+
diff --git a/openspec/changes/catch-up-workflow-skill-catalog/tasks.md b/openspec/changes/catch-up-workflow-skill-catalog/tasks.md
new file mode 100644
index 0000000..395ae3d
--- /dev/null
+++ b/openspec/changes/catch-up-workflow-skill-catalog/tasks.md
@@ -0,0 +1,28 @@
+# Workflow And Skill Catalog Catch-Up Tasks
+
+## Implementation Checklist
+- [x] Read `AGENTS.md` and `docs/architecture/product-boundary.md`; confirm the plan still stays inside the product boundary.
+- [x] Add or update the smallest focused tests for the first behavior slice.
+- [x] Run the focused failing test and confirm it fails for the expected reason.
+- [x] Implement the minimal registry/renderer/asset change for that slice.
+- [x] Re-run the focused test and confirm it passes.
+- [x] Repeat the TDD loop for each remaining slice in this plan.
+- [x] Create a workflow taxonomy: onboarding/discovery, design/architecture, implementation planning, QA/testing, release/hotfix, localization/accessibility, and team coordination.
+- [x] Add high-value workflow prompt shortcuts before low-value aliases: start/onboard, brainstorm, prototype, architecture-decision, architecture-review, create-epics, create-stories, sprint-plan, sprint-status, story-readiness, story-done, qa-plan, regression-suite, security-audit, perf-profile, release-checklist, hotfix, localization-plan.
+- [x] Keep workflow output prompt-only unless an existing CLI surface already owns state changes.
+- [x] Add tests for command help, workflow rendering, aliases, and project materialization.
+- [x] Update generated-surface/package validation expectations where assets or commands change.
+- [x] Run `git diff --check`.
+- [x] Run focused tests for touched areas.
+- [x] Run `npm run validate` before any parity or readiness claim.
+- [x] If functional behavior changed, update routed Truthmark docs and run `npx truthmark check --json` and `npx truthmark index --json`.
+
+## Suggested Focused Commands
+- `npm test -- --run tests/roles.test.ts tests/codex-prompts.test.ts tests/functionality-gap-pass.test.ts`
+- `npm test -- --run tests/project-workflow.test.ts tests/validation.test.ts`
+- `npm run validate`
+
+## Acceptance Criteria
+- OpenSpec validation for this change passes.
+- The new or changed OGS surfaces are locally reviewable and package-aware.
+- No explicit deferred/future-only feature becomes a user-facing command or required behavior.
diff --git a/openspec/config.yaml b/openspec/config.yaml
new file mode 100644
index 0000000..392946c
--- /dev/null
+++ b/openspec/config.yaml
@@ -0,0 +1,20 @@
+schema: spec-driven
+
+# Project context (optional)
+# This is shown to AI when creating artifacts.
+# Add your tech stack, conventions, style guides, domain knowledge, etc.
+# Example:
+#   context: |
+#     Tech stack: TypeScript, React, Node.js
+#     We use conventional commits
+#     Domain: e-commerce platform
+
+# Per-artifact rules (optional)
+# Add custom rules for specific artifacts.
+# Example:
+#   rules:
+#     proposal:
+#       - Keep proposals under 500 words
+#       - Always include a "Non-goals" section
+#     tasks:
+#       - Break tasks into chunks of max 2 hours
diff --git a/research/2026-06-17-catch-up-behavioral-evaluation-plan.md b/research/2026-06-17-catch-up-behavioral-evaluation-plan.md
new file mode 100644
index 0000000..4bece50
--- /dev/null
+++ b/research/2026-06-17-catch-up-behavioral-evaluation-plan.md
@@ -0,0 +1,64 @@
+# Behavioral Evaluation Catch-Up Implementation Plan
+
+> **For Hermes:** Use subagent-driven-development skill to implement this plan task-by-task.
+
+**Goal:** Add a lightweight, local, deterministic behavioral evaluation framework for OGS roles/workflows/templates that catches weak prompt contracts without requiring hosted evaluators or telemetry.
+
+**Architecture:** This plan is refined by OpenSpec change `catch-up-behavioral-evaluation`. The markdown file is the human-facing research index; the canonical refined implementation contract lives in the OpenSpec proposal, design, requirements, and tasks listed below.
+
+**Tech Stack:** TypeScript, NodeNext, npm package assets, Vitest, OpenSpec, Truthmark repository-truth validation.
+
+---
+
+## Gap Summary
+
+Open Game Studio validates CLI and generated-surface mechanics, but CCGS includes a skill/agent testing framework and rubrics that evaluate workflow and prompt behavior more directly.
+
+Current comparison baseline:
+- Open Game Studio: 20 roles, 13 workflow prompt shortcuts, 13 templates, 12 engine-reference files, TypeScript CLI/package, Codex-native run path, validation gate.
+- Claude Code Game Studios: 49 agents, 73 skills, 40 templates, 46 engine-reference files, richer authored specialist prompts and skill/testing framework.
+- Explicitly ignored/deferred for Open Game Studio: telemetry, planner/next, parallel orchestration, hard output-ownership enforcement, hosted service/daemon/background controller, hidden memory/checkpoints, non-Codex runtime replacements, mandatory heavyweight lifecycle.
+
+
+## OpenSpec Refinement
+
+- Change: `openspec/changes/catch-up-behavioral-evaluation/`
+- Proposal: `openspec/changes/catch-up-behavioral-evaluation/proposal.md`
+- Design: `openspec/changes/catch-up-behavioral-evaluation/design.md`
+- Requirements: `openspec/changes/catch-up-behavioral-evaluation/specs/codex-studio-behavioral-evaluation/spec.md`
+- Tasks: `openspec/changes/catch-up-behavioral-evaluation/tasks.md`
+
+## Product Boundary Check
+
+- Mission improvement: Add a lightweight, local, deterministic behavioral evaluation framework for OGS roles/workflows/templates that catches weak prompt contracts without requiring hosted evaluators or telemetry.
+- In-scope surfaces: `tests/`, `src/validation.ts`, `src/codex-prompts.ts`, `src/workflows.ts`, `docs/system-verification.md`, `docs/workflow-validation.md`, `package.json`
+- Lightweight mode preserved: yes; additions are opt-in/discoverable and selected by relevance.
+- Codex-native preserved: yes; no `.claude/**` clone, no hosted runtime, no daemon.
+- Reviewable local outputs: OpenSpec artifacts, source diffs, generated project files, package assets, validation output.
+- Explicitly excluded from this plan: telemetry, planner/next, parallel orchestration, hard ownership enforcement, hidden memory/checkpoints, non-Codex runtime replacement, mandatory heavyweight lifecycle.
+
+## Bite-Sized Implementation Tasks
+
+- [ ] Define an evaluation fixture format for role/workflow scenarios with expected prompt obligations and forbidden drift.
+- [ ] Add static behavior checks for required sections, relevant templates, selected context, forbidden future-only surfaces, and output contract coverage.
+- [ ] Add representative scenarios for core workflows and new catch-up roles.
+- [ ] Expose evaluation through npm scripts or validation subchecks only if it stays local and deterministic.
+- [ ] Document how to add a scenario when a role/workflow is added.
+- [ ] Add focused failing tests before each implementation slice.
+- [ ] Implement the smallest code/asset changes to pass each focused test.
+- [ ] Update validation and package smoke coverage for every new generated or packaged surface.
+- [ ] Update routed Truthmark docs only for behavior that actually ships.
+- [ ] Run `git diff --check`, focused tests, `npm run validate`, and applicable Truthmark gates.
+
+## Verification Commands
+
+```bash
+openspec validate catch-up-behavioral-evaluation --strict --json
+openspec status --change catch-up-behavioral-evaluation --json
+git diff --check -- research/2026-06-17-catch-up-behavioral-evaluation-plan.md openspec/changes/catch-up-behavioral-evaluation
+npm run validate
+```
+
+## Notes For Implementers
+
+Do not treat CCGS parity as file-for-file cloning. Translate useful CCGS coverage into Open Game Studio's local, Codex-native, package-friendly boundary. Keep prompt depth selected and bounded.
diff --git a/research/2026-06-17-catch-up-customization-ergonomics-plan.md b/research/2026-06-17-catch-up-customization-ergonomics-plan.md
new file mode 100644
index 0000000..a0ceccf
--- /dev/null
+++ b/research/2026-06-17-catch-up-customization-ergonomics-plan.md
@@ -0,0 +1,64 @@
+# Customization Ergonomics Catch-Up Implementation Plan
+
+> **For Hermes:** Use subagent-driven-development skill to implement this plan task-by-task.
+
+**Goal:** Add project-local customization packs for roles, workflows, templates, and studio policy that are schema-validated, visible in the repo, and safely merged with built-ins without becoming a general plugin/orchestrator platform.
+
+**Architecture:** This plan is refined by OpenSpec change `catch-up-customization-ergonomics`. The markdown file is the human-facing research index; the canonical refined implementation contract lives in the OpenSpec proposal, design, requirements, and tasks listed below.
+
+**Tech Stack:** TypeScript, NodeNext, npm package assets, Vitest, OpenSpec, Truthmark repository-truth validation.
+
+---
+
+## Gap Summary
+
+CCGS users can edit `.claude/agents`, `.claude/skills`, `.claude/rules`, and hooks directly. OGS is cleaner as a package but less no-code/custom-pack friendly because built-ins live primarily in TypeScript registries.
+
+Current comparison baseline:
+- Open Game Studio: 20 roles, 13 workflow prompt shortcuts, 13 templates, 12 engine-reference files, TypeScript CLI/package, Codex-native run path, validation gate.
+- Claude Code Game Studios: 49 agents, 73 skills, 40 templates, 46 engine-reference files, richer authored specialist prompts and skill/testing framework.
+- Explicitly ignored/deferred for Open Game Studio: telemetry, planner/next, parallel orchestration, hard output-ownership enforcement, hosted service/daemon/background controller, hidden memory/checkpoints, non-Codex runtime replacements, mandatory heavyweight lifecycle.
+
+
+## OpenSpec Refinement
+
+- Change: `openspec/changes/catch-up-customization-ergonomics/`
+- Proposal: `openspec/changes/catch-up-customization-ergonomics/proposal.md`
+- Design: `openspec/changes/catch-up-customization-ergonomics/design.md`
+- Requirements: `openspec/changes/catch-up-customization-ergonomics/specs/codex-studio-customization-ergonomics/spec.md`
+- Tasks: `openspec/changes/catch-up-customization-ergonomics/tasks.md`
+
+## Product Boundary Check
+
+- Mission improvement: Add project-local customization packs for roles, workflows, templates, and studio policy that are schema-validated, visible in the repo, and safely merged with built-ins without becoming a general plugin/orchestrator platform.
+- In-scope surfaces: `src/config.ts`, `src/roles.ts`, `src/workflows.ts`, `src/templates.ts`, `src/validation.ts`, `src/projects.ts`, `tests/validation.test.ts`, `tests/project-workflow.test.ts`, `docs/setup.md`, `docs/examples.md`
+- Lightweight mode preserved: yes; additions are opt-in/discoverable and selected by relevance.
+- Codex-native preserved: yes; no `.claude/**` clone, no hosted runtime, no daemon.
+- Reviewable local outputs: OpenSpec artifacts, source diffs, generated project files, package assets, validation output.
+- Explicitly excluded from this plan: telemetry, planner/next, parallel orchestration, hard ownership enforcement, hidden memory/checkpoints, non-Codex runtime replacement, mandatory heavyweight lifecycle.
+
+## Bite-Sized Implementation Tasks
+
+- [ ] Design `opengamestudio.config.json` or `.codex/studio/config.json` extension points for project-local role/workflow/template packs.
+- [ ] Define schema rules for custom role ids, workflow ids, template metadata, path containment, override/extend behavior, and conflict diagnostics.
+- [ ] Update init/validate/status/templates list/run prompt paths to load validated local packs.
+- [ ] Add tests for valid custom packs, duplicate ids, unsafe paths, missing template files, and built-in override policy.
+- [ ] Document examples that edit local pack files instead of editing package source.
+- [ ] Add focused failing tests before each implementation slice.
+- [ ] Implement the smallest code/asset changes to pass each focused test.
+- [ ] Update validation and package smoke coverage for every new generated or packaged surface.
+- [ ] Update routed Truthmark docs only for behavior that actually ships.
+- [ ] Run `git diff --check`, focused tests, `npm run validate`, and applicable Truthmark gates.
+
+## Verification Commands
+
+```bash
+openspec validate catch-up-customization-ergonomics --strict --json
+openspec status --change catch-up-customization-ergonomics --json
+git diff --check -- research/2026-06-17-catch-up-customization-ergonomics-plan.md openspec/changes/catch-up-customization-ergonomics
+npm run validate
+```
+
+## Notes For Implementers
+
+Do not treat CCGS parity as file-for-file cloning. Translate useful CCGS coverage into Open Game Studio's local, Codex-native, package-friendly boundary. Keep prompt depth selected and bounded.
diff --git a/research/2026-06-17-catch-up-domain-role-coverage-plan.md b/research/2026-06-17-catch-up-domain-role-coverage-plan.md
new file mode 100644
index 0000000..a3113d7
--- /dev/null
+++ b/research/2026-06-17-catch-up-domain-role-coverage-plan.md
@@ -0,0 +1,63 @@
+# Domain Role Coverage Catch-Up Implementation Plan
+
+> **For Hermes:** Use subagent-driven-development skill to implement this plan task-by-task.
+
+**Goal:** Expand Open Game Studio role coverage across game-development specialties while preserving bounded Codex prompts and the AGENTS.md/.codex generated-surface contract.
+
+**Architecture:** This plan is refined by OpenSpec change `catch-up-domain-role-coverage`. The markdown file is the human-facing research index; the canonical refined implementation contract lives in the OpenSpec proposal, design, requirements, and tasks listed below.
+
+**Tech Stack:** TypeScript, NodeNext, npm package assets, Vitest, OpenSpec, Truthmark repository-truth validation.
+
+---
+
+## Gap Summary
+
+Open Game Studio has 20 roles while CCGS has 49 agents. The missing value is not raw count; it is specialist coverage for production domains that a game developer reasonably expects.
+
+Current comparison baseline:
+- Open Game Studio: 20 roles, 13 workflow prompt shortcuts, 13 templates, 12 engine-reference files, TypeScript CLI/package, Codex-native run path, validation gate.
+- Claude Code Game Studios: 49 agents, 73 skills, 40 templates, 46 engine-reference files, richer authored specialist prompts and skill/testing framework.
+- Explicitly ignored/deferred for Open Game Studio: telemetry, planner/next, parallel orchestration, hard output-ownership enforcement, hosted service/daemon/background controller, hidden memory/checkpoints, non-Codex runtime replacements, mandatory heavyweight lifecycle.
+
+
+## OpenSpec Refinement
+
+- Change: `openspec/changes/catch-up-domain-role-coverage/`
+- Proposal: `openspec/changes/catch-up-domain-role-coverage/proposal.md`
+- Design: `openspec/changes/catch-up-domain-role-coverage/design.md`
+- Requirements: `openspec/changes/catch-up-domain-role-coverage/specs/codex-studio-domain-role-coverage/spec.md`
+- Tasks: `openspec/changes/catch-up-domain-role-coverage/tasks.md`
+
+## Product Boundary Check
+
+- Mission improvement: Expand Open Game Studio role coverage across game-development specialties while preserving bounded Codex prompts and the AGENTS.md/.codex generated-surface contract.
+- In-scope surfaces: `src/roles.ts`, `src/codex-prompts.ts`, `src/projects.ts`, `src/validation.ts`, `tests/roles.test.ts`, `tests/codex-prompts.test.ts`, `tests/functionality-gap-pass.test.ts`, `docs/truthmark/engineering/codex/roles-and-workflows.md`
+- Lightweight mode preserved: yes; additions are opt-in/discoverable and selected by relevance.
+- Codex-native preserved: yes; no `.claude/**` clone, no hosted runtime, no daemon.
+- Reviewable local outputs: OpenSpec artifacts, source diffs, generated project files, package assets, validation output.
+- Explicitly excluded from this plan: telemetry, planner/next, parallel orchestration, hard ownership enforcement, hidden memory/checkpoints, non-Codex runtime replacement, mandatory heavyweight lifecycle.
+
+## Bite-Sized Implementation Tasks
+
+- [ ] Add domain clusters for audio, level/world/content, systems/economy, live ops/community/localization/accessibility, security/devops/performance/network/AI/UI programming.
+- [ ] Add only roles with clear game-studio outputs and selected context strategies; do not add a role just to mirror a CCGS name.
+- [ ] Update role package rendering and generated project prompt materialization for every new role.
+- [ ] Add validation coverage that all role packages render and no single role run loads all roles.
+- [ ] Add focused failing tests before each implementation slice.
+- [ ] Implement the smallest code/asset changes to pass each focused test.
+- [ ] Update validation and package smoke coverage for every new generated or packaged surface.
+- [ ] Update routed Truthmark docs only for behavior that actually ships.
+- [ ] Run `git diff --check`, focused tests, `npm run validate`, and applicable Truthmark gates.
+
+## Verification Commands
+
+```bash
+openspec validate catch-up-domain-role-coverage --strict --json
+openspec status --change catch-up-domain-role-coverage --json
+git diff --check -- research/2026-06-17-catch-up-domain-role-coverage-plan.md openspec/changes/catch-up-domain-role-coverage
+npm run validate
+```
+
+## Notes For Implementers
+
+Do not treat CCGS parity as file-for-file cloning. Translate useful CCGS coverage into Open Game Studio's local, Codex-native, package-friendly boundary. Keep prompt depth selected and bounded.
diff --git a/research/2026-06-17-catch-up-engine-reference-depth-plan.md b/research/2026-06-17-catch-up-engine-reference-depth-plan.md
new file mode 100644
index 0000000..9c53a6b
--- /dev/null
+++ b/research/2026-06-17-catch-up-engine-reference-depth-plan.md
@@ -0,0 +1,64 @@
+# Engine Reference Depth Catch-Up Implementation Plan
+
+> **For Hermes:** Use subagent-driven-development skill to implement this plan task-by-task.
+
+**Goal:** Deepen packaged engine references for Godot, Unity, and Unreal with module-level and plugin-level files that can be selected by relevance without bloating every prompt.
+
+**Architecture:** This plan is refined by OpenSpec change `catch-up-engine-reference-depth`. The markdown file is the human-facing research index; the canonical refined implementation contract lives in the OpenSpec proposal, design, requirements, and tasks listed below.
+
+**Tech Stack:** TypeScript, NodeNext, npm package assets, Vitest, OpenSpec, Truthmark repository-truth validation.
+
+---
+
+## Gap Summary
+
+Open Game Studio ships 12 compact engine-reference files while CCGS ships roughly 46 files with modules, plugins, deprecated APIs, breaking changes, and best-practice guidance for Godot, Unity, and Unreal.
+
+Current comparison baseline:
+- Open Game Studio: 20 roles, 13 workflow prompt shortcuts, 13 templates, 12 engine-reference files, TypeScript CLI/package, Codex-native run path, validation gate.
+- Claude Code Game Studios: 49 agents, 73 skills, 40 templates, 46 engine-reference files, richer authored specialist prompts and skill/testing framework.
+- Explicitly ignored/deferred for Open Game Studio: telemetry, planner/next, parallel orchestration, hard output-ownership enforcement, hosted service/daemon/background controller, hidden memory/checkpoints, non-Codex runtime replacements, mandatory heavyweight lifecycle.
+
+
+## OpenSpec Refinement
+
+- Change: `openspec/changes/catch-up-engine-reference-depth/`
+- Proposal: `openspec/changes/catch-up-engine-reference-depth/proposal.md`
+- Design: `openspec/changes/catch-up-engine-reference-depth/design.md`
+- Requirements: `openspec/changes/catch-up-engine-reference-depth/specs/codex-studio-engine-reference-depth/spec.md`
+- Tasks: `openspec/changes/catch-up-engine-reference-depth/tasks.md`
+
+## Product Boundary Check
+
+- Mission improvement: Deepen packaged engine references for Godot, Unity, and Unreal with module-level and plugin-level files that can be selected by relevance without bloating every prompt.
+- In-scope surfaces: `engine_reference/`, `src/engine-reference.ts`, `src/engines.ts`, `src/prompt-context.ts`, `src/validation.ts`, `tests/engine-system.test.ts`, `tests/codex-context-files.test.ts`, `docs/truthmark/engineering/codex/runtime-and-tasks.md`
+- Lightweight mode preserved: yes; additions are opt-in/discoverable and selected by relevance.
+- Codex-native preserved: yes; no `.claude/**` clone, no hosted runtime, no daemon.
+- Reviewable local outputs: OpenSpec artifacts, source diffs, generated project files, package assets, validation output.
+- Explicitly excluded from this plan: telemetry, planner/next, parallel orchestration, hard ownership enforcement, hidden memory/checkpoints, non-Codex runtime replacement, mandatory heavyweight lifecycle.
+
+## Bite-Sized Implementation Tasks
+
+- [ ] Add per-engine `current-best-practices.md`, `deprecated-apis.md`, `breaking-changes.md`, and module files for animation, audio, input, navigation, networking, physics, rendering, UI.
+- [ ] Add plugin references for Unity Addressables/Cinemachine/DOTS and Unreal GAS/Common UI/PCG where in-scope.
+- [ ] Add reference metadata: engine, version reviewed, source/review date, tags, applicable roles/workflows.
+- [ ] Update context selection so engine-specialist prompts select only relevant module/plugin references.
+- [ ] Validate package shipping and temp-cwd installed-bin access.
+- [ ] Add focused failing tests before each implementation slice.
+- [ ] Implement the smallest code/asset changes to pass each focused test.
+- [ ] Update validation and package smoke coverage for every new generated or packaged surface.
+- [ ] Update routed Truthmark docs only for behavior that actually ships.
+- [ ] Run `git diff --check`, focused tests, `npm run validate`, and applicable Truthmark gates.
+
+## Verification Commands
+
+```bash
+openspec validate catch-up-engine-reference-depth --strict --json
+openspec status --change catch-up-engine-reference-depth --json
+git diff --check -- research/2026-06-17-catch-up-engine-reference-depth-plan.md openspec/changes/catch-up-engine-reference-depth
+npm run validate
+```
+
+## Notes For Implementers
+
+Do not treat CCGS parity as file-for-file cloning. Translate useful CCGS coverage into Open Game Studio's local, Codex-native, package-friendly boundary. Keep prompt depth selected and bounded.
diff --git a/research/2026-06-17-catch-up-production-templates-plan.md b/research/2026-06-17-catch-up-production-templates-plan.md
new file mode 100644
index 0000000..fd1f915
--- /dev/null
+++ b/research/2026-06-17-catch-up-production-templates-plan.md
@@ -0,0 +1,63 @@
+# Production Template Depth Catch-Up Implementation Plan
+
+> **For Hermes:** Use subagent-driven-development skill to implement this plan task-by-task.
+
+**Goal:** Add a richer built-in template pack for game production artifacts while keeping templates package-shipped, listed, selected by workflow relevance, and validated through npm pack smoke tests.
+
+**Architecture:** This plan is refined by OpenSpec change `catch-up-production-templates`. The markdown file is the human-facing research index; the canonical refined implementation contract lives in the OpenSpec proposal, design, requirements, and tasks listed below.
+
+**Tech Stack:** TypeScript, NodeNext, npm package assets, Vitest, OpenSpec, Truthmark repository-truth validation.
+
+---
+
+## Gap Summary
+
+Open Game Studio has 13 templates while CCGS has roughly 40 production templates spanning design, architecture, QA, release, UX, audio, art, risk, and postmortem artifacts.
+
+Current comparison baseline:
+- Open Game Studio: 20 roles, 13 workflow prompt shortcuts, 13 templates, 12 engine-reference files, TypeScript CLI/package, Codex-native run path, validation gate.
+- Claude Code Game Studios: 49 agents, 73 skills, 40 templates, 46 engine-reference files, richer authored specialist prompts and skill/testing framework.
+- Explicitly ignored/deferred for Open Game Studio: telemetry, planner/next, parallel orchestration, hard output-ownership enforcement, hosted service/daemon/background controller, hidden memory/checkpoints, non-Codex runtime replacements, mandatory heavyweight lifecycle.
+
+
+## OpenSpec Refinement
+
+- Change: `openspec/changes/catch-up-production-templates/`
+- Proposal: `openspec/changes/catch-up-production-templates/proposal.md`
+- Design: `openspec/changes/catch-up-production-templates/design.md`
+- Requirements: `openspec/changes/catch-up-production-templates/specs/codex-studio-production-template-pack/spec.md`
+- Tasks: `openspec/changes/catch-up-production-templates/tasks.md`
+
+## Product Boundary Check
+
+- Mission improvement: Add a richer built-in template pack for game production artifacts while keeping templates package-shipped, listed, selected by workflow relevance, and validated through npm pack smoke tests.
+- In-scope surfaces: `templates/`, `src/templates.ts`, `src/prompt-context.ts`, `src/validation.ts`, `tests/agents-templates.test.ts`, `tests/functionality-gap-pass.test.ts`, `tests/validation.test.ts`, `package.json`
+- Lightweight mode preserved: yes; additions are opt-in/discoverable and selected by relevance.
+- Codex-native preserved: yes; no `.claude/**` clone, no hosted runtime, no daemon.
+- Reviewable local outputs: OpenSpec artifacts, source diffs, generated project files, package assets, validation output.
+- Explicitly excluded from this plan: telemetry, planner/next, parallel orchestration, hard ownership enforcement, hidden memory/checkpoints, non-Codex runtime replacement, mandatory heavyweight lifecycle.
+
+## Bite-Sized Implementation Tasks
+
+- [ ] Add production templates for ADR, technical design, architecture traceability, art bible, sound bible, UX spec, accessibility requirements, test plan, test evidence, sprint plan, vertical-slice report, release notes, postmortem, risk register, economy model, difficulty curve, player journey, pitch document.
+- [ ] Represent each template in the template registry with category, path, short description, and relevant workflow/role hints.
+- [ ] Update package files and pack/install smoke checks so installed CLI can load the new templates from a temp cwd.
+- [ ] Add relevance-selection tests that a workflow includes only its mapped templates, not the whole pack.
+- [ ] Add focused failing tests before each implementation slice.
+- [ ] Implement the smallest code/asset changes to pass each focused test.
+- [ ] Update validation and package smoke coverage for every new generated or packaged surface.
+- [ ] Update routed Truthmark docs only for behavior that actually ships.
+- [ ] Run `git diff --check`, focused tests, `npm run validate`, and applicable Truthmark gates.
+
+## Verification Commands
+
+```bash
+openspec validate catch-up-production-templates --strict --json
+openspec status --change catch-up-production-templates --json
+git diff --check -- research/2026-06-17-catch-up-production-templates-plan.md openspec/changes/catch-up-production-templates
+npm run validate
+```
+
+## Notes For Implementers
+
+Do not treat CCGS parity as file-for-file cloning. Translate useful CCGS coverage into Open Game Studio's local, Codex-native, package-friendly boundary. Keep prompt depth selected and bounded.
diff --git a/research/2026-06-17-catch-up-role-prompt-depth-plan.md b/research/2026-06-17-catch-up-role-prompt-depth-plan.md
new file mode 100644
index 0000000..bf3eaf3
--- /dev/null
+++ b/research/2026-06-17-catch-up-role-prompt-depth-plan.md
@@ -0,0 +1,63 @@
+# Role Prompt Sophistication Catch-Up Implementation Plan
+
+> **For Hermes:** Use subagent-driven-development skill to implement this plan task-by-task.
+
+**Goal:** Upgrade built-in role packages from compact prompts into richer structured role contracts while preventing prompt bloat and preserving Codex-native single-role execution.
+
+**Architecture:** This plan is refined by OpenSpec change `catch-up-role-prompt-depth`. The markdown file is the human-facing research index; the canonical refined implementation contract lives in the OpenSpec proposal, design, requirements, and tasks listed below.
+
+**Tech Stack:** TypeScript, NodeNext, npm package assets, Vitest, OpenSpec, Truthmark repository-truth validation.
+
+---
+
+## Gap Summary
+
+Open Game Studio roles are compact and maintainable, but CCGS agents include richer responsibilities, collaboration protocol, delegation guidance, output formats, domain standards, and quality gates.
+
+Current comparison baseline:
+- Open Game Studio: 20 roles, 13 workflow prompt shortcuts, 13 templates, 12 engine-reference files, TypeScript CLI/package, Codex-native run path, validation gate.
+- Claude Code Game Studios: 49 agents, 73 skills, 40 templates, 46 engine-reference files, richer authored specialist prompts and skill/testing framework.
+- Explicitly ignored/deferred for Open Game Studio: telemetry, planner/next, parallel orchestration, hard output-ownership enforcement, hosted service/daemon/background controller, hidden memory/checkpoints, non-Codex runtime replacements, mandatory heavyweight lifecycle.
+
+
+## OpenSpec Refinement
+
+- Change: `openspec/changes/catch-up-role-prompt-depth/`
+- Proposal: `openspec/changes/catch-up-role-prompt-depth/proposal.md`
+- Design: `openspec/changes/catch-up-role-prompt-depth/design.md`
+- Requirements: `openspec/changes/catch-up-role-prompt-depth/specs/codex-studio-role-prompt-depth/spec.md`
+- Tasks: `openspec/changes/catch-up-role-prompt-depth/tasks.md`
+
+## Product Boundary Check
+
+- Mission improvement: Upgrade built-in role packages from compact prompts into richer structured role contracts while preventing prompt bloat and preserving Codex-native single-role execution.
+- In-scope surfaces: `src/roles.ts`, `src/codex-prompts.ts`, `src/agents.ts`, `src/generated-surfaces.ts`, `tests/codex-prompts.test.ts`, `tests/roles.test.ts`, `tests/agents-templates.test.ts`, `docs/truthmark/engineering/codex/roles-and-workflows.md`
+- Lightweight mode preserved: yes; additions are opt-in/discoverable and selected by relevance.
+- Codex-native preserved: yes; no `.claude/**` clone, no hosted runtime, no daemon.
+- Reviewable local outputs: OpenSpec artifacts, source diffs, generated project files, package assets, validation output.
+- Explicitly excluded from this plan: telemetry, planner/next, parallel orchestration, hard ownership enforcement, hidden memory/checkpoints, non-Codex runtime replacement, mandatory heavyweight lifecycle.
+
+## Bite-Sized Implementation Tasks
+
+- [ ] Extend the role package model with optional structured sections: responsibilities, inputs to inspect, outputs, quality gates, collaboration notes, stop conditions, and handoff format.
+- [ ] Move repeated guidance into shared compact fragments rendered only when relevant.
+- [ ] Add role-specific output schemas/checklists for high-value roles before expanding every role.
+- [ ] Add tests that rendered role prompts include required sections and remain under explicit size/breadth limits.
+- [ ] Add focused failing tests before each implementation slice.
+- [ ] Implement the smallest code/asset changes to pass each focused test.
+- [ ] Update validation and package smoke coverage for every new generated or packaged surface.
+- [ ] Update routed Truthmark docs only for behavior that actually ships.
+- [ ] Run `git diff --check`, focused tests, `npm run validate`, and applicable Truthmark gates.
+
+## Verification Commands
+
+```bash
+openspec validate catch-up-role-prompt-depth --strict --json
+openspec status --change catch-up-role-prompt-depth --json
+git diff --check -- research/2026-06-17-catch-up-role-prompt-depth-plan.md openspec/changes/catch-up-role-prompt-depth
+npm run validate
+```
+
+## Notes For Implementers
+
+Do not treat CCGS parity as file-for-file cloning. Translate useful CCGS coverage into Open Game Studio's local, Codex-native, package-friendly boundary. Keep prompt depth selected and bounded.
diff --git a/research/2026-06-17-catch-up-workflow-skill-catalog-plan.md b/research/2026-06-17-catch-up-workflow-skill-catalog-plan.md
new file mode 100644
index 0000000..004af66
--- /dev/null
+++ b/research/2026-06-17-catch-up-workflow-skill-catalog-plan.md
@@ -0,0 +1,63 @@
+# Workflow And Skill Catalog Catch-Up Implementation Plan
+
+> **For Hermes:** Use subagent-driven-development skill to implement this plan task-by-task.
+
+**Goal:** Expand workflow coverage into a curated Codex-native catalog of game-development actions without importing CCGS slash-command ceremony or turning OGS into a general task manager.
+
+**Architecture:** This plan is refined by OpenSpec change `catch-up-workflow-skill-catalog`. The markdown file is the human-facing research index; the canonical refined implementation contract lives in the OpenSpec proposal, design, requirements, and tasks listed below.
+
+**Tech Stack:** TypeScript, NodeNext, npm package assets, Vitest, OpenSpec, Truthmark repository-truth validation.
+
+---
+
+## Gap Summary
+
+Open Game Studio has 13 workflow shortcuts while CCGS exposes 73 skills across onboarding, design, QA, testing, release, sprint, team, localization, hotfix, and review workflows.
+
+Current comparison baseline:
+- Open Game Studio: 20 roles, 13 workflow prompt shortcuts, 13 templates, 12 engine-reference files, TypeScript CLI/package, Codex-native run path, validation gate.
+- Claude Code Game Studios: 49 agents, 73 skills, 40 templates, 46 engine-reference files, richer authored specialist prompts and skill/testing framework.
+- Explicitly ignored/deferred for Open Game Studio: telemetry, planner/next, parallel orchestration, hard output-ownership enforcement, hosted service/daemon/background controller, hidden memory/checkpoints, non-Codex runtime replacements, mandatory heavyweight lifecycle.
+
+
+## OpenSpec Refinement
+
+- Change: `openspec/changes/catch-up-workflow-skill-catalog/`
+- Proposal: `openspec/changes/catch-up-workflow-skill-catalog/proposal.md`
+- Design: `openspec/changes/catch-up-workflow-skill-catalog/design.md`
+- Requirements: `openspec/changes/catch-up-workflow-skill-catalog/specs/codex-studio-workflow-catalog/spec.md`
+- Tasks: `openspec/changes/catch-up-workflow-skill-catalog/tasks.md`
+
+## Product Boundary Check
+
+- Mission improvement: Expand workflow coverage into a curated Codex-native catalog of game-development actions without importing CCGS slash-command ceremony or turning OGS into a general task manager.
+- In-scope surfaces: `src/workflows.ts`, `src/cli.ts`, `src/templates.ts`, `src/projects.ts`, `src/validation.ts`, `tests/functionality-gap-pass.test.ts`, `tests/cli-prompt-surface.test.ts`, `tests/project-workflow.test.ts`, `templates/`
+- Lightweight mode preserved: yes; additions are opt-in/discoverable and selected by relevance.
+- Codex-native preserved: yes; no `.claude/**` clone, no hosted runtime, no daemon.
+- Reviewable local outputs: OpenSpec artifacts, source diffs, generated project files, package assets, validation output.
+- Explicitly excluded from this plan: telemetry, planner/next, parallel orchestration, hard ownership enforcement, hidden memory/checkpoints, non-Codex runtime replacement, mandatory heavyweight lifecycle.
+
+## Bite-Sized Implementation Tasks
+
+- [ ] Create a workflow taxonomy: onboarding/discovery, design/architecture, implementation planning, QA/testing, release/hotfix, localization/accessibility, and team coordination.
+- [ ] Add high-value workflow prompt shortcuts before low-value aliases: start/onboard, brainstorm, prototype, architecture-decision, architecture-review, create-epics, create-stories, sprint-plan, sprint-status, story-readiness, story-done, qa-plan, regression-suite, security-audit, perf-profile, release-checklist, hotfix, localization-plan.
+- [ ] Keep workflow output prompt-only unless an existing CLI surface already owns state changes.
+- [ ] Add tests for command help, workflow rendering, aliases, and project materialization.
+- [ ] Add focused failing tests before each implementation slice.
+- [ ] Implement the smallest code/asset changes to pass each focused test.
+- [ ] Update validation and package smoke coverage for every new generated or packaged surface.
+- [ ] Update routed Truthmark docs only for behavior that actually ships.
+- [ ] Run `git diff --check`, focused tests, `npm run validate`, and applicable Truthmark gates.
+
+## Verification Commands
+
+```bash
+openspec validate catch-up-workflow-skill-catalog --strict --json
+openspec status --change catch-up-workflow-skill-catalog --json
+git diff --check -- research/2026-06-17-catch-up-workflow-skill-catalog-plan.md openspec/changes/catch-up-workflow-skill-catalog
+npm run validate
+```
+
+## Notes For Implementers
+
+Do not treat CCGS parity as file-for-file cloning. Translate useful CCGS coverage into Open Game Studio's local, Codex-native, package-friendly boundary. Keep prompt depth selected and bounded.
diff --git a/src/agents.ts b/src/agents.ts
index 5892aeb..dd41245 100644
--- a/src/agents.ts
+++ b/src/agents.ts
@@ -4,7 +4,7 @@ import { guidanceConfigHash, type ProjectConfig } from "./config.js";
 import type { EngineConfigRegistry } from "./engines.js";
 import { engineReferenceProjectPath, selectedEngineReferencePrompts } from "./engine-reference.js";
 import { renderGeneratedSurfaceMetadata } from "./generated-surfaces.js";
-import { projectRoleIdsForEngine, rolePackages, studioRoleIds, type StudioRoleId } from "./roles.js";
+import { projectRoleIdsForEngine, renderRoleContractSections, rolePackages, studioRoleIds, type StudioRoleId } from "./roles.js";
 
 export type MaterializeAgentsInput = {
   projectRoot: string;
@@ -15,7 +15,17 @@ export type MaterializeAgentsInput = {
 export function validateBaseAgents(): string[] {
   return studioRoleIds.flatMap((role) => {
     const pkg = rolePackages[role];
-    return pkg.systemPrompt.trim() && pkg.expectedOutputs.length && pkg.reviewChecklist.length ? [] : [`Invalid role package ${role}`];
+    return pkg.systemPrompt.trim() &&
+      pkg.responsibilities.length &&
+      pkg.inputsToInspect.length &&
+      pkg.expectedOutputs.length &&
+      pkg.qualityGates.length &&
+      pkg.collaborationNotes.length &&
+      pkg.stopConditions.length &&
+      pkg.sharedFragments.length &&
+      pkg.reviewChecklist.length
+      ? []
+      : [`Invalid role package ${role}`];
   });
 }
 
@@ -106,6 +116,7 @@ export function renderProjectRolePrompt(role: StudioRoleId, config: ProjectConfi
     `Project: ${config.project.name}`,
     `Slug: ${config.project.slug}`,
     `Role: ${pkg.displayName}`,
+    `Context Strategy: ${pkg.contextStrategy}`,
     `Mode: ${config.project.mode}`,
     `Studio Mode: ${config.project.studio_mode}`,
     `Engine: ${engine.display_name} ${config.project.engine_version}`,
@@ -126,6 +137,8 @@ export function renderProjectRolePrompt(role: StudioRoleId, config: ProjectConfi
     "",
     pkg.systemPrompt,
     "",
+    renderRoleContractSections(pkg),
+    "",
     "## Engine Context",
     "",
     ...engine.codex_hints.map((hint) => `- ${hint}`),
@@ -165,8 +178,16 @@ export function projectRolePromptSourceInput(role: StudioRoleId, config: Project
   return {
     role,
     displayName: pkg.displayName,
+    contextStrategy: pkg.contextStrategy,
     systemPrompt: pkg.systemPrompt,
+    responsibilities: pkg.responsibilities,
+    inputsToInspect: pkg.inputsToInspect,
     expectedOutputs: pkg.expectedOutputs,
+    outputSchema: pkg.outputSchema,
+    qualityGates: pkg.qualityGates,
+    collaborationNotes: pkg.collaborationNotes,
+    stopConditions: pkg.stopConditions,
+    sharedFragments: pkg.sharedFragments,
     reviewChecklist: pkg.reviewChecklist,
     handoffTemplate: pkg.handoffTemplate,
     engineDisplayName: engine.display_name,
diff --git a/src/behavioral-evaluation.ts b/src/behavioral-evaluation.ts
new file mode 100644
index 0000000..c4636cd
--- /dev/null
+++ b/src/behavioral-evaluation.ts
@@ -0,0 +1,213 @@
+import { createCodexStudioSession, type CodexStudioPhase } from "./codex-session.js";
+import { renderCodexPrompt } from "./codex-prompts.js";
+import { renderWorkflowPrompt, workflowRegistry, type WorkflowId } from "./workflows.js";
+import { rolePackages, type StudioRoleId } from "./roles.js";
+import type { TemplateId } from "./templates.js";
+
+export type BehavioralEvaluationTarget =
+  | { kind: "role"; role: StudioRoleId; phase: CodexStudioPhase; objective: string; contextFiles?: string[] }
+  | { kind: "workflow"; workflow: WorkflowId };
+
+export type BehavioralEvaluationScenario = {
+  id: string;
+  description: string;
+  target: BehavioralEvaluationTarget;
+  requiredPhrases: string[];
+  forbiddenPhrases: string[];
+  expectedContextCategories: string[];
+  requiredTemplateIds?: TemplateId[];
+  forbiddenTemplateIds?: TemplateId[];
+  maxPromptLength?: number;
+};
+
+export type BehavioralEvaluationResult = {
+  id: string;
+  status: "pass" | "fail";
+  prompt: string;
+  promptLength: number;
+  localDeterministic: true;
+  usesHostedEvaluator: false;
+  usesLlmCall: false;
+  missingRequiredPhrases: string[];
+  presentForbiddenPhrases: string[];
+  missingContextCategories: string[];
+  missingTemplateIds: TemplateId[];
+  presentForbiddenTemplateIds: TemplateId[];
+};
+
+const defaultForbiddenDrift = ["CODEX.md", "telemetry", "parallel orchestration", "hidden memory", "hosted service", "planner/next"];
+
+function withDefaultForbidden(extra: string[] = []): string[] {
+  return [...new Set([...defaultForbiddenDrift, ...extra])];
+}
+
+export const behavioralEvaluationScenarios: BehavioralEvaluationScenario[] = [
+  {
+    id: "role.gameplay-programmer.contract",
+    description: "Gameplay programmer prompts require implementation handoff fields, verification evidence, and bounded Codex-native edit guidance.",
+    target: {
+      kind: "role",
+      role: "gameplay-programmer",
+      phase: "implement",
+      objective: "Implement a bounded playable movement change.",
+      contextFiles: ["AGENTS.md", ".codex/studio.json", "source/project-game/player.gd"]
+    },
+    requiredPhrases: ["Role: Gameplay Programmer", "Context Strategy: focused", "## Responsibilities", "Changed files", "Verification evidence", "File Edits: allowed"],
+    forbiddenPhrases: withDefaultForbidden(["Template: market_analysis"]),
+    expectedContextCategories: ["project-instructions", "studio-state", "source-artifact", "role-contract", "output-contract"],
+    maxPromptLength: 15000
+  },
+  {
+    id: "role.qa-playtester.contract",
+    description: "QA playtester prompts require reproducible issue evidence, severity, expected/actual result fields, and no implementation-only drift.",
+    target: {
+      kind: "role",
+      role: "qa-playtester",
+      phase: "review",
+      objective: "Review current playtest blockers and warnings.",
+      contextFiles: ["AGENTS.md", ".codex/studio.json", "documentation/design/gdd.md"]
+    },
+    requiredPhrases: ["Role: QA Playtester", "Issue ID", "Severity", "Reproduction steps", "Expected result", "Actual result", "File Edits: not allowed"],
+    forbiddenPhrases: withDefaultForbidden(["danger-full-access", "Template: release_notes"]),
+    expectedContextCategories: ["project-instructions", "studio-state", "project-docs", "role-contract", "output-contract"],
+    maxPromptLength: 15000
+  },
+  {
+    id: "role.release-manager.contract",
+    description: "Release manager prompts require release decision structure, blocker separation, validation evidence, and release-readiness guidance.",
+    target: {
+      kind: "role",
+      role: "release-manager",
+      phase: "ship",
+      objective: "Assess whether the milestone is ready to ship.",
+      contextFiles: ["AGENTS.md", ".codex/studio.json", "documentation/production/timeline.md"]
+    },
+    requiredPhrases: ["Role: Release Manager", "Release decision", "Blocking issues", "Validation evidence", "Rollback notes", "release blockers"],
+    forbiddenPhrases: withDefaultForbidden(["Template: analytics_setup"]),
+    expectedContextCategories: ["project-instructions", "studio-state", "project-docs", "role-contract", "output-contract"],
+    maxPromptLength: 15000
+  },
+  {
+    id: "workflow.ship-check.release-readiness",
+    description: "Ship-check workflow prompts must select release templates, timeline context, and release-manager evidence without pulling unrelated market or analytics templates.",
+    target: { kind: "workflow", workflow: "ship-check" },
+    requiredPhrases: ["Role: Release Manager", workflowRegistry["ship-check"].objective, "Blocking issues", "Validation evidence", "documentation/production/timeline.md"],
+    forbiddenPhrases: withDefaultForbidden(["Template: market_analysis", "Template: analytics_setup"]),
+    expectedContextCategories: ["project-instructions", "studio-state", "workflow-file", "project-docs", "templates", "role-contract", "output-contract"],
+    requiredTemplateIds: ["ship_check", "release_notes", "risk_register"],
+    forbiddenTemplateIds: ["market_analysis", "analytics_setup"],
+    maxPromptLength: 15000
+  },
+  {
+    id: "workflow.playtest.issue-evidence",
+    description: "Playtest workflow prompts must select playtest evidence templates and QA issue contract fields without mutating project state.",
+    target: { kind: "workflow", workflow: "playtest" },
+    requiredPhrases: ["Role: QA Playtester", workflowRegistry.playtest.objective, "Reproduction steps", "Evidence", "File Edits: not allowed"],
+    forbiddenPhrases: withDefaultForbidden(["Template: release_notes", "danger-full-access"]),
+    expectedContextCategories: ["project-instructions", "studio-state", "workflow-file", "templates", "role-contract", "output-contract"],
+    requiredTemplateIds: ["playtest_report", "test_evidence"],
+    forbiddenTemplateIds: ["release_notes", "market_analysis"],
+    maxPromptLength: 15000
+  },
+  {
+    id: "workflow.market-analysis.positioning",
+    description: "Market-analysis workflow prompts must select market and pitch material while avoiding analytics-only and release-only templates.",
+    target: { kind: "workflow", workflow: "market-analysis" },
+    requiredPhrases: ["Role: Market Analyst", workflowRegistry["market-analysis"].objective, "resources/market-research/market-overview.md", "Expected Outputs"],
+    forbiddenPhrases: withDefaultForbidden(["Template: analytics_setup", "Template: release_notes"]),
+    expectedContextCategories: ["project-instructions", "studio-state", "workflow-file", "project-docs", "templates", "role-contract"],
+    requiredTemplateIds: ["market_analysis", "pitch_document"],
+    forbiddenTemplateIds: ["analytics_setup", "release_notes"],
+    maxPromptLength: 15000
+  }
+];
+
+function renderScenarioPrompt(scenario: BehavioralEvaluationScenario, options: { projectRoot?: string } = {}): string {
+  if (scenario.target.kind === "workflow") {
+    const definition = workflowRegistry[scenario.target.workflow];
+    if (options.projectRoot) return renderWorkflowPrompt(options.projectRoot, scenario.target.workflow);
+    return renderCodexPrompt(
+      createCodexStudioSession({
+        projectRoot: options.projectRoot ?? process.cwd(),
+        role: definition.role,
+        objective: definition.objective,
+        phase: definition.phase,
+        engine: "godot",
+        contextFiles: definition.contextFiles
+      })
+    );
+  }
+
+  return renderCodexPrompt(
+    createCodexStudioSession({
+      projectRoot: options.projectRoot ?? process.cwd(),
+      role: scenario.target.role,
+      objective: scenario.target.objective,
+      phase: scenario.target.phase,
+      engine: "godot",
+      contextFiles: scenario.target.contextFiles
+    })
+  );
+}
+
+function actualContextCategories(scenario: BehavioralEvaluationScenario, prompt: string): string[] {
+  const categories = new Set<string>();
+  if (prompt.includes("AGENTS.md")) categories.add("project-instructions");
+  if (prompt.includes(".codex/studio.json")) categories.add("studio-state");
+  if (prompt.includes(".codex/workflows/")) categories.add("workflow-file");
+  if (/documentation\/|resources\//.test(prompt)) categories.add("project-docs");
+  if (/source\//.test(prompt)) categories.add("source-artifact");
+  if (prompt.includes("docs/engine-reference/")) categories.add("engine-reference");
+  if (prompt.includes("## Workflow Templates") || (scenario.target.kind === "workflow" && (workflowRegistry[scenario.target.workflow].templateIds?.length ?? 0) > 0)) categories.add("templates");
+  if (prompt.includes("## Responsibilities") && prompt.includes("## Quality Gates")) categories.add("role-contract");
+  if (prompt.includes("## Output Format") || prompt.includes("## Expected Outputs")) categories.add("output-contract");
+  return [...categories];
+}
+
+function templateToken(id: TemplateId): string {
+  return `Template: ${id}`;
+}
+
+function containsForbiddenDrift(prompt: string, phrase: string): boolean {
+  const haystack = prompt.toLowerCase();
+  const needle = phrase.toLowerCase();
+  let index = haystack.indexOf(needle);
+  while (index !== -1) {
+    const window = haystack.slice(Math.max(0, index - 90), Math.min(haystack.length, index + needle.length + 90));
+    const negated = /do not|must not|not exposed|without|forbidden|excluded|absent/.test(window);
+    if (!negated) return true;
+    index = haystack.indexOf(needle, index + needle.length);
+  }
+  return false;
+}
+
+export function evaluateBehavioralScenario(scenario: BehavioralEvaluationScenario, options: { projectRoot?: string } = {}): BehavioralEvaluationResult {
+  const prompt = renderScenarioPrompt(scenario, options);
+  const categories = actualContextCategories(scenario, prompt);
+  const missingRequiredPhrases = scenario.requiredPhrases.filter((phrase) => !prompt.includes(phrase));
+  const presentForbiddenPhrases = scenario.forbiddenPhrases.filter((phrase) => containsForbiddenDrift(prompt, phrase));
+  const missingContextCategories = scenario.expectedContextCategories.filter((category) => !categories.includes(category));
+  const missingTemplateIds = (scenario.requiredTemplateIds ?? []).filter((id) => options.projectRoot && !prompt.includes(templateToken(id)));
+  const presentForbiddenTemplateIds = (scenario.forbiddenTemplateIds ?? []).filter((id) => prompt.includes(templateToken(id)));
+  const tooLong = prompt.length > (scenario.maxPromptLength ?? 15000);
+  const status = missingRequiredPhrases.length || presentForbiddenPhrases.length || missingContextCategories.length || missingTemplateIds.length || presentForbiddenTemplateIds.length || tooLong ? "fail" : "pass";
+
+  return {
+    id: scenario.id,
+    status,
+    prompt,
+    promptLength: prompt.length,
+    localDeterministic: true,
+    usesHostedEvaluator: false,
+    usesLlmCall: false,
+    missingRequiredPhrases,
+    presentForbiddenPhrases,
+    missingContextCategories,
+    missingTemplateIds,
+    presentForbiddenTemplateIds
+  };
+}
+
+export function runBehavioralEvaluations(options: { projectRoot?: string } = {}): BehavioralEvaluationResult[] {
+  return behavioralEvaluationScenarios.map((scenario) => evaluateBehavioralScenario(scenario, options));
+}
diff --git a/src/cli.ts b/src/cli.ts
index 2bbfb7e..150bd95 100644
--- a/src/cli.ts
+++ b/src/cli.ts
@@ -17,7 +17,7 @@ import { runValidation } from "./validation.js";
 import { executeRunLifecycle, prepareRun } from "./runner.js";
 import { checkCodexAvailability } from "./codex-runtime.js";
 import { createTask, executeTaskRun, readTaskStore, resolveTaskProject } from "./tasks.js";
-import { renderWorkflowPrompt, workflowRegistry, type WorkflowId } from "./workflows.js";
+import { renderWorkflowPrompt, workflowAliases, workflowRegistry, type WorkflowId } from "./workflows.js";
 import { isStudioRoleId, unknownStudioRoleMessage } from "./roles.js";
 import type { ProjectStage, StudioMode } from "./studio-policy.js";
 
@@ -122,16 +122,19 @@ program
   });
 
 const templates = program.command("templates").description("Discover templates");
-templates.command("list").description("List template IDs").action(() => {
-  for (const info of listTemplates()) console.log(`${info.id}\t${info.category}\t${info.path}`);
+templates.command("list").description("List template IDs").option("--project <path>", "project path for local templates").action((opts) => {
+  const projectRoot = opts.project ? resolveTaskProject(opts.project) : undefined;
+  for (const info of listTemplates(projectRoot)) console.log(`${info.id}\t${info.category}\t${info.path}`);
 });
 templates
   .command("show")
   .description("Show a template")
   .argument("<template-id>")
-  .action((id: TemplateId) => {
-    if (!templateRegistry[id]) throw new Error(`Unknown template "${id}"`);
-    console.log(formatTemplateShow(id));
+  .option("--project <path>", "project path for local templates")
+  .action((id: string, opts) => {
+    const projectRoot = opts.project ? resolveTaskProject(opts.project) : undefined;
+    if (!templateRegistry[id as TemplateId] && !projectRoot) throw new Error(`Unknown template "${id}"`);
+    console.log(formatTemplateShow(id, projectRoot ? { projectRoot } : {}));
   });
 
 const approval = program.command("approval").description("Manage auditable studio approvals");
@@ -339,11 +342,19 @@ task
     if (result.lifecycle?.finalStatus === "blocked") process.exitCode = 1;
   });
 
-function renderWorkflowCommand(workflow: WorkflowId, opts: { project: string }): void {
+function renderWorkflowCommand(workflow: string, opts: { project: string }): void {
   const projectRoot = resolveTaskProject(opts.project);
   console.log(renderWorkflowPrompt(projectRoot, workflow));
 }
 
+program
+  .command("workflow")
+  .description("Render a built-in or project-local workflow prompt by id")
+  .argument("<workflow-id>")
+  .requiredOption("--project <path>", "project path")
+  .option("--dry-run", "render prompt without launching Codex")
+  .action((workflow: string, opts) => renderWorkflowCommand(workflow, opts));
+
 function addWorkflowCommand(name: "review" | "ship-check"): void {
   program
     .command(name)
@@ -353,13 +364,15 @@ function addWorkflowCommand(name: "review" | "ship-check"): void {
     .action((opts) => renderWorkflowCommand(name, opts));
 }
 
-for (const workflow of Object.values(workflowRegistry).filter((entry) => entry.cliAlias)) {
-  program
-    .command(workflow.cliAlias!)
-    .description(`Render the ${workflow.id} workflow prompt`)
-    .requiredOption("--project <path>", "project path")
-    .option("--dry-run", "render prompt without launching Codex")
-    .action((opts) => renderWorkflowCommand(workflow.id, opts));
+for (const workflow of Object.values(workflowRegistry)) {
+  for (const alias of workflowAliases(workflow)) {
+    program
+      .command(alias)
+      .description(`Render the ${workflow.id} workflow prompt`)
+      .requiredOption("--project <path>", "project path")
+      .option("--dry-run", "render prompt without launching Codex")
+      .action((opts) => renderWorkflowCommand(workflow.id, opts));
+  }
 }
 addWorkflowCommand("review");
 addWorkflowCommand("ship-check");
diff --git a/src/codex-prompts.ts b/src/codex-prompts.ts
index 0ca7210..0fabb8b 100644
--- a/src/codex-prompts.ts
+++ b/src/codex-prompts.ts
@@ -1,4 +1,4 @@
-import { rolePackages } from "./roles.js";
+import { renderRoleContractSections, rolePackages } from "./roles.js";
 import type { CodexStudioSession } from "./codex-session.js";
 import { loadEngineConfigs } from "./engines.js";
 import { packageAssetPath } from "./paths.js";
@@ -29,6 +29,7 @@ export function renderCodexPrompt(session: CodexStudioSession): string {
     "",
     `Role: ${role.displayName}`,
     `Role ID: ${role.id}`,
+    `Context Strategy: ${role.contextStrategy}`,
     `Phase: ${session.phase}`,
     `Project Root: ${session.projectRoot}`,
     `Objective: ${session.objective}`,
@@ -42,6 +43,8 @@ export function renderCodexPrompt(session: CodexStudioSession): string {
     "## Role Contract",
     role.systemPrompt,
     "",
+    renderRoleContractSections(role),
+    "",
     "## Engine Context",
     engineSection,
     "",
diff --git a/src/config.ts b/src/config.ts
index 34b4c30..b5858aa 100644
--- a/src/config.ts
+++ b/src/config.ts
@@ -59,18 +59,53 @@ export function slugify(value: string): string {
 export function activeAgentsForMode(mode: ProjectMode): AgentName[] {
   const always: AgentName[] = ["studio-orchestrator", "producer", "market-analyst", "data-scientist"];
   const byMode: Record<ProjectMode, AgentName[]> = {
-    design: ["creative-director", "senior-game-designer", "game-designer", "narrative-designer", "senior-game-artist", "ui-ux-designer"],
-    prototype: ["senior-game-designer", "game-designer", "game-feel-designer", "gameplay-programmer", "qa-playtester"],
+    design: [
+      "creative-director",
+      "senior-game-designer",
+      "game-designer",
+      "narrative-designer",
+      "writer",
+      "world-builder",
+      "level-designer",
+      "systems-designer",
+      "economy-designer",
+      "audio-director",
+      "senior-game-artist",
+      "ui-ux-designer",
+      "accessibility-specialist"
+    ],
+    prototype: [
+      "senior-game-designer",
+      "game-designer",
+      "systems-designer",
+      "level-designer",
+      "game-feel-designer",
+      "gameplay-programmer",
+      "ui-programmer",
+      "sound-designer",
+      "qa-playtester",
+      "accessibility-specialist"
+    ],
     development: [
+      "technical-director",
       "senior-game-designer",
       "game-designer",
       "game-feel-designer",
       "gameplay-programmer",
       "engine-programmer",
       "tools-programmer",
+      "ai-programmer",
+      "network-programmer",
+      "ui-programmer",
+      "devops-engineer",
+      "security-engineer",
+      "performance-analyst",
       "qa-playtester",
       "senior-game-artist",
       "technical-artist",
+      "localization-lead",
+      "live-ops-designer",
+      "community-manager",
       "ui-ux-designer",
       "release-manager"
     ]
diff --git a/src/customization.ts b/src/customization.ts
new file mode 100644
index 0000000..2d10266
--- /dev/null
+++ b/src/customization.ts
@@ -0,0 +1,278 @@
+import { existsSync, mkdirSync, readFileSync, writeFileSync } from "node:fs";
+import path from "node:path";
+import { z } from "zod";
+import { studioRoleIds, type StudioRoleId } from "./roles.js";
+import type { CodexStudioPhase } from "./codex-session.js";
+
+const customIdSchema = z.string().regex(/^custom-[a-z0-9][a-z0-9-]*$/, "custom ids must start with custom- and use lowercase letters, numbers, and hyphens");
+const relativePathSchema = z.string().min(1);
+
+export const customRoleSchema = z.object({
+  id: z.string().min(1),
+  displayName: z.string().min(1),
+  promptFile: relativePathSchema,
+  contextStrategy: z.enum(["minimal", "focused", "broad"]),
+  phase: z.enum(["plan", "implement", "review", "ship"]).default("plan"),
+  expectedOutputs: z.array(z.string().min(1)).min(1),
+  reviewChecklist: z.array(z.string().min(1)).min(1),
+  contextFiles: z.array(relativePathSchema).default([])
+});
+
+export const customTemplateSchema = z.object({
+  id: z.string().min(1),
+  category: z.string().min(1),
+  path: relativePathSchema,
+  description: z.string().min(1),
+  roles: z.array(z.string().min(1)).min(1),
+  workflows: z.array(z.string().min(1)).min(1),
+  tags: z.array(z.string().min(1)).default([]),
+  requiredSections: z.array(z.string().min(1)).default([])
+});
+
+export const customWorkflowSchema = z.object({
+  id: z.string().min(1),
+  role: z.string().min(1),
+  phase: z.enum(["plan", "implement", "review", "ship"]),
+  objective: z.string().min(1),
+  file: relativePathSchema,
+  contextFiles: z.array(relativePathSchema).default([]),
+  templateIds: z.array(z.string().min(1)).default([]),
+  aliases: z.array(z.string().min(1)).default([])
+});
+
+export const projectCustomizationSchema = z.object({
+  schemaVersion: z.literal(1),
+  policy: z.object({ merge: z.literal("extend-only") }).default({ merge: "extend-only" }),
+  roles: z.array(customRoleSchema).default([]),
+  workflows: z.array(customWorkflowSchema).default([]),
+  templates: z.array(customTemplateSchema).default([])
+});
+
+export type CustomRoleDefinition = z.infer<typeof customRoleSchema>;
+export type CustomWorkflowDefinition = z.infer<typeof customWorkflowSchema>;
+export type CustomTemplateDefinition = z.infer<typeof customTemplateSchema> & { custom: true };
+export type ProjectCustomization = z.infer<typeof projectCustomizationSchema>;
+
+export type CustomizationDiagnostic = {
+  id: string;
+  status: "pass" | "fail";
+  message: string;
+  path?: string;
+};
+
+export function customizationConfigPath(projectRoot: string): string {
+  return path.join(projectRoot, ".codex", "studio", "config.json");
+}
+
+export function defaultProjectCustomization(): ProjectCustomization {
+  return { schemaVersion: 1, policy: { merge: "extend-only" }, roles: [], workflows: [], templates: [] };
+}
+
+export function writeDefaultProjectCustomization(projectRoot: string): void {
+  const configPath = customizationConfigPath(projectRoot);
+  mkdirSync(path.dirname(configPath), { recursive: true });
+  if (!existsSync(configPath)) writeFileSync(configPath, `${JSON.stringify(defaultProjectCustomization(), null, 2)}\n`);
+}
+
+function parseCustomizationFile(projectRoot: string): { ok: true; value: ProjectCustomization } | { ok: false; error: string; file: string } {
+  const file = customizationConfigPath(projectRoot);
+  if (!existsSync(file)) return { ok: true, value: defaultProjectCustomization() };
+  try {
+    return { ok: true, value: projectCustomizationSchema.parse(JSON.parse(readFileSync(file, "utf8"))) };
+  } catch (error) {
+    return { ok: false, error: (error as Error).message, file };
+  }
+}
+
+export function readProjectCustomization(projectRoot: string): ProjectCustomization {
+  const parsed = parseCustomizationFile(projectRoot);
+  if (!parsed.ok) throw new Error(`Invalid Open Game Studio customization config: ${parsed.error}`);
+  return parsed.value;
+}
+
+function hasDuplicate(values: string[]): string | undefined {
+  const seen = new Set<string>();
+  for (const value of values) {
+    if (seen.has(value)) return value;
+    seen.add(value);
+  }
+  return undefined;
+}
+
+export function projectRelativePath(projectRoot: string, relativePath: string): { ok: true; full: string; display: string } | { ok: false; error: string } {
+  if (/[\u0000-\u001f\u007f]/.test(relativePath)) return { ok: false, error: "path contains control characters" };
+  if (path.isAbsolute(relativePath)) return { ok: false, error: "path must be relative to the project root" };
+  const normalized = path.normalize(relativePath).split(path.sep).join("/");
+  if (normalized === "." || normalized.startsWith("../") || normalized === "..") return { ok: false, error: "path cannot escape the project root" };
+  if (normalized.startsWith(".git/") || normalized === ".git") return { ok: false, error: "path cannot target .git" };
+  const full = path.resolve(projectRoot, normalized);
+  const root = path.resolve(projectRoot);
+  if (full !== root && !full.startsWith(`${root}${path.sep}`)) return { ok: false, error: "path cannot escape the project root" };
+  return { ok: true, full, display: normalized };
+}
+
+function sectionHasContent(body: string, section: string): boolean {
+  const escaped = section.replace(/[.*+?^${}()|[\]\\]/g, "\\$&");
+  const match = new RegExp(`^${escaped}\\s*$`, "m").exec(body);
+  if (!match) return false;
+  const start = match.index + match[0].length;
+  const rest = body.slice(start);
+  const nextHeading = rest.search(/^#/m);
+  return (nextHeading === -1 ? rest : rest.slice(0, nextHeading)).trim().length > 0;
+}
+
+export function validateProjectCustomization(
+  projectRoot: string,
+  options: { builtInWorkflowIds?: string[]; builtInTemplateIds?: string[] } = {}
+): CustomizationDiagnostic[] {
+  const file = customizationConfigPath(projectRoot);
+  const parsed = parseCustomizationFile(projectRoot);
+  if (!parsed.ok) return [{ id: "codex.customization.config", status: "fail", message: `customization config invalid: ${parsed.error}`, path: parsed.file }];
+  const config = parsed.value;
+  const diagnostics: CustomizationDiagnostic[] = [
+    { id: "codex.customization.config", status: "pass", message: "customization config schema-readable", path: file }
+  ];
+  const builtInRoles = new Set<string>(studioRoleIds);
+  const builtInWorkflows = new Set(options.builtInWorkflowIds ?? []);
+  const builtInTemplates = new Set(options.builtInTemplateIds ?? []);
+  const roleIds = config.roles.map((role) => role.id);
+  const workflowIds = config.workflows.map((workflow) => workflow.id);
+  const templateIds = config.templates.map((template) => template.id);
+  for (const [kind, duplicate] of [
+    ["role", hasDuplicate(roleIds)],
+    ["workflow", hasDuplicate(workflowIds)],
+    ["template", hasDuplicate(templateIds)]
+  ] as const) {
+    if (duplicate) diagnostics.push({ id: `codex.customization.${kind}.${duplicate}`, status: "fail", message: `duplicate custom ${kind} id ${duplicate}`, path: file });
+  }
+
+  const customRoleIds = new Set(roleIds);
+  const customWorkflowIds = new Set(workflowIds);
+  const customTemplateIds = new Set(templateIds);
+
+  for (const role of config.roles) {
+    const problems: string[] = [];
+    if (!customIdSchema.safeParse(role.id).success) problems.push("role id must start with custom- and use lowercase letters, numbers, and hyphens");
+    if (builtInRoles.has(role.id)) problems.push("role id conflicts with a built-in role; extend-only packs cannot override built-ins");
+    const prompt = projectRelativePath(projectRoot, role.promptFile);
+    if (!prompt.ok) problems.push(`promptFile ${prompt.error}`);
+    else if (!existsSync(prompt.full)) problems.push(`promptFile missing: ${prompt.display}`);
+    for (const contextFile of role.contextFiles) {
+      const context = projectRelativePath(projectRoot, contextFile);
+      if (!context.ok) problems.push(`context file ${contextFile}: ${context.error}`);
+    }
+    diagnostics.push({ id: `codex.customization.role.${role.id}`, status: problems.length ? "fail" : "pass", message: problems.length ? problems.join("; ") : `${role.id} custom role is valid`, path: problems.length ? file : prompt.ok ? prompt.full : file });
+  }
+
+  for (const template of config.templates) {
+    const problems: string[] = [];
+    if (!customIdSchema.safeParse(template.id).success) problems.push("template id must start with custom- and use lowercase letters, numbers, and hyphens");
+    if (builtInTemplates.has(template.id)) problems.push("template id conflicts with a built-in template; extend-only packs cannot override built-ins");
+    const templatePath = projectRelativePath(projectRoot, template.path);
+    if (!templatePath.ok) problems.push(`template path ${templatePath.error}`);
+    else if (!existsSync(templatePath.full)) problems.push(`template file missing: ${templatePath.display}`);
+    if (templatePath.ok && existsSync(templatePath.full)) {
+      const body = readFileSync(templatePath.full, "utf8");
+      for (const section of template.requiredSections) {
+        if (!sectionHasContent(body, section)) problems.push(`template missing non-empty ${section}`);
+      }
+    }
+    for (const role of template.roles) {
+      if (!builtInRoles.has(role) && !customRoleIds.has(role)) problems.push(`template references unknown role ${role}`);
+    }
+    for (const workflow of template.workflows) {
+      if (!builtInWorkflows.has(workflow) && !customWorkflowIds.has(workflow)) problems.push(`template references unknown workflow ${workflow}`);
+    }
+    diagnostics.push({ id: `codex.customization.template.${template.id}`, status: problems.length ? "fail" : "pass", message: problems.length ? problems.join("; ") : `${template.id} custom template is valid`, path: templatePath.ok ? templatePath.full : file });
+  }
+
+  for (const workflow of config.workflows) {
+    const problems: string[] = [];
+    if (!customIdSchema.safeParse(workflow.id).success) problems.push("workflow id must start with custom- and use lowercase letters, numbers, and hyphens");
+    if (builtInWorkflows.has(workflow.id)) problems.push("workflow id conflicts with a built-in workflow; extend-only packs cannot override built-ins");
+    if (!builtInRoles.has(workflow.role) && !customRoleIds.has(workflow.role)) problems.push(`workflow references unknown role ${workflow.role}`);
+    const workflowPath = projectRelativePath(projectRoot, workflow.file);
+    if (!workflowPath.ok) problems.push(`workflow file ${workflowPath.error}`);
+    for (const contextFile of workflow.contextFiles) {
+      const context = projectRelativePath(projectRoot, contextFile);
+      if (!context.ok) problems.push(`context file ${contextFile}: ${context.error}`);
+    }
+    for (const templateId of workflow.templateIds) {
+      if (!builtInTemplates.has(templateId) && !customTemplateIds.has(templateId)) problems.push(`workflow references unknown template ${templateId}`);
+    }
+    diagnostics.push({ id: `codex.customization.workflow.${workflow.id}`, status: problems.length ? "fail" : "pass", message: problems.length ? problems.join("; ") : `${workflow.id} custom workflow is valid`, path: workflowPath.ok ? workflowPath.full : file });
+  }
+
+  return diagnostics;
+}
+
+export function customizationIsValid(projectRoot: string, options: { builtInWorkflowIds?: string[]; builtInTemplateIds?: string[] } = {}): boolean {
+  return validateProjectCustomization(projectRoot, options).every((diagnostic) => diagnostic.status === "pass");
+}
+
+export function findCustomRole(projectRoot: string, roleId: string): CustomRoleDefinition | undefined {
+  const config = readProjectCustomization(projectRoot);
+  return config.roles.find((role) => role.id === roleId);
+}
+
+export function findCustomWorkflow(projectRoot: string, workflowId: string): CustomWorkflowDefinition | undefined {
+  const config = readProjectCustomization(projectRoot);
+  return config.workflows.find((workflow) => workflow.id === workflowId || workflow.aliases.includes(workflowId));
+}
+
+export function findCustomTemplate(projectRoot: string, templateId: string): CustomTemplateDefinition | undefined {
+  const config = readProjectCustomization(projectRoot);
+  const template = config.templates.find((candidate) => candidate.id === templateId);
+  return template ? { ...template, custom: true } : undefined;
+}
+
+export function listCustomTemplates(projectRoot: string): CustomTemplateDefinition[] {
+  return readProjectCustomization(projectRoot).templates.map((template) => ({ ...template, custom: true }));
+}
+
+export function readCustomTemplate(projectRoot: string, templateId: string): string {
+  const template = findCustomTemplate(projectRoot, templateId);
+  if (!template) throw new Error(`Unknown custom template "${templateId}"`);
+  const safe = projectRelativePath(projectRoot, template.path);
+  if (!safe.ok) throw new Error(`Unsafe custom template path for ${templateId}: ${safe.error}`);
+  return readFileSync(safe.full, "utf8");
+}
+
+export function customTemplateIdsForRole(projectRoot: string, roleId: string, task: string): string[] {
+  const lower = task.toLowerCase();
+  return listCustomTemplates(projectRoot)
+    .filter((template) => template.roles.includes(roleId) || template.tags.some((tag) => lower.includes(tag.toLowerCase())))
+    .map((template) => template.id);
+}
+
+export function renderCustomRolePrompt(projectRoot: string, role: CustomRoleDefinition): string {
+  const promptPath = projectRelativePath(projectRoot, role.promptFile);
+  const prompt = promptPath.ok && existsSync(promptPath.full) ? readFileSync(promptPath.full, "utf8").trim() : "Custom prompt file missing.";
+  return [
+    `# Project Custom Role Prompt: ${role.promptFile}`,
+    "",
+    `Role: ${role.displayName}`,
+    `Role ID: ${role.id}`,
+    `Context Strategy: ${role.contextStrategy}`,
+    "",
+    "## Role Instructions",
+    "",
+    prompt,
+    "",
+    "## Expected Outputs",
+    "",
+    ...role.expectedOutputs.map((item) => `- ${item}`),
+    "",
+    "## Review Checklist",
+    "",
+    ...role.reviewChecklist.map((item) => `- ${item}`)
+  ].join("\n");
+}
+
+export function customPhaseForRun(role: CustomRoleDefinition): CodexStudioPhase {
+  return role.phase;
+}
+
+export function isBuiltInRole(role: string): role is StudioRoleId {
+  return (studioRoleIds as readonly string[]).includes(role);
+}
diff --git a/src/engine-reference.ts b/src/engine-reference.ts
index 891457a..9c10de2 100644
--- a/src/engine-reference.ts
+++ b/src/engine-reference.ts
@@ -10,6 +10,7 @@ export type EngineReferencePrompt = {
   path: string;
   reason: string;
   roles?: StudioRoleId[];
+  keywords?: string[];
   required: boolean;
 };
 
@@ -18,11 +19,12 @@ export type EngineReferencePack = {
   packageRoot: string;
   projectRoot: string;
   requiredFiles: string[];
+  moduleFiles: string[];
   pluginFiles: string[];
   specialistFiles: string[];
   promptReferences: EngineReferencePrompt[];
   validation: {
-    requiredMetadata: ["reviewer", "date", "source-link"];
+    requiredMetadata: ["reviewer", "date", "source-link", "engine", "version-reviewed", "tags", "roles", "workflows"];
   };
   packageSmokeFiles: string[];
   projectPath(file: string): string;
@@ -36,25 +38,79 @@ export type EngineReferenceCheck = {
 };
 
 const programmingRoles: StudioRoleId[] = ["gameplay-programmer", "engine-programmer", "tools-programmer", "technical-artist"];
+const qaRoles: StudioRoleId[] = ["qa-playtester", "performance-analyst"];
+const designRoles: StudioRoleId[] = ["game-designer", "senior-game-designer", "game-feel-designer", "systems-designer", "level-designer"];
+const artRoles: StudioRoleId[] = ["senior-game-artist", "technical-artist", "ui-ux-designer"];
+const audioRoles: StudioRoleId[] = ["audio-director", "sound-designer"];
+
+const moduleFiles = [
+  "modules/animation.md",
+  "modules/audio.md",
+  "modules/input.md",
+  "modules/navigation.md",
+  "modules/networking.md",
+  "modules/physics.md",
+  "modules/rendering.md",
+  "modules/ui.md"
+];
+
+const moduleReferences: EngineReferencePrompt[] = [
+  { path: "modules/animation.md", reason: "animation systems, state machines, blend trees, and timing guidance", roles: [...programmingRoles, ...artRoles, ...designRoles], keywords: ["animation", "animator", "blend", "state machine", "montage", "timeline", "skeletal"], required: false },
+  { path: "modules/audio.md", reason: "audio routing, sound effects, music, and mix guidance", roles: [...programmingRoles, ...audioRoles], keywords: ["audio", "sound", "sfx", "music", "mix", "voice", "subtitle"], required: false },
+  { path: "modules/input.md", reason: "input actions, remapping, devices, and accessibility guidance", roles: [...programmingRoles, ...designRoles, "accessibility-specialist"], keywords: ["input", "control", "controls", "gamepad", "keyboard", "remap", "binding", "accessibility"], required: false },
+  { path: "modules/navigation.md", reason: "AI navigation, navmesh, pathfinding, and movement-agent guidance", roles: [...programmingRoles, "ai-programmer", "level-designer"], keywords: ["navigation", "navmesh", "pathfinding", "ai", "agent", "steering"], required: false },
+  { path: "modules/networking.md", reason: "multiplayer, replication, rollback, synchronization, and authority guidance", roles: [...programmingRoles, "network-programmer", ...qaRoles], keywords: ["network", "networking", "multiplayer", "replication", "rollback", "netcode", "sync", "authority", "server", "client"], required: false },
+  { path: "modules/physics.md", reason: "physics bodies, collision, queries, and deterministic simulation guidance", roles: [...programmingRoles, "game-feel-designer", ...qaRoles], keywords: ["physics", "collision", "rigidbody", "raycast", "query", "deterministic", "simulation"], required: false },
+  { path: "modules/rendering.md", reason: "rendering pipeline, materials, lighting, post-processing, and performance guidance", roles: [...programmingRoles, ...artRoles, "performance-analyst"], keywords: ["render", "rendering", "material", "shader", "lighting", "post-processing", "postprocess", "gpu", "performance"], required: false },
+  { path: "modules/ui.md", reason: "UI layout, HUD, menus, focus, and accessibility guidance", roles: [...programmingRoles, "ui-programmer", "ui-ux-designer", "accessibility-specialist"], keywords: ["ui", "ux", "hud", "menu", "menus", "widget", "interface", "focus", "screen"], required: false }
+];
+
+const pluginReferences: Record<EngineReferenceId, EngineReferencePrompt[]> = {
+  godot: [
+    { path: "plugins.md", reason: "Godot addons, asset library, and GDExtension guidance", roles: ["tools-programmer", "engine-programmer", "godot-specialist"], keywords: ["plugin", "addon", "gdextension", "asset library", "tool script"], required: false }
+  ],
+  unity: [
+    { path: "plugins.md", reason: "Unity package manager and verified package guidance", roles: ["tools-programmer", "engine-programmer", "unity-specialist"], keywords: ["plugin", "package", "upm", "manifest"], required: false },
+    { path: "plugins/addressables.md", reason: "Unity Addressables asset loading and content update guidance", roles: ["tools-programmer", "engine-programmer", "technical-artist", "unity-specialist"], keywords: ["addressables", "assetbundle", "asset bundle", "content update", "remote content", "asset loading"], required: false },
+    { path: "plugins/cinemachine.md", reason: "Unity Cinemachine camera and follow-target guidance", roles: ["gameplay-programmer", "technical-artist", "game-feel-designer", "unity-specialist"], keywords: ["cinemachine", "camera", "follow", "look at", "confiner", "dolly"], required: false },
+    { path: "plugins/dots.md", reason: "Unity DOTS, ECS, Burst, and Jobs guidance", roles: ["engine-programmer", "performance-analyst", "unity-specialist"], keywords: ["dots", "ecs", "entities", "burst", "jobs", "job system", "data-oriented"], required: false }
+  ],
+  unreal: [
+    { path: "plugins.md", reason: "Unreal plugin, module, and marketplace guidance", roles: ["tools-programmer", "engine-programmer", "unreal-specialist"], keywords: ["plugin", "module", "marketplace"], required: false },
+    { path: "plugins/gas.md", reason: "Unreal Gameplay Ability System guidance", roles: ["gameplay-programmer", "systems-designer", "network-programmer", "unreal-specialist"], keywords: ["gas", "gameplay ability", "ability system", "attribute", "effect", "tag"], required: false },
+    { path: "plugins/common-ui.md", reason: "Unreal Common UI input routing and screen stack guidance", roles: ["ui-programmer", "ui-ux-designer", "accessibility-specialist", "unreal-specialist"], keywords: ["common ui", "commonui", "widget", "input routing", "screen stack", "ui"], required: false },
+    { path: "plugins/pcg.md", reason: "Unreal PCG procedural content guidance", roles: ["level-designer", "technical-artist", "tools-programmer", "unreal-specialist"], keywords: ["pcg", "procedural", "generation", "scatter", "graph"], required: false }
+  ]
+};
+
+const requiredMetadata = ["reviewer", "date", "source-link", "engine", "version-reviewed", "tags", "roles", "workflows"] as EngineReferencePack["validation"]["requiredMetadata"];
 
 function pack(engine: EngineReferenceId): EngineReferencePack {
   const packageRoot = `engine_reference/${engine}`;
   const projectRoot = `docs/engine-reference/${engine}`;
+  const requiredFiles = ["VERSION.md", "current-best-practices.md", "deprecated-apis.md", "breaking-changes.md", "gameplay.md", "specialist.md"];
+  const pluginFiles = pluginReferences[engine].map((reference) => reference.path);
+  const allReferenceFiles = [...new Set([...requiredFiles, ...moduleFiles, ...pluginFiles])];
   return {
     engine,
     packageRoot,
     projectRoot,
-    requiredFiles: ["VERSION.md", "gameplay.md", "specialist.md"],
-    pluginFiles: ["plugins.md"],
+    requiredFiles,
+    moduleFiles,
+    pluginFiles,
     specialistFiles: ["specialist.md"],
     promptReferences: [
       { path: "VERSION.md", reason: `${engine} version applicability and official links`, required: true },
+      { path: "current-best-practices.md", reason: `${engine} current best practices and default guardrails`, required: true },
       { path: "gameplay.md", reason: `${engine} gameplay implementation reference`, roles: programmingRoles, required: false },
-      { path: "plugins.md", reason: `${engine} plugin and package guidance`, roles: ["tools-programmer", "engine-programmer"], required: false },
-      { path: "specialist.md", reason: `${engine} specialist role reference`, roles: [`${engine}-specialist` as StudioRoleId], required: false }
+      { path: "deprecated-apis.md", reason: `${engine} deprecated API avoidance guidance`, roles: [...programmingRoles, ...qaRoles], keywords: ["deprecated", "deprecation", "obsolete", "upgrade", "migration"], required: false },
+      { path: "breaking-changes.md", reason: `${engine} breaking-change and migration guidance`, roles: [...programmingRoles, ...qaRoles], keywords: ["breaking", "migration", "upgrade", "version", "compatibility"], required: false },
+      { path: "specialist.md", reason: `${engine} specialist role reference`, roles: [`${engine}-specialist` as StudioRoleId], required: false },
+      ...moduleReferences,
+      ...pluginReferences[engine]
     ],
-    validation: { requiredMetadata: ["reviewer", "date", "source-link"] },
-    packageSmokeFiles: ["VERSION.md", "gameplay.md"],
+    validation: { requiredMetadata },
+    packageSmokeFiles: allReferenceFiles,
     projectPath(file: string): string {
       return `${projectRoot}/${file}`;
     }
@@ -75,18 +131,34 @@ export function engineReferenceProjectPath(engine: EngineReferenceId, file: stri
   return engineReferenceRegistry[engine].projectPath(file);
 }
 
-export function selectedEngineReferencePrompts(engine: EngineReferenceId, role: StudioRoleId): EngineReferencePrompt[] {
-  return engineReferenceRegistry[engine].promptReferences.filter((reference) => reference.required || !reference.roles || reference.roles.includes(role));
+function keywordMatches(task: string | undefined, keywords: string[] | undefined): boolean {
+  if (!task || !keywords?.length) return false;
+  const normalized = task.toLowerCase();
+  return keywords.some((keyword) => normalized.includes(keyword.toLowerCase()));
 }
 
-export function defaultEngineReferenceContextRequests(studio: StudioProjectState): { sourcePath: string; reason: string; required?: boolean }[] {
-  return selectedEngineReferencePrompts(studio.engine, "gameplay-programmer").map((reference) => ({
-    sourcePath: engineReferenceProjectPath(studio.engine, reference.path),
+export function selectedEngineReferencePrompts(engine: EngineReferenceId, role: StudioRoleId, task?: string): EngineReferencePrompt[] {
+  return engineReferenceRegistry[engine].promptReferences.filter((reference) => {
+    if (reference.required) return true;
+    const roleMatches = !reference.roles || reference.roles.includes(role);
+    if (!roleMatches) return false;
+    if (reference.keywords?.length) return keywordMatches(task, reference.keywords);
+    return true;
+  });
+}
+
+export function engineReferenceContextRequests(engine: EngineReferenceId, role: StudioRoleId, task?: string): { sourcePath: string; reason: string; required?: boolean }[] {
+  return selectedEngineReferencePrompts(engine, role, task).map((reference) => ({
+    sourcePath: engineReferenceProjectPath(engine, reference.path),
     reason: reference.reason,
     required: reference.required
   }));
 }
 
+export function defaultEngineReferenceContextRequests(studio: StudioProjectState): { sourcePath: string; reason: string; required?: boolean }[] {
+  return engineReferenceContextRequests(studio.engine, "gameplay-programmer");
+}
+
 function pass(id: string, message: string, file?: string): EngineReferenceCheck {
   return { id, status: "pass", message, path: file };
 }
@@ -105,10 +177,14 @@ export function readEngineReferenceMetadata(body: string): Record<string, string
   return metadata;
 }
 
+function allPackFiles(pack: EngineReferencePack): string[] {
+  return [...new Set([...pack.requiredFiles, ...pack.moduleFiles, ...pack.pluginFiles, ...pack.specialistFiles])];
+}
+
 export function validateEngineReferencePacks(packageRoot: string): EngineReferenceCheck[] {
   const checks: EngineReferenceCheck[] = [];
   for (const pack of Object.values(engineReferenceRegistry)) {
-    for (const file of [...new Set([...pack.requiredFiles, ...pack.pluginFiles, ...pack.specialistFiles])]) {
+    for (const file of allPackFiles(pack)) {
       const full = engineReferencePackagePath(packageRoot, pack.engine, file);
       if (!existsSync(full)) {
         checks.push(fail(`engine_reference.${pack.engine}.${file}.exists`, `${pack.engine} ${file} missing`, full));
@@ -116,15 +192,25 @@ export function validateEngineReferencePacks(packageRoot: string): EngineReferen
       }
       checks.push(pass(`engine_reference.${pack.engine}.${file}.exists`, `${pack.engine} ${file} exists`, full));
       const metadata = readEngineReferenceMetadata(readFileSync(full, "utf8"));
-      const metadataOk =
+      const hasBaseMetadata =
         typeof metadata.reviewer === "string" &&
         metadata.reviewer.trim().length > 0 &&
         /^\d{4}-\d{2}-\d{2}$/.test(metadata.date ?? "") &&
         /^https:\/\/.+/.test(metadata["source-link"] ?? "");
+      const hasReferenceMetadata =
+        metadata.engine === pack.engine &&
+        typeof metadata["version-reviewed"] === "string" &&
+        metadata["version-reviewed"].trim().length > 0 &&
+        typeof metadata.tags === "string" &&
+        metadata.tags.trim().length > 0 &&
+        typeof metadata.roles === "string" &&
+        metadata.roles.trim().length > 0 &&
+        typeof metadata.workflows === "string" &&
+        metadata.workflows.trim().length > 0;
       checks.push(
-        metadataOk
+        hasBaseMetadata && hasReferenceMetadata
           ? pass(`engine_reference.${pack.engine}.${file}.metadata`, `${pack.engine} ${file} seed review metadata present`, full)
-          : fail(`engine_reference.${pack.engine}.${file}.metadata`, `${pack.engine} ${file} must include reviewer/date/source-link metadata`, full)
+          : fail(`engine_reference.${pack.engine}.${file}.metadata`, `${pack.engine} ${file} must include reviewer/date/source-link/engine/version-reviewed/tags/roles/workflows metadata`, full)
       );
     }
   }
@@ -133,9 +219,8 @@ export function validateEngineReferencePacks(packageRoot: string): EngineReferen
 
 export function materializeEngineReferences(projectRoot: string, packageRoot: string, engine: EngineReferenceId): string[] {
   const pack = engineReferenceRegistry[engine];
-  const files = [...new Set([...pack.requiredFiles, ...pack.pluginFiles, ...pack.specialistFiles])];
   const written: string[] = [];
-  for (const file of files) {
+  for (const file of allPackFiles(pack)) {
     const source = engineReferencePackagePath(packageRoot, engine, file);
     const destination = path.join(projectRoot, pack.projectPath(file));
     mkdirSync(path.dirname(destination), { recursive: true });
diff --git a/src/projects.ts b/src/projects.ts
index eca2e48..33b5f72 100644
--- a/src/projects.ts
+++ b/src/projects.ts
@@ -2,6 +2,7 @@ import { existsSync, mkdirSync, readFileSync, readdirSync, writeFileSync } from
 import path from "node:path";
 import { activeAgentsForProject, slugify, type ProjectConfig, type ProjectMode } from "./config.js";
 import { createEngineFolders, createEngineProjectFiles, loadEngineConfigs, normalizeEngine, projectClassName, sourceRoot, unrealProjectFileName } from "./engines.js";
+import { writeDefaultProjectCustomization, readProjectCustomization } from "./customization.js";
 import { materializeEngineReferences } from "./engine-reference.js";
 import { materializeAgents } from "./agents.js";
 import { writeApprovalStore } from "./approvals.js";
@@ -9,7 +10,7 @@ import { writeContextManifest } from "./context-manifest.js";
 import { renderGeneratedSurfaceMetadata } from "./generated-surfaces.js";
 import { packageAssetPath, resolveProjectRoot } from "./paths.js";
 import { projectRoleIdsForEngine, rolePackages, type StudioRoleId } from "./roles.js";
-import { workflowIds, workflowRegistry, type WorkflowId } from "./workflows.js";
+import { workflowAliases, workflowIds, workflowRegistry, type WorkflowId } from "./workflows.js";
 import type { StudioMode } from "./studio-policy.js";
 
 export type InitProjectOptions = {
@@ -199,6 +200,15 @@ export function workflowBody(workflow: WorkflowId): string {
     "",
     `${pkg.displayName} (${definition.role}) owns this workflow.`,
     "",
+    "## Taxonomy",
+    "",
+    `Category: ${definition.category}`,
+    "CCGS-derived gap coverage:",
+    ...definition.gapCoverage.map((item) => `- ${item}`),
+    "",
+    "CLI aliases:",
+    ...(workflowAliases(definition).length ? workflowAliases(definition).map((alias) => `- ${alias}`) : ["- none"]),
+    "",
     "## Outputs",
     "",
     ...pkg.expectedOutputs.map((item) => `- ${item}`),
@@ -224,6 +234,9 @@ export function workflowSourceInput(workflow: WorkflowId): unknown {
     role: definition.role,
     phase: definition.phase,
     objective: definition.objective,
+    category: definition.category,
+    gapCoverage: definition.gapCoverage,
+    aliases: workflowAliases(definition),
     file: definition.file,
     contextFiles: definition.contextFiles,
     templateIds: definition.templateIds ?? [],
@@ -251,6 +264,7 @@ export function initProject(options: InitProjectOptions, cwd = process.cwd()): {
   mkdirSync(path.join(projectRoot, ".codex", "runs"), { recursive: true });
   writeApprovalStore(projectRoot);
   writeStudioProject(projectRoot, studioStateFromConfig(config));
+  writeDefaultProjectCustomization(projectRoot);
   writeCodexWorkflowFiles(projectRoot);
   writeStarterDocs(projectRoot, config);
   materializeEngineReferences(projectRoot, packageAssetPath("."), config.project.engine);
@@ -262,6 +276,7 @@ export function initProject(options: InitProjectOptions, cwd = process.cwd()): {
 export function statusProject(project?: string, cwd = process.cwd()): string {
   const root = resolveProjectRoot(project, cwd);
   const config = readStudioProject(root);
+  const customization = readProjectCustomization(root);
   return [
     `${config.name}`,
     `phase: ${config.phase}`,
@@ -269,7 +284,8 @@ export function statusProject(project?: string, cwd = process.cwd()): string {
     `mode: ${config.mode}`,
     `studio mode: ${config.studioMode}`,
     `engine: ${config.engine}`,
-    `active roles: ${(config.activeRoles ?? config.roles).join(", ")}`
+    `active roles: ${(config.activeRoles ?? config.roles).join(", ")}`,
+    `custom roles: ${customization.roles.length}, workflows: ${customization.workflows.length}, templates: ${customization.templates.length}`
   ].join("\n");
 }
 
diff --git a/src/roles.ts b/src/roles.ts
index 6a52dc1..deb2aab 100644
--- a/src/roles.ts
+++ b/src/roles.ts
@@ -7,52 +7,154 @@ export const studioRoleIds = [
   "senior-game-designer",
   "game-designer",
   "narrative-designer",
+  "writer",
+  "world-builder",
+  "level-designer",
   "game-feel-designer",
+  "systems-designer",
+  "economy-designer",
   "gameplay-programmer",
+  "ai-programmer",
+  "network-programmer",
+  "ui-programmer",
   "engine-programmer",
   "godot-specialist",
   "unity-specialist",
   "unreal-specialist",
   "tools-programmer",
+  "technical-director",
+  "devops-engineer",
+  "security-engineer",
+  "performance-analyst",
   "senior-game-artist",
   "technical-artist",
+  "audio-director",
+  "sound-designer",
   "ui-ux-designer",
+  "accessibility-specialist",
   "qa-playtester",
+  "localization-lead",
+  "live-ops-designer",
+  "community-manager",
   "release-manager"
 ] as const;
 
 export type StudioRoleId = (typeof studioRoleIds)[number];
 export type RoleEngineId = "godot" | "unity" | "unreal";
 
+export type RoleContractFragmentId = "scope-control" | "verification-evidence" | "write-policy" | "handoff-discipline" | "release-readiness";
+
 export type CodexRolePackage = {
   id: StudioRoleId;
   displayName: string;
   systemPrompt: string;
   contextStrategy: "minimal" | "focused" | "broad";
+  responsibilities: string[];
+  inputsToInspect: string[];
   expectedOutputs: string[];
+  outputSchema?: string[];
+  qualityGates: string[];
+  collaborationNotes: string[];
+  stopConditions: string[];
+  sharedFragments: RoleContractFragmentId[];
   handoffTemplate: string;
   reviewChecklist: string[];
 };
 
+type RoleContractDetails = Partial<Pick<CodexRolePackage, "responsibilities" | "inputsToInspect" | "outputSchema" | "qualityGates" | "collaborationNotes" | "stopConditions" | "sharedFragments" | "handoffTemplate">>;
+
+export const roleContractFragments: Record<RoleContractFragmentId, string> = {
+  "scope-control": "Keep the response bounded to the requested role, project stage, and selected context; do not introduce hidden planner, telemetry, ownership, or parallel-orchestration behavior.",
+  "verification-evidence": "Report concrete validation, playtest, inspection, or build evidence; label unverified assumptions and manual checks separately.",
+  "write-policy": "When file edits are allowed, make the smallest reviewable change and name the files or assets changed; when edits are not allowed, provide an implementation-ready handoff instead.",
+  "handoff-discipline": "Name the next owner only when a handoff is needed, and separate decisions, blockers, warnings, and follow-up options.",
+  "release-readiness": "Separate blocking release issues from warnings, confirm packaging/build validation evidence, and call out rollback or deferral options."
+};
+
+function defaultSharedFragments(id: StudioRoleId, contextStrategy: CodexRolePackage["contextStrategy"]): RoleContractFragmentId[] {
+  const fragments: RoleContractFragmentId[] = ["scope-control", "verification-evidence", "handoff-discipline"];
+  if (contextStrategy !== "minimal" || id.includes("programmer") || id === "technical-artist" || id === "tools-programmer") fragments.splice(2, 0, "write-policy");
+  if (id === "release-manager" || id === "producer" || id === "devops-engineer") fragments.push("release-readiness");
+  return [...new Set(fragments)];
+}
+
+function defaultInputsToInspect(id: StudioRoleId): string[] {
+  const inputs = ["AGENTS.md, .codex/studio.json, and the active project role prompt", "Task-relevant source, design, template, workflow, or engine-reference files selected for this role"];
+  if (id.includes("programmer") || id === "technical-artist" || id === "tools-programmer") inputs.push("Build, test, runtime, or engine files needed to verify the implementation slice");
+  if (id === "release-manager") inputs.push("Validation output, package/build state, release notes, blockers, and rollback notes");
+  if (id === "qa-playtester") inputs.push("Recent changes, acceptance criteria, reproduction context, and expected player-facing behavior");
+  return inputs;
+}
+
 function role(
   id: StudioRoleId,
   displayName: string,
   systemPrompt: string,
   contextStrategy: CodexRolePackage["contextStrategy"],
   expectedOutputs: string[],
-  reviewChecklist: string[]
+  reviewChecklist: string[],
+  details: RoleContractDetails = {}
 ): CodexRolePackage {
   return {
     id,
     displayName,
     systemPrompt,
     contextStrategy,
+    responsibilities: details.responsibilities ?? [systemPrompt, `Keep ${displayName} work scoped, reviewable, and aligned with the current project stage.`],
+    inputsToInspect: details.inputsToInspect ?? defaultInputsToInspect(id),
     expectedOutputs,
-    handoffTemplate: `Report decisions, changed files or artifacts, verification results, next owner, and unresolved risks for ${displayName}.`,
+    outputSchema: details.outputSchema,
+    qualityGates: details.qualityGates ?? reviewChecklist,
+    collaborationNotes: details.collaborationNotes ?? ["State assumptions and project constraints before recommendations.", "Identify handoff owners only when another role is needed."],
+    stopConditions: details.stopConditions ?? ["Stop and report a blocker when required context, approval, engine evidence, or verification access is missing."],
+    sharedFragments: details.sharedFragments ?? defaultSharedFragments(id, contextStrategy),
+    handoffTemplate: details.handoffTemplate ?? `Report decisions, changed files or artifacts, verification results, next owner, and unresolved risks for ${displayName}.`,
     reviewChecklist
   };
 }
 
+function formatList(values: string[]): string {
+  return values.length ? values.map((value) => `- ${value}`).join("\n") : "- None";
+}
+
+export function renderRoleContractSections(pkg: CodexRolePackage): string {
+  return [
+    "## Responsibilities",
+    "",
+    formatList(pkg.responsibilities),
+    "",
+    "## Inputs To Inspect",
+    "",
+    formatList(pkg.inputsToInspect),
+    "",
+    "## Expected Outputs",
+    "",
+    formatList(pkg.expectedOutputs),
+    pkg.outputSchema?.length ? "" : undefined,
+    pkg.outputSchema?.length ? "## Output Format" : undefined,
+    pkg.outputSchema?.length ? "" : undefined,
+    pkg.outputSchema?.length ? formatList(pkg.outputSchema) : undefined,
+    "",
+    "## Quality Gates",
+    "",
+    formatList(pkg.qualityGates),
+    "",
+    "## Shared Guidance",
+    "",
+    formatList(pkg.sharedFragments.map((fragment) => roleContractFragments[fragment])),
+    "",
+    "## Collaboration Notes",
+    "",
+    formatList(pkg.collaborationNotes),
+    "",
+    "## Stop Conditions",
+    "",
+    formatList(pkg.stopConditions)
+  ]
+    .filter((line): line is string => line !== undefined)
+    .join("\n");
+}
+
 export const rolePackages: Record<StudioRoleId, CodexRolePackage> = {
   "studio-orchestrator": role(
     "studio-orchestrator",
@@ -118,6 +220,30 @@ export const rolePackages: Record<StudioRoleId, CodexRolePackage> = {
     ["Narrative brief", "Content list", "Tone guidance"],
     ["Tone is consistent", "Content is shippable", "Narrative constraints are explicit"]
   ),
+  writer: role(
+    "writer",
+    "Writer",
+    "Draft shippable dialogue, item text, barks, tutorial copy, lore snippets, and narrative-facing implementation notes that fit the project's tone and production constraints.",
+    "minimal",
+    ["Draft copy", "Tone notes", "Implementation handoff"],
+    ["Copy matches the stated tone", "Text is scoped for implementation", "Localization and content risks are noted"]
+  ),
+  "world-builder": role(
+    "world-builder",
+    "World Builder",
+    "Define factions, places, rules, environmental storytelling hooks, collectible lore, and setting constraints that support level, narrative, and content production.",
+    "focused",
+    ["World bible slice", "Environment hooks", "Consistency constraints"],
+    ["Setting rules are concrete", "Locations support gameplay", "Lore does not exceed production scope"]
+  ),
+  "level-designer": role(
+    "level-designer",
+    "Level Designer",
+    "Design levels, encounter spaces, navigation beats, pacing, objective flow, metrics, blockout notes, and testable acceptance criteria for playable content.",
+    "focused",
+    ["Level brief", "Blockout notes", "Playtest criteria"],
+    ["Player path and objectives are clear", "Encounters and pacing are testable", "Metrics and constraints are implementation-ready"]
+  ),
   "game-feel-designer": role(
     "game-feel-designer",
     "Game Feel Designer",
@@ -126,13 +252,58 @@ export const rolePackages: Record<StudioRoleId, CodexRolePackage> = {
     ["Feel review", "Tuning recommendations", "Feedback checklist"],
     ["Controls are responsive", "Feedback supports player intent", "Tuning changes are actionable"]
   ),
+  "systems-designer": role(
+    "systems-designer",
+    "Systems Designer",
+    "Design interconnected rules, progression loops, resource flows, balancing levers, edge cases, and acceptance tests for durable game systems.",
+    "focused",
+    ["Systems spec", "Balance levers", "Edge-case notes"],
+    ["System loops are coherent", "Tuning values have rationale", "Failure and exploit cases are considered"]
+  ),
+  "economy-designer": role(
+    "economy-designer",
+    "Economy Designer",
+    "Model currencies, rewards, sinks, pacing, pricing, progression pressure, and fairness risks for game economies without adding hidden monetization assumptions.",
+    "focused",
+    ["Economy model", "Reward and sink table", "Balance risks"],
+    ["Sources and sinks are balanced", "Progression pacing is explicit", "Fairness and monetization risks are named"]
+  ),
   "gameplay-programmer": role(
     "gameplay-programmer",
     "Gameplay Programmer",
     "Implement gameplay systems with focused file edits, engine-native idioms, deterministic behavior, and verification evidence.",
     "focused",
     ["Code changes", "Verification results", "Implementation notes"],
-    ["Gameplay behavior matches spec", "Tests or manual checks are reported", "Engine idioms are respected"]
+    ["Gameplay behavior matches spec", "Tests or manual checks are reported", "Engine idioms are respected"],
+    {
+      outputSchema: ["Changed files", "Implementation notes", "Verification evidence", "Risks or follow-ups"],
+      collaborationNotes: ["Call out design assumptions before changing gameplay feel or balance.", "Handoff engine, art, audio, or QA risks to the matching specialist role."],
+      stopConditions: ["Stop and report a blocker when gameplay requirements are ambiguous or required engine/project files are unavailable.", "Stop before broad refactors that exceed the requested feature slice."]
+    }
+  ),
+  "ai-programmer": role(
+    "ai-programmer",
+    "AI Programmer",
+    "Implement game AI behavior, decision logic, navigation, perception, tuning hooks, debug visibility, and deterministic verification for NPC or systemic agents.",
+    "focused",
+    ["AI implementation", "Behavior tuning notes", "Debug and test evidence"],
+    ["AI behavior matches design intent", "Edge cases are testable", "Runtime and debugging implications are clear"]
+  ),
+  "network-programmer": role(
+    "network-programmer",
+    "Network Programmer",
+    "Implement networked gameplay, replication, synchronization, authority boundaries, latency handling, rollback risks, and multiplayer verification notes.",
+    "broad",
+    ["Networking implementation", "Synchronization notes", "Multiplayer verification"],
+    ["Authority and ownership are explicit", "Latency and desync risks are named", "Verification covers multiplayer behavior"]
+  ),
+  "ui-programmer": role(
+    "ui-programmer",
+    "UI Programmer",
+    "Implement HUD, menu, input, state binding, responsive layout, accessibility hooks, and UI runtime behavior from designer-facing interaction specs.",
+    "focused",
+    ["UI implementation", "State binding notes", "Interaction verification"],
+    ["UI states map to design requirements", "Input and accessibility hooks are considered", "Runtime behavior is verified"]
   ),
   "engine-programmer": role(
     "engine-programmer",
@@ -174,6 +345,38 @@ export const rolePackages: Record<StudioRoleId, CodexRolePackage> = {
     ["Tooling changes", "Usage notes", "Failure modes"],
     ["Workflow is ergonomic", "Failure modes are handled", "Automation is scoped"]
   ),
+  "technical-director": role(
+    "technical-director",
+    "Technical Director",
+    "Coordinate technical architecture, engineering tradeoffs, engine constraints, risk triage, validation gates, and discipline handoffs for game production.",
+    "broad",
+    ["Technical direction", "Architecture tradeoffs", "Risk and gate summary"],
+    ["Tradeoffs are explicit", "Technical risks map to owners", "Validation gates are practical"]
+  ),
+  "devops-engineer": role(
+    "devops-engineer",
+    "DevOps Engineer",
+    "Design build, packaging, CI, release automation, environment setup, cache strategy, and reproducible validation flows for game projects.",
+    "focused",
+    ["Build automation", "CI or packaging notes", "Reproducibility checks"],
+    ["Commands are reproducible", "Environment assumptions are explicit", "Release pipeline risks are surfaced"]
+  ),
+  "security-engineer": role(
+    "security-engineer",
+    "Security Engineer",
+    "Review game client, tools, build scripts, online surfaces, secrets handling, abuse cases, and dependency risks with practical mitigation steps.",
+    "focused",
+    ["Security review", "Threat notes", "Mitigation checklist"],
+    ["Threats are tied to project surfaces", "Secrets and dependencies are considered", "Mitigations are actionable"]
+  ),
+  "performance-analyst": role(
+    "performance-analyst",
+    "Performance Analyst",
+    "Profile frame time, memory, loading, asset cost, CPU/GPU bottlenecks, instrumentation needs, and optimization priorities for game builds.",
+    "focused",
+    ["Performance report", "Optimization priorities", "Measurement plan"],
+    ["Metrics are tied to player experience", "Bottlenecks are prioritized", "Optimization recommendations are measurable"]
+  ),
   "senior-game-artist": role(
     "senior-game-artist",
     "Senior Game Artist",
@@ -190,6 +393,22 @@ export const rolePackages: Record<StudioRoleId, CodexRolePackage> = {
     ["Art pipeline guidance", "Asset constraints", "Optimization notes"],
     ["Asset edits are explicit", "Runtime cost is considered", "Pipeline risks are surfaced"]
   ),
+  "audio-director": role(
+    "audio-director",
+    "Audio Director",
+    "Define audio pillars, music direction, soundscape priorities, implementation constraints, mix goals, and cross-discipline audio production handoffs.",
+    "focused",
+    ["Audio direction", "Soundscape priorities", "Implementation constraints"],
+    ["Audio goals support player experience", "Asset needs are prioritized", "Mix and implementation risks are named"]
+  ),
+  "sound-designer": role(
+    "sound-designer",
+    "Sound Designer",
+    "Specify sound effects, feedback cues, ambience, music triggers, implementation events, and audio verification notes for gameplay moments.",
+    "minimal",
+    ["Sound cue list", "Audio event notes", "Verification checklist"],
+    ["Cues map to gameplay feedback", "Events are implementation-ready", "Accessibility and mix issues are considered"]
+  ),
   "ui-ux-designer": role(
     "ui-ux-designer",
     "UI UX Designer",
@@ -198,13 +417,50 @@ export const rolePackages: Record<StudioRoleId, CodexRolePackage> = {
     ["UI flow review", "HUD/menu recommendations", "Accessibility notes"],
     ["Flows are understandable", "Accessibility is considered", "Interaction states are specified"]
   ),
+  "accessibility-specialist": role(
+    "accessibility-specialist",
+    "Accessibility Specialist",
+    "Review accessibility for controls, visual/audio feedback, readability, cognitive load, difficulty options, platform conventions, and testable accommodations.",
+    "focused",
+    ["Accessibility review", "Accommodation checklist", "Inclusive design risks"],
+    ["Barriers are concrete", "Recommendations are testable", "Accessibility is balanced with project scope"]
+  ),
   "qa-playtester": role(
     "qa-playtester",
     "QA Playtester",
     "Find reproducible gameplay, usability, accessibility, and regression issues with clear severity, evidence, and verification steps.",
     "focused",
     ["Issue list", "Repro steps", "Severity notes"],
-    ["Findings are reproducible", "Severity is calibrated", "Verification steps are clear"]
+    ["Findings are reproducible", "Severity is calibrated", "Verification steps are clear"],
+    {
+      outputSchema: ["Issue ID", "Severity", "Reproduction steps", "Expected result", "Actual result", "Evidence"],
+      collaborationNotes: ["Route likely implementation fixes to the owning programmer or designer role.", "Keep subjective feel notes separate from reproducible defects."],
+      stopConditions: ["Stop and report a blocker when the build, scene, save data, or acceptance criteria needed to reproduce behavior is missing."]
+    }
+  ),
+  "localization-lead": role(
+    "localization-lead",
+    "Localization Lead",
+    "Plan localization scope, string readiness, culturalization risks, text expansion, asset dependencies, voice/subtitle needs, and handoff checks.",
+    "focused",
+    ["Localization plan", "String and asset risks", "Culturalization notes"],
+    ["Localization scope is explicit", "Text and asset dependencies are named", "Cultural risks are handled respectfully"]
+  ),
+  "live-ops-designer": role(
+    "live-ops-designer",
+    "Live Ops Designer",
+    "Design live events, retention loops, update cadence, economy impacts, player messaging, operational risks, and post-launch measurement plans.",
+    "focused",
+    ["Live ops plan", "Event loop notes", "Measurement and risk summary"],
+    ["Cadence and player value are clear", "Economy impact is considered", "Measurement and rollback risks are named"]
+  ),
+  "community-manager": role(
+    "community-manager",
+    "Community Manager",
+    "Plan player communication, feedback triage, community launch beats, moderation risks, sentiment signals, and actionable handoffs to production roles.",
+    "minimal",
+    ["Community plan", "Feedback triage notes", "Messaging risks"],
+    ["Player messaging is clear", "Feedback loops connect to production", "Moderation and sentiment risks are identified"]
   ),
   "release-manager": role(
     "release-manager",
@@ -212,7 +468,17 @@ export const rolePackages: Record<StudioRoleId, CodexRolePackage> = {
     "Assess ship readiness, release risk, packaging, validation status, milestone blockers, and remaining warnings before release decisions.",
     "broad",
     ["Ship checklist", "Release risks", "Validation summary"],
-    ["Blockers are separated from warnings", "Validation is current", "Packaging risks are explicit"]
+    ["Blockers are separated from warnings", "Validation is current", "Packaging risks are explicit"],
+    {
+      outputSchema: ["Release decision", "Blocking issues", "Warnings", "Validation evidence", "Rollback notes"],
+      responsibilities: [
+        "Assess ship readiness, release risk, packaging, validation status, milestone blockers, and remaining warnings before release decisions.",
+        "Separate release blockers from warnings, deferrals, and accepted risks.",
+        "Keep the release recommendation tied to local validation evidence and reviewable project files."
+      ],
+      collaborationNotes: ["Escalate ownership for blockers to the role best positioned to fix them.", "Do not convert release review into hidden CI, merge approval, or governance automation."],
+      stopConditions: ["Stop and report a blocker when validation output, package state, or rollback context is unavailable.", "Stop before declaring a release ready without current validation evidence."]
+    }
   )
 };
 
diff --git a/src/runner.ts b/src/runner.ts
index 1a3f247..5b32bff 100644
--- a/src/runner.ts
+++ b/src/runner.ts
@@ -7,9 +7,11 @@ import { buildCodexExecArgs, resolveCodexCommand, type CodexExecutionResult } fr
 import { renderCodexPrompt } from "./codex-prompts.js";
 import { createCodexStudioSession, type VerificationCommand } from "./codex-session.js";
 import { selectContextEntries, type ContextManifestEntry, type ContextRequestEntry } from "./context-manifest.js";
+import { engineReferenceContextRequests } from "./engine-reference.js";
 import { renderContextContract } from "./prompt-context.js";
 import { readStudioProject } from "./projects.js";
 import { isEngineSpecialistRoleId, isStudioRoleId, projectRoleIdsForEngine, unknownStudioRoleMessage, type StudioRoleId } from "./roles.js";
+import { customPhaseForRun, customTemplateIdsForRole, findCustomRole, renderCustomRolePrompt } from "./customization.js";
 import { resolveProjectRoot } from "./paths.js";
 import { evaluateStudioRunEligibility, type CodexSandboxMode, type CodexStudioPhase, type StudioRunEligibility } from "./studio-policy.js";
 import { renderSelectedTemplates, selectTemplates } from "./templates.js";
@@ -37,7 +39,7 @@ export type PreparedRun = {
   promptPath: string;
   metadataPath: string;
   projectRoot: string;
-  role: StudioRoleId;
+  role: string;
   task: string;
   contextFiles: string[];
   verification?: VerificationCommand;
@@ -309,11 +311,89 @@ export async function executeRunLifecycle(run: PreparedRun): Promise<RunLifecycl
 
 let runSequence = 0;
 
+function prepareCustomRun(role: ReturnType<typeof findCustomRole> extends infer T ? NonNullable<T> : never, options: RunOptions, cwd: string, roleInput: string, task: string, projectRoot: string): PreparedRun {
+  const studio = readStudioProject(projectRoot);
+  const artifactRefs = (options.includeArtifact ?? []).map((artifact) => {
+    const { full, display } = safeArtifact(projectRoot, artifact);
+    return { full, display };
+  });
+  const artifactDisplays = artifactRefs.map((artifact) => artifact.display);
+  const contextRequests: ContextRequestEntry[] = [
+    { sourcePath: "AGENTS.md", reason: "project instructions", required: true },
+    { sourcePath: ".codex/studio.json", reason: "project state", required: true },
+    { sourcePath: role.promptFile, reason: "selected custom role prompt", required: true },
+    ...role.contextFiles.map((sourcePath) => ({ sourcePath, reason: "custom role context", required: false })),
+    ...artifactDisplays.map((display) => ({ sourcePath: display, reason: "included artifact", required: true })),
+    ...(options.allowBroadContext ? broadContextRequests() : [])
+  ];
+  const contextSelection = selectContextEntries(projectRoot, contextRequests);
+  const contextFilesForRun = contextFiles(contextSelection.entries);
+  const selectedContextFiles = new Set(contextFilesForRun);
+  const artifactBodies = artifactRefs
+    .filter((artifact) => selectedContextFiles.has(artifact.display))
+    .map((artifact) => `\n\n# Included Artifact: ${artifact.display}\n\n${readFileSync(artifact.full, "utf8")}`);
+  const maxFixPasses = options.maxFixPasses ?? 1;
+  if (!Number.isFinite(maxFixPasses) || maxFixPasses < 0) throw new Error("--max-fix-passes must be a finite non-negative number");
+  const phase = customPhaseForRun(role);
+  const eligibility = evaluateStudioRunEligibility({
+    projectStage: studio.mode,
+    studioMode: studio.studioMode,
+    phase,
+    approvedByUser: options.approvedByUser,
+    constrainedSandbox: options.constrainedSandbox
+  });
+  if (!eligibility.allowed && !options.printPrompt && !options.dryRun) throw new Error(eligibility.reason);
+  const templateIds = customTemplateIdsForRole(projectRoot, role.id, task);
+  const prompt = [
+    "# Codex Game Studio Custom Role Session",
+    "",
+    `Role: ${role.displayName}`,
+    `Role ID: ${role.id}`,
+    `Context Strategy: ${role.contextStrategy}`,
+    `Phase: ${phase}`,
+    `Project Root: ${projectRoot}`,
+    `Objective: ${task}`,
+    `Engine: ${studio.engine}`,
+    `Sandbox: ${eligibility.codexSandbox}`,
+    `Write Policy: ${eligibility.writePolicy}`,
+    `File Edits: ${eligibility.allowFileEdits ? "allowed" : "not allowed"}`,
+    "",
+    "## Context Files",
+    contextFilesForRun.length ? contextFilesForRun.map((file) => `- ${file}`).join("\n") : "- None selected",
+    "",
+    renderCustomRolePrompt(projectRoot, role),
+    renderSelectedTemplates(templateIds, "## Selected Templates", { projectRoot }),
+    artifactBodies.join("")
+  ].join("\n");
+  const runId = `${new Date().toISOString().replace(/[-:.TZ]/g, "").slice(0, 17)}-${process.pid}-${++runSequence}`;
+  const runDir = path.join(projectRoot, ".codex", "runs", `${runId}-${role.id}`);
+  const promptPath = path.join(runDir, "prompt.md");
+  const metadataPath = path.join(runDir, "metadata.json");
+  if (!options.printPrompt && !options.dryRun) {
+    mkdirSync(runDir, { recursive: true });
+    writeFileSync(promptPath, prompt);
+    writeFileSync(
+      metadataPath,
+      `${JSON.stringify({ timestamp: new Date().toISOString(), product: "codex-game-studio", project: path.relative(cwd, projectRoot) || ".", role: role.id, task, customRole: true, prompt_chars: prompt.length, prompt_cache_path: path.relative(cwd, promptPath), writePolicy: eligibility.writePolicy, allowFileEdits: eligibility.allowFileEdits, codexSandbox: eligibility.codexSandbox, eligibility }, null, 2)}\n`
+    );
+  }
+  const codexBin = options.codexBin ?? resolveCodexCommand();
+  const codexCommand = codexExecInvocation(projectRoot, codexBin, eligibility.codexSandbox);
+  const output = options.printPrompt
+    ? prompt
+    : options.dryRun
+      ? `Prompt cache (not written): ${promptPath}\nMetadata (not written): ${metadataPath}\n${formatEligibility(eligibility)}\nContext files:\n${contextFilesForRun.map((f) => `- ${f}`).join("\n")}\nCodex command: ${codexCommand.display}`
+      : `Prompt cache written: ${promptPath}\n${formatEligibility(eligibility)}\nExecuting Codex: ${codexCommand.display}`;
+  return { prompt, promptPath, metadataPath, projectRoot, role: roleInput, task, contextFiles: contextFilesForRun, verification: options.verifyCommand, codexCommand, output, maxFixPasses, eligibility };
+}
+
 export function prepareRun(roleInput: string, options: RunOptions, cwd = process.cwd()): PreparedRun {
-  if (!isStudioRoleId(roleInput)) throw new Error(unknownStudioRoleMessage(roleInput));
-  const role = roleInput as StudioRoleId;
   const task = requireTask(options.task);
   const projectRoot = resolveProjectRoot(options.project, cwd);
+  const customRole = isStudioRoleId(roleInput) ? undefined : findCustomRole(projectRoot, roleInput);
+  if (customRole) return prepareCustomRun(customRole, options, cwd, roleInput, task, projectRoot);
+  if (!isStudioRoleId(roleInput)) throw new Error(unknownStudioRoleMessage(roleInput));
+  const role = roleInput as StudioRoleId;
   const studio = readStudioProject(projectRoot);
   if (isEngineSpecialistRoleId(role) && !projectRoleIdsForEngine(studio.engine).includes(role)) {
     throw new Error(`${role} is not available for ${studio.engine} projects; use ${studio.engine}-specialist for this project.`);
@@ -328,6 +408,7 @@ export function prepareRun(roleInput: string, options: RunOptions, cwd = process
     { sourcePath: ".codex/studio.json", reason: "project state", required: true },
     { sourcePath: `.codex/prompts/${role}.md`, reason: "selected role prompt", required: true },
     ...artifactDisplays.map((display) => ({ sourcePath: display, reason: "included artifact", required: true })),
+    ...engineReferenceContextRequests(studio.engine, role, task),
     ...(options.allowBroadContext ? broadContextRequests() : [])
   ];
   const contextSelection = selectContextEntries(projectRoot, contextRequests);
diff --git a/src/templates.ts b/src/templates.ts
index 90fd3ec..ca02e2b 100644
--- a/src/templates.ts
+++ b/src/templates.ts
@@ -1,6 +1,7 @@
 import { existsSync, readFileSync } from "node:fs";
 import path from "node:path";
 import { packageAssetPath } from "./paths.js";
+import { findCustomTemplate, listCustomTemplates, readCustomTemplate, type CustomTemplateDefinition } from "./customization.js";
 import type { AgentName } from "./config.js";
 
 export type TemplateId =
@@ -16,71 +17,109 @@ export type TemplateId =
   | "ui_ux_review"
   | "production_milestone"
   | "playtest_report"
-  | "ship_check";
+  | "ship_check"
+  | "adr"
+  | "technical_design"
+  | "architecture_traceability"
+  | "art_bible"
+  | "sound_bible"
+  | "ux_spec"
+  | "accessibility_requirements"
+  | "test_plan"
+  | "test_evidence"
+  | "sprint_plan"
+  | "vertical_slice_report"
+  | "release_notes"
+  | "postmortem"
+  | "risk_register"
+  | "economy_model"
+  | "difficulty_curve"
+  | "player_journey"
+  | "pitch_document";
 
 export type TemplateInfo = {
   id: TemplateId;
   category: string;
   path: string;
+  description: string;
   roles: AgentName[];
+  workflows: string[];
   tags: string[];
   requiredSections: string[];
 };
 
+export type AnyTemplateInfo = Omit<TemplateInfo, "id" | "roles"> & { id: string; roles: string[]; custom?: true };
+
+const markdownSections = ["# Purpose", "# Inputs", "# Outputs", "# Validation"];
+
 export const templateRegistry: Record<TemplateId, TemplateInfo> = {
   gdd: {
     id: "gdd",
     category: "design",
     path: "templates/gdd_template.md",
+    description: "Game design document scaffold for the core loop, player goals, systems, content scope, and risks.",
     roles: ["game-designer", "creative-director"],
+    workflows: ["design-spec", "brainstorm", "create-epics"],
     tags: ["design", "gdd"],
-    requiredSections: ["# Purpose", "# Inputs", "# Outputs", "# Validation"]
+    requiredSections: markdownSections
   },
   feature_spec: {
     id: "feature_spec",
     category: "design",
     path: "templates/feature_spec_template.md",
-    roles: ["senior-game-designer", "game-designer", "gameplay-programmer"],
+    description: "Feature specification scaffold for rules, edge cases, acceptance criteria, and implementation slices.",
+    roles: ["senior-game-designer", "game-designer", "gameplay-programmer", "producer"],
+    workflows: ["design-spec", "create-stories", "story-readiness"],
     tags: ["feature", "spec", "design"],
-    requiredSections: ["# Purpose", "# Inputs", "# Outputs", "# Validation"]
+    requiredSections: markdownSections
   },
   handoff: {
     id: "handoff",
     category: "coordination",
     path: "templates/handoff_template.md",
+    description: "Contributor handoff scaffold for current state, blockers, next owners, and verification evidence.",
     roles: ["studio-orchestrator", "creative-director", "producer"],
+    workflows: ["handoff", "sprint-status", "onboard"],
     tags: ["handoff", "coordination"],
-    requiredSections: ["# Purpose", "# Inputs", "# Outputs", "# Validation"]
+    requiredSections: markdownSections
   },
   analytics_setup: {
     id: "analytics_setup",
     category: "analytics",
     path: "templates/analytics_setup_template.md",
+    description: "Analytics setup scaffold for events, success metrics, experiments, and evidence loops.",
     roles: ["data-scientist", "producer"],
+    workflows: ["analytics-setup"],
     tags: ["analytics", "metrics"],
-    requiredSections: ["# Purpose", "# Inputs", "# Outputs", "# Validation"]
+    requiredSections: markdownSections
   },
   engine_setup: {
     id: "engine_setup",
     category: "engine",
     path: "templates/engine_setup_template.md",
+    description: "Engine setup scaffold for project structure, run commands, import rules, and validation checks.",
     roles: ["gameplay-programmer", "engine-programmer", "technical-artist"],
+    workflows: ["prototype", "architecture-review"],
     tags: ["engine", "setup"],
-    requiredSections: ["# Purpose", "# Inputs", "# Outputs", "# Validation"]
+    requiredSections: markdownSections
   },
   market_analysis: {
     id: "market_analysis",
     category: "market",
     path: "templates/market_analysis_template.md",
+    description: "Market analysis scaffold for audience, competitors, positioning, pricing, and risks.",
     roles: ["market-analyst", "producer"],
+    workflows: ["market-analysis", "brainstorm"],
     tags: ["market", "competitors"],
-    requiredSections: ["# Purpose", "# Inputs", "# Outputs", "# Validation"]
+    requiredSections: markdownSections
   },
   project_config: {
     id: "project_config",
     category: "config",
     path: "templates/project_config_template.json",
+    description: "Canonical project configuration JSON seed used to initialize Open Game Studio projects.",
     roles: ["producer", "creative-director"],
+    workflows: ["onboard", "prototype"],
     tags: ["config", "setup"],
     requiredSections: []
   },
@@ -88,73 +127,268 @@ export const templateRegistry: Record<TemplateId, TemplateInfo> = {
     id: "game_feel_tuning",
     category: "design",
     path: "templates/game_feel_tuning_template.md",
+    description: "Game-feel tuning scaffold for controls, camera, feedback, timing, and feel validation.",
     roles: ["game-feel-designer", "qa-playtester"],
+    workflows: ["game-feel-tuning", "prototype"],
     tags: ["feel", "controls", "tuning"],
-    requiredSections: ["# Purpose", "# Inputs", "# Outputs", "# Validation"]
+    requiredSections: markdownSections
   },
   art_direction: {
     id: "art_direction",
     category: "art",
     path: "templates/art_direction_template.md",
+    description: "Art direction scaffold for visual goals, constraints, asset lists, and review criteria.",
     roles: ["senior-game-artist", "technical-artist", "creative-director"],
+    workflows: ["art-direction", "brainstorm"],
     tags: ["art", "visual", "style"],
-    requiredSections: ["# Purpose", "# Inputs", "# Outputs", "# Validation"]
+    requiredSections: markdownSections
   },
   ui_ux_review: {
     id: "ui_ux_review",
     category: "ui",
     path: "templates/ui_ux_review_template.md",
+    description: "UI/UX review scaffold for flows, HUD/menu clarity, usability, onboarding, and interaction risks.",
     roles: ["ui-ux-designer", "qa-playtester"],
+    workflows: ["ui-ux-review"],
     tags: ["ui", "ux", "usability"],
-    requiredSections: ["# Purpose", "# Inputs", "# Outputs", "# Validation"]
+    requiredSections: markdownSections
   },
   production_milestone: {
     id: "production_milestone",
     category: "production",
     path: "templates/production_milestone_template.md",
+    description: "Production milestone scaffold for goals, owners, risks, task slices, and validation gates.",
     roles: ["producer", "studio-orchestrator"],
+    workflows: ["production-milestone", "create-epics"],
     tags: ["milestone", "scope", "schedule"],
-    requiredSections: ["# Purpose", "# Inputs", "# Outputs", "# Validation"]
+    requiredSections: markdownSections
   },
   playtest_report: {
     id: "playtest_report",
     category: "qa",
     path: "templates/playtest_report_template.md",
+    description: "Playtest report scaffold for reproducible issues, blockers, warnings, and player-experience notes.",
     roles: ["qa-playtester"],
+    workflows: ["playtest", "review"],
     tags: ["playtest", "qa", "report"],
-    requiredSections: ["# Purpose", "# Inputs", "# Outputs", "# Validation"]
+    requiredSections: markdownSections
   },
   ship_check: {
     id: "ship_check",
     category: "release",
     path: "templates/ship_check_template.md",
+    description: "Ship-check scaffold for package readiness, blockers, warnings, rollback, and final validation status.",
     roles: ["release-manager", "producer"],
+    workflows: ["ship-check", "release-checklist"],
     tags: ["ship", "release", "readiness"],
-    requiredSections: ["# Purpose", "# Inputs", "# Outputs", "# Validation"]
+    requiredSections: markdownSections
+  },
+  adr: {
+    id: "adr",
+    category: "architecture",
+    path: "templates/adr_template.md",
+    description: "Architecture decision record scaffold for context, options, decision, consequences, and verification.",
+    roles: ["technical-director", "engine-programmer"],
+    workflows: ["architecture-decision", "architecture-review"],
+    tags: ["architecture", "decision", "adr"],
+    requiredSections: markdownSections
+  },
+  technical_design: {
+    id: "technical_design",
+    category: "architecture",
+    path: "templates/technical_design_template.md",
+    description: "Technical design scaffold for systems, APIs, data flow, engine constraints, risks, and test strategy.",
+    roles: ["technical-director", "engine-programmer", "tools-programmer", "producer"],
+    workflows: ["architecture-decision", "architecture-review", "prototype"],
+    tags: ["technical", "design", "architecture"],
+    requiredSections: markdownSections
+  },
+  architecture_traceability: {
+    id: "architecture_traceability",
+    category: "architecture",
+    path: "templates/architecture_traceability_template.md",
+    description: "Traceability scaffold linking design promises, architecture decisions, implementation files, and tests.",
+    roles: ["technical-director", "producer", "qa-playtester"],
+    workflows: ["architecture-decision", "architecture-review", "story-done"],
+    tags: ["architecture", "traceability", "evidence"],
+    requiredSections: markdownSections
+  },
+  art_bible: {
+    id: "art_bible",
+    category: "art",
+    path: "templates/art_bible_template.md",
+    description: "Art bible scaffold for style pillars, palette, asset rules, references, and production constraints.",
+    roles: ["senior-game-artist", "technical-artist", "creative-director"],
+    workflows: ["art-direction", "brainstorm"],
+    tags: ["art", "style", "bible"],
+    requiredSections: markdownSections
+  },
+  sound_bible: {
+    id: "sound_bible",
+    category: "audio",
+    path: "templates/sound_bible_template.md",
+    description: "Sound bible scaffold for audio pillars, music direction, SFX rules, voice/subtitle needs, and mix risks.",
+    roles: ["audio-director", "sound-designer", "creative-director"],
+    workflows: ["brainstorm", "prototype"],
+    tags: ["audio", "sound", "music"],
+    requiredSections: markdownSections
+  },
+  ux_spec: {
+    id: "ux_spec",
+    category: "ui",
+    path: "templates/ux_spec_template.md",
+    description: "UX specification scaffold for player flows, screens, interaction states, affordances, and errors.",
+    roles: ["ui-ux-designer", "game-designer", "localization-lead"],
+    workflows: ["ui-ux-review", "design-spec"],
+    tags: ["ux", "flows", "interface"],
+    requiredSections: markdownSections
+  },
+  accessibility_requirements: {
+    id: "accessibility_requirements",
+    category: "accessibility",
+    path: "templates/accessibility_requirements_template.md",
+    description: "Accessibility requirements scaffold for input, visuals, audio, text, difficulty, and verification checks.",
+    roles: ["accessibility-specialist", "ui-ux-designer", "qa-playtester", "localization-lead"],
+    workflows: ["ui-ux-review", "localization-plan", "qa-plan"],
+    tags: ["accessibility", "requirements", "inclusive-design"],
+    requiredSections: markdownSections
+  },
+  test_plan: {
+    id: "test_plan",
+    category: "qa",
+    path: "templates/test_plan_template.md",
+    description: "QA test plan scaffold for scenarios, risks, manual checks, automated checks, and exit criteria.",
+    roles: ["qa-playtester", "producer", "release-manager"],
+    workflows: ["qa-plan", "regression-suite", "release-checklist"],
+    tags: ["qa", "test", "plan"],
+    requiredSections: markdownSections
+  },
+  test_evidence: {
+    id: "test_evidence",
+    category: "qa",
+    path: "templates/test_evidence_template.md",
+    description: "Test evidence scaffold for executed checks, results, artifacts, failures, and follow-up owners.",
+    roles: ["qa-playtester", "release-manager", "performance-analyst", "gameplay-programmer"],
+    workflows: ["qa-plan", "regression-suite", "story-done", "ship-check"],
+    tags: ["qa", "evidence", "validation"],
+    requiredSections: markdownSections
+  },
+  sprint_plan: {
+    id: "sprint_plan",
+    category: "production",
+    path: "templates/sprint_plan_template.md",
+    description: "Sprint plan scaffold for iteration goals, committed stories, owners, risks, and validation gates.",
+    roles: ["producer", "studio-orchestrator"],
+    workflows: ["sprint-plan", "sprint-status"],
+    tags: ["sprint", "planning", "production"],
+    requiredSections: markdownSections
+  },
+  vertical_slice_report: {
+    id: "vertical_slice_report",
+    category: "production",
+    path: "templates/vertical_slice_report_template.md",
+    description: "Vertical-slice report scaffold for playable goals, implemented scope, missing pieces, and validation evidence.",
+    roles: ["producer", "qa-playtester", "gameplay-programmer"],
+    workflows: ["vertical-slice", "prototype", "story-done"],
+    tags: ["vertical-slice", "prototype", "report"],
+    requiredSections: markdownSections
+  },
+  release_notes: {
+    id: "release_notes",
+    category: "release",
+    path: "templates/release_notes_template.md",
+    description: "Release notes scaffold for highlights, fixes, known issues, compatibility notes, and validation evidence.",
+    roles: ["release-manager", "community-manager", "producer", "gameplay-programmer"],
+    workflows: ["ship-check", "release-checklist", "hotfix"],
+    tags: ["release", "notes", "community"],
+    requiredSections: markdownSections
+  },
+  postmortem: {
+    id: "postmortem",
+    category: "production",
+    path: "templates/postmortem_template.md",
+    description: "Postmortem scaffold for outcomes, what worked, what failed, learnings, and follow-up improvements.",
+    roles: ["producer", "studio-orchestrator", "qa-playtester"],
+    workflows: ["sprint-status", "story-done", "release-checklist"],
+    tags: ["postmortem", "retrospective", "learning"],
+    requiredSections: markdownSections
+  },
+  risk_register: {
+    id: "risk_register",
+    category: "production",
+    path: "templates/risk_register_template.md",
+    description: "Risk register scaffold for risks, impact, probability, mitigation, owner, trigger, and status.",
+    roles: ["producer", "technical-director", "release-manager", "gameplay-programmer"],
+    workflows: ["production-milestone", "sprint-plan", "ship-check", "release-checklist", "hotfix"],
+    tags: ["risk", "mitigation", "production"],
+    requiredSections: markdownSections
+  },
+  economy_model: {
+    id: "economy_model",
+    category: "design",
+    path: "templates/economy_model_template.md",
+    description: "Economy model scaffold for resources, sinks, sources, prices, progression, and balancing risks.",
+    roles: ["economy-designer", "systems-designer", "data-scientist", "senior-game-designer"],
+    workflows: ["design-spec", "brainstorm"],
+    tags: ["economy", "balance", "systems"],
+    requiredSections: markdownSections
+  },
+  difficulty_curve: {
+    id: "difficulty_curve",
+    category: "design",
+    path: "templates/difficulty_curve_template.md",
+    description: "Difficulty curve scaffold for progression beats, challenge ramps, fail states, assists, and telemetry signals.",
+    roles: ["systems-designer", "game-feel-designer", "qa-playtester", "senior-game-designer"],
+    workflows: ["game-feel-tuning", "design-spec", "qa-plan"],
+    tags: ["difficulty", "progression", "balance"],
+    requiredSections: markdownSections
+  },
+  player_journey: {
+    id: "player_journey",
+    category: "design",
+    path: "templates/player_journey_template.md",
+    description: "Player journey scaffold for onboarding, emotional beats, friction points, goals, and retention risks.",
+    roles: ["creative-director", "ui-ux-designer", "game-designer", "senior-game-designer"],
+    workflows: ["brainstorm", "ui-ux-review", "design-spec"],
+    tags: ["journey", "onboarding", "player-experience"],
+    requiredSections: markdownSections
+  },
+  pitch_document: {
+    id: "pitch_document",
+    category: "market",
+    path: "templates/pitch_document_template.md",
+    description: "Pitch document scaffold for fantasy, differentiators, audience, visual/audio hook, and production promise.",
+    roles: ["creative-director", "market-analyst", "producer", "studio-orchestrator"],
+    workflows: ["brainstorm", "market-analysis", "onboard"],
+    tags: ["pitch", "market", "concept"],
+    requiredSections: markdownSections
   }
 };
 
-export function listTemplates(): TemplateInfo[] {
-  return Object.values(templateRegistry);
+export function listTemplates(projectRoot?: string): AnyTemplateInfo[] {
+  return projectRoot ? [...Object.values(templateRegistry), ...listCustomTemplates(projectRoot)] : Object.values(templateRegistry);
 }
 
-export function readTemplate(id: TemplateId): string {
-  const info = templateRegistry[id];
-  if (!info) throw new Error(`Unknown template "${id}"`);
-  return readFileSync(packageAssetPath(info.path), "utf8");
+export function readTemplate(id: string, options: { projectRoot?: string } = {}): string {
+  const builtIn = templateRegistry[id as TemplateId];
+  if (builtIn) return readFileSync(packageAssetPath(builtIn.path), "utf8");
+  if (options.projectRoot && findCustomTemplate(options.projectRoot, id)) return readCustomTemplate(options.projectRoot, id);
+  throw new Error(`Unknown template "${id}"`);
 }
 
-export function formatTemplateShow(id: TemplateId): string {
-  const info = templateRegistry[id];
+export function formatTemplateShow(id: string, options: { projectRoot?: string } = {}): string {
+  const info = (templateRegistry[id as TemplateId] as AnyTemplateInfo | undefined) ?? (options.projectRoot ? findCustomTemplate(options.projectRoot, id) : undefined);
   if (!info) throw new Error(`Unknown template "${id}"`);
   return [
     `ID: ${info.id}`,
     `Category: ${info.category}`,
     `Path: ${info.path}`,
+    `Description: ${info.description}`,
     `Roles: ${info.roles.join(", ")}`,
+    `Workflows: ${info.workflows.join(", ")}`,
     `Tags: ${info.tags.join(", ")}`,
     "",
-    readTemplate(id)
+    readTemplate(id, options)
   ].join("\n");
 }
 
@@ -181,6 +415,9 @@ export function validateTemplateFiles(): string[] {
       failures.push(`Missing template ${info.id}: ${info.path}`);
       continue;
     }
+    if (!info.description.trim()) failures.push(`Template ${info.id} missing description`);
+    if (info.roles.length === 0) failures.push(`Template ${info.id} missing role hints`);
+    if (info.workflows.length === 0) failures.push(`Template ${info.id} missing workflow hints`);
     const body = readFileSync(fullPath, "utf8");
     for (const section of info.requiredSections) {
       if (!sectionHasContent(body, section)) failures.push(`Template ${info.id} missing non-empty ${section}`);
@@ -190,15 +427,19 @@ export function validateTemplateFiles(): string[] {
   return failures;
 }
 
-export function renderSelectedTemplates(templateIds: TemplateId[], heading = "## Selected Templates"): string {
+export function renderSelectedTemplates(templateIds: string[], heading = "## Selected Templates", options: { projectRoot?: string } = {}): string {
   if (templateIds.length === 0) return "";
   return [
     "",
     heading,
     "",
     ...templateIds.flatMap((id) => {
-      const info = templateRegistry[id];
-      return [`### Template: ${id}`, `Source: package:${info.path}`, "", readTemplate(id).trim(), ""];
+      const builtIn = templateRegistry[id as TemplateId];
+      const custom = !builtIn && options.projectRoot ? findCustomTemplate(options.projectRoot, id) : undefined;
+      const info = builtIn ?? custom;
+      if (!info) throw new Error(`Unknown template "${id}"`);
+      const sourcePrefix = custom ? "project" : "package";
+      return [`### Template: ${id}`, `Source: ${sourcePrefix}:${info.path}`, "", readTemplate(id, options).trim(), ""];
     })
   ].join("\n");
 }
@@ -228,8 +469,26 @@ export function selectTemplates(agent: AgentName, task: string): TemplateId[] {
   if (agent === "qa-playtester" && /(feel|control|movement|timing|camera|pacing)/.test(lower)) selected.add("game_feel_tuning");
   if ((agent === "senior-game-artist" || agent === "technical-artist" || agent === "creative-director") && /(art|visual|style|asset|direction)/.test(lower)) {
     selected.add("art_direction");
+    selected.add("art_bible");
   }
   if ((agent === "producer" || agent === "studio-orchestrator") && /(milestone|scope|schedule|production)/.test(lower)) selected.add("production_milestone");
+  if ((agent === "producer" || agent === "studio-orchestrator") && /sprint/.test(lower)) selected.add("sprint_plan");
+  if ((agent === "producer" || agent === "release-manager" || agent === "community-manager") && /(release|ship|readiness|package|launch|notes)/.test(lower)) selected.add("release_notes");
   if ((agent === "producer" || agent === "release-manager") && /(release|ship|readiness|package|launch)/.test(lower)) selected.add("ship_check");
+  if ((agent === "producer" || agent === "technical-director" || agent === "release-manager") && /(risk|mitigation|rollback|blocker)/.test(lower)) selected.add("risk_register");
+  if ((agent === "technical-director" || agent === "engine-programmer") && /(adr|architecture decision|decision record)/.test(lower)) selected.add("adr");
+  if ((agent === "technical-director" || agent === "engine-programmer" || agent === "tools-programmer") && /(technical design|system design|architecture)/.test(lower)) selected.add("technical_design");
+  if ((agent === "technical-director" || agent === "producer" || agent === "qa-playtester") && /(traceability|architecture|decision)/.test(lower)) selected.add("architecture_traceability");
+  if ((agent === "audio-director" || agent === "sound-designer" || agent === "creative-director") && /(sound|audio|music|sfx)/.test(lower)) selected.add("sound_bible");
+  if ((agent === "ui-ux-designer" || agent === "game-designer") && /(ux|flow|screen|interface|journey)/.test(lower)) selected.add("ux_spec");
+  if ((agent === "accessibility-specialist" || agent === "ui-ux-designer" || agent === "qa-playtester" || agent === "localization-lead") && /(accessibility|accessible|subtitle|remap|colorblind)/.test(lower)) selected.add("accessibility_requirements");
+  if ((agent === "qa-playtester" || agent === "producer") && /(test plan|qa plan|scenario|exit criteria)/.test(lower)) selected.add("test_plan");
+  if ((agent === "qa-playtester" || agent === "release-manager") && /(test evidence|evidence|results|regression)/.test(lower)) selected.add("test_evidence");
+  if ((agent === "producer" || agent === "qa-playtester" || agent === "gameplay-programmer") && /(vertical slice|prototype report|playable slice)/.test(lower)) selected.add("vertical_slice_report");
+  if ((agent === "producer" || agent === "studio-orchestrator" || agent === "qa-playtester") && /(postmortem|retro|retrospective)/.test(lower)) selected.add("postmortem");
+  if ((agent === "economy-designer" || agent === "systems-designer" || agent === "data-scientist") && /(economy|resource|currency|sink|source|price)/.test(lower)) selected.add("economy_model");
+  if ((agent === "systems-designer" || agent === "game-feel-designer" || agent === "qa-playtester") && /(difficulty|curve|progression|challenge)/.test(lower)) selected.add("difficulty_curve");
+  if ((agent === "creative-director" || agent === "ui-ux-designer" || agent === "game-designer") && /(player journey|onboarding|emotional beat|friction)/.test(lower)) selected.add("player_journey");
+  if ((agent === "creative-director" || agent === "market-analyst" || agent === "producer") && /(pitch|differentiator|hook|fantasy)/.test(lower)) selected.add("pitch_document");
   return [...selected];
 }
diff --git a/src/validation.ts b/src/validation.ts
index b3faac7..e090bc3 100644
--- a/src/validation.ts
+++ b/src/validation.ts
@@ -6,8 +6,10 @@ import path from "node:path";
 import { activeAgentsForProject } from "./config.js";
 import { projectAgentsMdRequiredSections, projectRolePromptSourceInput, renderProjectRolePrompt, validateBaseAgents } from "./agents.js";
 import { validateApprovalStore } from "./approvals.js";
+import { runBehavioralEvaluations } from "./behavioral-evaluation.js";
 import { checkCodexAvailability } from "./codex-runtime.js";
 import { contextManifestInput, createContextManifest, type ContextManifest, type ContextManifestMeta } from "./context-manifest.js";
+import { validateProjectCustomization } from "./customization.js";
 import { createCodexStudioSession } from "./codex-session.js";
 import { renderCodexPrompt } from "./codex-prompts.js";
 import { loadEngineConfigs, sourceRoot, unrealProjectFileName } from "./engines.js";
@@ -161,7 +163,7 @@ function engineReferenceRepoChecks(root: string): ValidationCheck[] {
 function engineReferenceProjectChecks(projectRoot: string, studio: StudioProjectState): ValidationCheck[] {
   const checks: ValidationCheck[] = [];
   const pack = engineReferenceRegistry[studio.engine];
-  const materializedFiles = [...new Set([...pack.requiredFiles, ...pack.pluginFiles, ...pack.specialistFiles])];
+  const materializedFiles = [...new Set([...pack.requiredFiles, ...pack.moduleFiles, ...pack.pluginFiles, ...pack.specialistFiles])];
   for (const file of materializedFiles) {
     const projectFile = path.join(projectRoot, pack.projectPath(file));
     checks.push(existsSync(projectFile) ? pass(`engine_reference.project.${studio.engine}.${file}`, `${studio.engine} ${file} materialized`, projectFile) : fail(`engine_reference.project.${studio.engine}.${file}`, `${studio.engine} ${file} missing from generated project`, projectFile));
@@ -231,7 +233,7 @@ export async function validateRepo(root = process.cwd()): Promise<ValidationChec
   for (const file of ["dist/", "engine_configs/", "engine_reference/", "templates/"]) {
     checks.push(pkg.files?.includes(file) ? pass(`pkg.files.${file}`, `${file} shipped`) : fail(`pkg.files.${file}`, `${file} missing from package files`, pkgPath));
   }
-  for (const file of ["src/cli.ts", "src/codex-runtime.ts", "src/codex-session.ts", "src/codex-prompts.ts", "src/prompt-context.ts", "src/context-manifest.ts", "src/roles.ts", "src/tasks.ts", "src/workflows.ts", "src/verification.ts", "src/projects.ts", "src/runner.ts", "src/validation.ts"]) {
+  for (const file of ["src/cli.ts", "src/behavioral-evaluation.ts", "src/customization.ts", "src/codex-runtime.ts", "src/codex-session.ts", "src/codex-prompts.ts", "src/prompt-context.ts", "src/context-manifest.ts", "src/roles.ts", "src/tasks.ts", "src/workflows.ts", "src/verification.ts", "src/projects.ts", "src/runner.ts", "src/validation.ts"]) {
     checks.push(existsSync(path.join(root, file)) ? pass(`src.${file}`, `${file} exists`) : fail(`src.${file}`, `${file} missing`, file));
   }
 
@@ -258,6 +260,13 @@ export async function validateRepo(root = process.cwd()): Promise<ValidationChec
     checks.push(rendered.includes(definition.objective) ? pass(`codex.workflow.${workflow}.render`, `${workflow} workflow renders`) : fail(`codex.workflow.${workflow}.render`, `${workflow} workflow did not render`));
   }
 
+  for (const result of runBehavioralEvaluations({})) {
+    const message = result.status === "pass"
+      ? `${result.id} behavioral scenario passes`
+      : `${result.id} behavioral scenario failed: missing phrases [${result.missingRequiredPhrases.join(", ")}], forbidden phrases [${result.presentForbiddenPhrases.join(", ")}], missing context [${result.missingContextCategories.join(", ")}], missing templates [${result.missingTemplateIds.join(", ")}], forbidden templates [${result.presentForbiddenTemplateIds.join(", ")}]`;
+    checks.push(result.status === "pass" ? pass(`behavioral.scenario.${result.id}`, message) : fail(`behavioral.scenario.${result.id}`, message));
+  }
+
   const templateFailures = validateTemplateFiles();
   checks.push(...templateFailures.map((message) => fail("templates", message)));
   for (const [id, info] of Object.entries(templateRegistry)) {
@@ -339,6 +348,11 @@ export function validateProject(projectRoot: string): ValidationCheck[] {
   checks.push(JSON.stringify(studio.roles) === JSON.stringify(expectedProjectRoles) ? pass("codex.project.roles", "engine-scoped role roster recorded", studioPath) : fail("codex.project.roles", "studio roles must match engine-scoped project roles", studioPath));
   checks.push(JSON.stringify(studio.activeRoles) === JSON.stringify(expectedActiveRoles) ? pass("codex.project.activeRoles", "mode and engine-active roles recorded", studioPath) : fail("codex.project.activeRoles", "activeRoles must match project mode and engine", studioPath));
   checks.push(JSON.stringify(studio.workflows) === JSON.stringify(workflowIds()) ? pass("codex.project.workflows", "canonical workflows recorded", studioPath) : fail("codex.project.workflows", "workflows must match registry keys", studioPath));
+  checks.push(
+    ...validateProjectCustomization(projectRoot, { builtInWorkflowIds: workflowIds(), builtInTemplateIds: Object.keys(templateRegistry) }).map((check) =>
+      check.status === "pass" ? pass(check.id, check.message, check.path) : fail(check.id, check.message, check.path)
+    )
+  );
 
   const approvalsPath = path.join(projectRoot, ".codex", "approvals.json");
   if (!existsSync(approvalsPath)) {
diff --git a/src/workflows.ts b/src/workflows.ts
index f277a2f..451a480 100644
--- a/src/workflows.ts
+++ b/src/workflows.ts
@@ -8,7 +8,18 @@ import { renderContextContract } from "./prompt-context.js";
 import type { StudioProjectState } from "./projects.js";
 import type { StudioRoleId } from "./roles.js";
 import { evaluateStudioRunEligibility } from "./studio-policy.js";
+import { engineReferenceContextRequests } from "./engine-reference.js";
 import { renderSelectedTemplates, type TemplateId } from "./templates.js";
+import { findCustomRole, findCustomWorkflow, renderCustomRolePrompt } from "./customization.js";
+
+export type WorkflowCategory =
+  | "onboarding-discovery"
+  | "design-architecture"
+  | "implementation-planning"
+  | "qa-testing"
+  | "release-hotfix"
+  | "localization-accessibility"
+  | "team-coordination";
 
 export type WorkflowId =
   | "vertical-slice"
@@ -23,146 +34,379 @@ export type WorkflowId =
   | "production-milestone"
   | "handoff"
   | "review"
-  | "ship-check";
+  | "ship-check"
+  | "onboard"
+  | "brainstorm"
+  | "prototype"
+  | "architecture-decision"
+  | "architecture-review"
+  | "create-epics"
+  | "create-stories"
+  | "sprint-plan"
+  | "sprint-status"
+  | "story-readiness"
+  | "story-done"
+  | "qa-plan"
+  | "regression-suite"
+  | "security-audit"
+  | "perf-profile"
+  | "release-checklist"
+  | "hotfix"
+  | "localization-plan";
 
 export type WorkflowDefinition = {
   id: WorkflowId;
   role: StudioRoleId;
   phase: Extract<CodexStudioPhase, "plan" | "implement" | "review" | "ship">;
   objective: string;
+  category: WorkflowCategory;
+  gapCoverage: string[];
   file: `.codex/workflows/${string}.md`;
   contextFiles: string[];
   templateIds?: TemplateId[];
   cliAlias?: string;
+  cliAliases?: string[];
 };
 
+type WorkflowInput = Omit<WorkflowDefinition, "file" | "contextFiles"> & {
+  extraContextFiles?: string[];
+};
+
+function workflow(input: WorkflowInput): WorkflowDefinition {
+  return {
+    ...input,
+    file: `.codex/workflows/${input.id}.md`,
+    contextFiles: ["AGENTS.md", ".codex/studio.json", `.codex/workflows/${input.id}.md`, ...(input.extraContextFiles ?? [])]
+  };
+}
+
 export const workflowRegistry: Record<WorkflowId, WorkflowDefinition> = {
-  "vertical-slice": {
+  "vertical-slice": workflow({
     id: "vertical-slice",
     role: "producer",
     phase: "plan",
+    category: "implementation-planning",
+    gapCoverage: ["vertical-slice planning", "milestone decomposition"],
     objective: "Create a bounded vertical-slice plan with tasks, risks, and verification gates.",
-    file: ".codex/workflows/vertical-slice.md",
-    contextFiles: ["AGENTS.md", ".codex/studio.json", ".codex/workflows/vertical-slice.md", "documentation/design/gdd.md"]
-  },
-  bugfix: {
+    extraContextFiles: ["documentation/design/gdd.md"]
+  }),
+  bugfix: workflow({
     id: "bugfix",
     role: "gameplay-programmer",
     phase: "implement",
-    objective: "Reproduce, fix, verify, and document a defect with bounded scope.",
-    file: ".codex/workflows/bugfix.md",
-    contextFiles: ["AGENTS.md", ".codex/studio.json", ".codex/workflows/bugfix.md"]
-  },
-  playtest: {
+    category: "release-hotfix",
+    gapCoverage: ["defect triage", "bounded implementation repair"],
+    objective: "Reproduce, fix, verify, and document a defect with bounded scope."
+  }),
+  playtest: workflow({
     id: "playtest",
     role: "qa-playtester",
     phase: "review",
+    category: "qa-testing",
+    gapCoverage: ["playtest reporting", "reproducible issue capture"],
     objective: "Inspect the current build, report reproducible playtest issues, and separate blockers from warnings.",
-    file: ".codex/workflows/playtest.md",
-    contextFiles: ["AGENTS.md", ".codex/studio.json", ".codex/workflows/playtest.md"],
-    templateIds: ["playtest_report"]
-  },
-  "market-analysis": {
+    templateIds: ["playtest_report", "test_evidence"]
+  }),
+  "market-analysis": workflow({
     id: "market-analysis",
     role: "market-analyst",
     phase: "plan",
+    category: "onboarding-discovery",
+    gapCoverage: ["market discovery", "competitor positioning"],
     objective: "Analyze audience, competitors, positioning, pricing, and market risks for the current project.",
-    file: ".codex/workflows/market-analysis.md",
-    contextFiles: ["AGENTS.md", ".codex/studio.json", ".codex/workflows/market-analysis.md", "resources/market-research/market-overview.md"],
-    templateIds: ["market_analysis"],
+    extraContextFiles: ["resources/market-research/market-overview.md"],
+    templateIds: ["market_analysis", "pitch_document"],
     cliAlias: "market"
-  },
-  "analytics-setup": {
+  }),
+  "analytics-setup": workflow({
     id: "analytics-setup",
     role: "data-scientist",
     phase: "plan",
+    category: "onboarding-discovery",
+    gapCoverage: ["analytics onboarding", "success metric planning"],
     objective: "Define analytics events, success metrics, experiment plans, and evidence loops for the current project.",
-    file: ".codex/workflows/analytics-setup.md",
-    contextFiles: ["AGENTS.md", ".codex/studio.json", ".codex/workflows/analytics-setup.md"],
     templateIds: ["analytics_setup"],
     cliAlias: "analytics"
-  },
-  "design-spec": {
+  }),
+  "design-spec": workflow({
     id: "design-spec",
     role: "senior-game-designer",
     phase: "plan",
+    category: "design-architecture",
+    gapCoverage: ["feature specification", "design acceptance criteria"],
     objective: "Create or review a feature/design spec with rules, edge cases, implementation slices, and acceptance criteria.",
-    file: ".codex/workflows/design-spec.md",
-    contextFiles: ["AGENTS.md", ".codex/studio.json", ".codex/workflows/design-spec.md", "documentation/design/gdd.md"],
-    templateIds: ["feature_spec"],
+    extraContextFiles: ["documentation/design/gdd.md"],
+    templateIds: ["feature_spec", "economy_model", "difficulty_curve", "player_journey"],
     cliAlias: "design-spec"
-  },
-  "game-feel-tuning": {
+  }),
+  "game-feel-tuning": workflow({
     id: "game-feel-tuning",
     role: "game-feel-designer",
     phase: "review",
+    category: "design-architecture",
+    gapCoverage: ["game-feel review", "tuning recommendations"],
     objective: "Review moment-to-moment feel, controls, feedback, pacing, and tuning risks with actionable changes.",
-    file: ".codex/workflows/game-feel-tuning.md",
-    contextFiles: ["AGENTS.md", ".codex/studio.json", ".codex/workflows/game-feel-tuning.md"],
-    templateIds: ["game_feel_tuning"],
+    templateIds: ["game_feel_tuning", "difficulty_curve"],
     cliAlias: "feel-review"
-  },
-  "art-direction": {
+  }),
+  "art-direction": workflow({
     id: "art-direction",
     role: "senior-game-artist",
     phase: "plan",
+    category: "design-architecture",
+    gapCoverage: ["art direction", "asset production planning"],
     objective: "Define art direction, visual constraints, asset list, production risks, and review criteria.",
-    file: ".codex/workflows/art-direction.md",
-    contextFiles: ["AGENTS.md", ".codex/studio.json", ".codex/workflows/art-direction.md"],
-    templateIds: ["art_direction"],
+    templateIds: ["art_direction", "art_bible"],
     cliAlias: "art-direction"
-  },
-  "ui-ux-review": {
+  }),
+  "ui-ux-review": workflow({
     id: "ui-ux-review",
     role: "ui-ux-designer",
     phase: "review",
+    category: "localization-accessibility",
+    gapCoverage: ["UX review", "accessibility-aware UI inspection"],
     objective: "Review UI flows, HUD/menu clarity, usability, onboarding, accessibility, and interaction risks.",
-    file: ".codex/workflows/ui-ux-review.md",
-    contextFiles: ["AGENTS.md", ".codex/studio.json", ".codex/workflows/ui-ux-review.md"],
-    templateIds: ["ui_ux_review"],
+    templateIds: ["ui_ux_review", "ux_spec", "accessibility_requirements", "player_journey"],
     cliAlias: "ui-review"
-  },
-  "production-milestone": {
+  }),
+  "production-milestone": workflow({
     id: "production-milestone",
     role: "producer",
     phase: "plan",
+    category: "team-coordination",
+    gapCoverage: ["milestone planning", "production risk tracking"],
     objective: "Convert current project state into milestone goals, task slices, risks, owners, and verification gates.",
-    file: ".codex/workflows/production-milestone.md",
-    contextFiles: ["AGENTS.md", ".codex/studio.json", ".codex/workflows/production-milestone.md", "documentation/production/timeline.md"],
-    templateIds: ["production_milestone"],
+    extraContextFiles: ["documentation/production/timeline.md"],
+    templateIds: ["production_milestone", "risk_register"],
     cliAlias: "milestone"
-  },
-  handoff: {
+  }),
+  handoff: workflow({
     id: "handoff",
     role: "studio-orchestrator",
     phase: "plan",
+    category: "team-coordination",
+    gapCoverage: ["role handoff", "next-action routing"],
     objective: "Summarize current state, route next work to the right role, identify blockers, and produce a concise handoff.",
-    file: ".codex/workflows/handoff.md",
-    contextFiles: ["AGENTS.md", ".codex/studio.json", ".codex/workflows/handoff.md"],
     templateIds: ["handoff"],
     cliAlias: "handoff"
-  },
-  review: {
+  }),
+  review: workflow({
     id: "review",
     role: "qa-playtester",
     phase: "review",
-    objective: "Review the current project state and report blockers, warnings, and verification gaps as JSON.",
-    file: ".codex/workflows/review.md",
-    contextFiles: ["AGENTS.md", ".codex/studio.json", ".codex/workflows/review.md"]
-  },
-  "ship-check": {
+    category: "qa-testing",
+    gapCoverage: ["general project review", "verification gap reporting"],
+    objective: "Review the current project state and report blockers, warnings, and verification gaps as JSON."
+  }),
+  "ship-check": workflow({
     id: "ship-check",
     role: "release-manager",
     phase: "ship",
+    category: "release-hotfix",
+    gapCoverage: ["ship readiness", "release blocker review"],
     objective: "Assess milestone readiness, package risk, validation status, and release blockers.",
-    file: ".codex/workflows/ship-check.md",
-    contextFiles: ["AGENTS.md", ".codex/studio.json", ".codex/workflows/ship-check.md", "documentation/production/timeline.md"],
-    templateIds: ["ship_check"]
-  }
+    extraContextFiles: ["documentation/production/timeline.md"],
+    templateIds: ["ship_check", "release_notes", "risk_register"]
+  }),
+  onboard: workflow({
+    id: "onboard",
+    role: "studio-orchestrator",
+    phase: "plan",
+    category: "onboarding-discovery",
+    gapCoverage: ["project onboarding", "repository orientation"],
+    objective: "Orient a contributor to the project goal, current stage, key files, active roles, and safest first actions.",
+    extraContextFiles: ["documentation/design/gdd.md", "documentation/production/timeline.md"],
+    templateIds: ["handoff", "pitch_document"],
+    cliAlias: "start",
+    cliAliases: ["onboard"]
+  }),
+  brainstorm: workflow({
+    id: "brainstorm",
+    role: "creative-director",
+    phase: "plan",
+    category: "design-architecture",
+    gapCoverage: ["concept ideation", "creative option generation"],
+    objective: "Generate bounded game ideas, feature variations, player fantasies, and tradeoff notes from the current project constraints.",
+    extraContextFiles: ["documentation/design/gdd.md"],
+    templateIds: ["pitch_document", "player_journey", "art_bible", "sound_bible"],
+    cliAlias: "brainstorm"
+  }),
+  prototype: workflow({
+    id: "prototype",
+    role: "producer",
+    phase: "plan",
+    category: "implementation-planning",
+    gapCoverage: ["prototype planning", "playable-loop slicing"],
+    objective: "Plan the smallest playable prototype slice with owner roles, required assets, implementation tasks, and validation checks.",
+    extraContextFiles: ["documentation/design/gdd.md"],
+    templateIds: ["vertical_slice_report", "technical_design", "risk_register"],
+    cliAlias: "prototype"
+  }),
+  "architecture-decision": workflow({
+    id: "architecture-decision",
+    role: "technical-director",
+    phase: "plan",
+    category: "design-architecture",
+    gapCoverage: ["architecture decision records", "technical tradeoff capture"],
+    objective: "Draft an architecture decision with context, options, selected direction, consequences, risks, and verification implications.",
+    extraContextFiles: ["documentation/design/gdd.md"],
+    templateIds: ["adr", "technical_design", "architecture_traceability"],
+    cliAlias: "architecture-decision"
+  }),
+  "architecture-review": workflow({
+    id: "architecture-review",
+    role: "technical-director",
+    phase: "review",
+    category: "design-architecture",
+    gapCoverage: ["architecture review", "technical risk review"],
+    objective: "Review architecture, engine constraints, module boundaries, technical risks, and validation gaps for a proposed or existing feature.",
+    templateIds: ["technical_design", "architecture_traceability"],
+    cliAlias: "architecture-review"
+  }),
+  "create-epics": workflow({
+    id: "create-epics",
+    role: "producer",
+    phase: "plan",
+    category: "implementation-planning",
+    gapCoverage: ["epic creation", "roadmap decomposition"],
+    objective: "Create production epics from the project goal with scope, owners, dependencies, risks, and acceptance signals.",
+    extraContextFiles: ["documentation/design/gdd.md", "documentation/production/timeline.md"],
+    templateIds: ["production_milestone", "risk_register"],
+    cliAlias: "create-epics"
+  }),
+  "create-stories": workflow({
+    id: "create-stories",
+    role: "producer",
+    phase: "plan",
+    category: "implementation-planning",
+    gapCoverage: ["story breakdown", "implementation-ready task slicing"],
+    objective: "Break an epic or feature into implementation-ready stories with role owner, files or artifacts to inspect, acceptance criteria, and verification gates.",
+    extraContextFiles: ["documentation/production/timeline.md"],
+    templateIds: ["feature_spec"],
+    cliAlias: "create-stories"
+  }),
+  "sprint-plan": workflow({
+    id: "sprint-plan",
+    role: "producer",
+    phase: "plan",
+    category: "team-coordination",
+    gapCoverage: ["sprint planning", "iteration commitment"],
+    objective: "Plan the next sprint or iteration with committed goals, role assignments, risks, validation gates, and explicit non-goals.",
+    extraContextFiles: ["documentation/production/timeline.md"],
+    templateIds: ["sprint_plan", "risk_register"],
+    cliAlias: "sprint-plan"
+  }),
+  "sprint-status": workflow({
+    id: "sprint-status",
+    role: "studio-orchestrator",
+    phase: "review",
+    category: "team-coordination",
+    gapCoverage: ["sprint status", "blocker visibility"],
+    objective: "Summarize sprint status, completed work, blockers, risks, next owners, and verification evidence without mutating task state.",
+    extraContextFiles: ["documentation/production/timeline.md"],
+    templateIds: ["sprint_plan", "postmortem"],
+    cliAlias: "sprint-status"
+  }),
+  "story-readiness": workflow({
+    id: "story-readiness",
+    role: "producer",
+    phase: "review",
+    category: "team-coordination",
+    gapCoverage: ["story readiness", "definition-of-ready review"],
+    objective: "Review whether a story is ready for implementation by checking scope, owner role, context files, acceptance criteria, risks, and verification commands.",
+    templateIds: ["feature_spec", "risk_register"],
+    cliAlias: "story-readiness"
+  }),
+  "story-done": workflow({
+    id: "story-done",
+    role: "qa-playtester",
+    phase: "review",
+    category: "team-coordination",
+    gapCoverage: ["definition of done", "completion review"],
+    objective: "Review whether a story is done by checking acceptance criteria, changed artifacts, verification evidence, risks, and follow-up ownership.",
+    templateIds: ["test_evidence", "vertical_slice_report", "postmortem"],
+    cliAlias: "story-done"
+  }),
+  "qa-plan": workflow({
+    id: "qa-plan",
+    role: "qa-playtester",
+    phase: "plan",
+    category: "qa-testing",
+    gapCoverage: ["test planning", "QA strategy"],
+    objective: "Create a QA plan with target scenarios, risk areas, test data, manual checks, automated checks, and exit criteria.",
+    extraContextFiles: ["documentation/design/gdd.md"],
+    templateIds: ["test_plan", "test_evidence", "accessibility_requirements"],
+    cliAlias: "qa-plan"
+  }),
+  "regression-suite": workflow({
+    id: "regression-suite",
+    role: "qa-playtester",
+    phase: "review",
+    category: "qa-testing",
+    gapCoverage: ["regression suite planning", "test coverage review"],
+    objective: "Design or review a regression suite for changed gameplay, UI, engine, content, and release-critical behavior.",
+    templateIds: ["test_plan", "test_evidence"],
+    cliAlias: "regression-suite"
+  }),
+  "security-audit": workflow({
+    id: "security-audit",
+    role: "security-engineer",
+    phase: "review",
+    category: "qa-testing",
+    gapCoverage: ["security review", "abuse-case inspection"],
+    objective: "Review security, secrets, dependencies, online surfaces, abuse cases, and mitigation priorities for the project or feature.",
+    cliAlias: "security-audit"
+  }),
+  "perf-profile": workflow({
+    id: "perf-profile",
+    role: "performance-analyst",
+    phase: "review",
+    category: "qa-testing",
+    gapCoverage: ["performance profiling", "optimization triage"],
+    objective: "Plan or review performance profiling across frame time, memory, loading, asset cost, bottlenecks, and measurement evidence.",
+    templateIds: ["test_evidence"],
+    cliAlias: "perf-profile"
+  }),
+  "release-checklist": workflow({
+    id: "release-checklist",
+    role: "release-manager",
+    phase: "ship",
+    category: "release-hotfix",
+    gapCoverage: ["release checklist", "ship gate verification"],
+    objective: "Create a release checklist with blockers, warnings, validation commands, packaging checks, rollback notes, and communication needs.",
+    extraContextFiles: ["documentation/production/timeline.md"],
+    templateIds: ["release_notes", "risk_register", "test_plan"],
+    cliAlias: "release-checklist"
+  }),
+  hotfix: workflow({
+    id: "hotfix",
+    role: "gameplay-programmer",
+    phase: "review",
+    category: "release-hotfix",
+    gapCoverage: ["hotfix triage", "safe repair planning"],
+    objective: "Triage a hotfix by identifying the minimal repair, risk surface, verification commands, rollback plan, and release communication notes.",
+    templateIds: ["release_notes", "risk_register", "test_evidence"],
+    cliAlias: "hotfix"
+  }),
+  "localization-plan": workflow({
+    id: "localization-plan",
+    role: "localization-lead",
+    phase: "plan",
+    category: "localization-accessibility",
+    gapCoverage: ["localization planning", "culturalization readiness"],
+    objective: "Create a localization plan with string scope, culturalization risks, asset dependencies, text expansion, subtitles, and verification checks.",
+    extraContextFiles: ["documentation/design/gdd.md"],
+    templateIds: ["accessibility_requirements", "ux_spec"],
+    cliAlias: "localization-plan"
+  })
 };
 
-function renderWorkflowTemplates(workflow: WorkflowId): string {
-  return renderSelectedTemplates(workflowRegistry[workflow].templateIds ?? [], "## Workflow Templates");
+export function workflowAliases(workflow: WorkflowDefinition): string[] {
+  return [...new Set([workflow.cliAlias, ...(workflow.cliAliases ?? [])].filter((alias): alias is string => Boolean(alias)))];
+}
+
+function renderWorkflowTemplates(workflow: WorkflowId, projectRoot?: string): string {
+  return renderSelectedTemplates(workflowRegistry[workflow].templateIds ?? [], "## Workflow Templates", projectRoot ? { projectRoot } : {});
 }
 
 function readStudioEngine(projectRoot: string): EngineId {
@@ -179,15 +423,20 @@ export function workflowIds(): WorkflowId[] {
 }
 
 export function workflowForAlias(alias: string): WorkflowDefinition | undefined {
-  return Object.values(workflowRegistry).find((workflow) => workflow.cliAlias === alias);
+  return Object.values(workflowRegistry).find((workflow) => workflowAliases(workflow).includes(alias));
 }
 
-export function renderWorkflowPrompt(projectRoot: string, workflow: WorkflowId): string {
-  const config = workflowRegistry[workflow];
+export function renderWorkflowPrompt(projectRoot: string, workflow: string): string {
+  const builtIn = workflowRegistry[workflow as WorkflowId];
+  if (!builtIn) return renderCustomWorkflowPrompt(projectRoot, workflow);
+  const config = builtIn;
   const studio = readWorkflowStudio(projectRoot);
   const selection = selectContextEntries(
     projectRoot,
-    config.contextFiles.map((sourcePath) => ({ sourcePath, reason: `workflow ${workflow} context`, required: true }))
+    [
+      ...config.contextFiles.map((sourcePath) => ({ sourcePath, reason: `workflow ${workflow} context`, required: true })),
+      ...engineReferenceContextRequests(studio.engine, config.role, config.objective)
+    ]
   );
   const eligibility = evaluateStudioRunEligibility({
     projectStage: studio.mode,
@@ -218,6 +467,49 @@ export function renderWorkflowPrompt(projectRoot: string, workflow: WorkflowId):
           readOnlyReview: config.phase === "review"
         })
       }
-    ) + renderWorkflowTemplates(workflow)
+    ) + renderWorkflowTemplates(workflow as WorkflowId, projectRoot)
   );
 }
+
+function renderCustomWorkflowPrompt(projectRoot: string, workflowId: string): string {
+  const workflow = findCustomWorkflow(projectRoot, workflowId);
+  if (!workflow) throw new Error(`Unknown workflow "${workflowId}"`);
+  const role = findCustomRole(projectRoot, workflow.role);
+  if (!role) throw new Error(`Custom workflow "${workflow.id}" references unavailable role "${workflow.role}"`);
+  const studio = readWorkflowStudio(projectRoot);
+  const selection = selectContextEntries(
+    projectRoot,
+    [
+      { sourcePath: "AGENTS.md", reason: `custom workflow ${workflow.id} instructions`, required: true },
+      { sourcePath: ".codex/studio.json", reason: `custom workflow ${workflow.id} project state`, required: true },
+      { sourcePath: role.promptFile, reason: `custom workflow ${workflow.id} role prompt`, required: true },
+      ...workflow.contextFiles.map((sourcePath) => ({ sourcePath, reason: `custom workflow ${workflow.id} context`, required: false }))
+    ]
+  );
+  const eligibility = evaluateStudioRunEligibility({
+    projectStage: studio.mode,
+    studioMode: studio.studioMode,
+    phase: workflow.phase
+  });
+  return [
+    "# Codex Game Studio Custom Workflow",
+    "",
+    `Workflow ID: ${workflow.id}`,
+    `Role: ${role.displayName}`,
+    `Role ID: ${role.id}`,
+    `Context Strategy: ${role.contextStrategy}`,
+    `Phase: ${workflow.phase}`,
+    `Project Root: ${projectRoot}`,
+    `Objective: ${workflow.objective}`,
+    `Engine: ${studio.engine}`,
+    `Sandbox: ${eligibility.codexSandbox}`,
+    `Write Policy: ${eligibility.writePolicy}`,
+    `File Edits: ${eligibility.allowFileEdits ? "allowed" : "not allowed"}`,
+    "",
+    "## Context Files",
+    selection.selected.length ? selection.selected.map((entry) => `- ${entry.sourcePath}`).join("\n") : "- None selected",
+    "",
+    renderCustomRolePrompt(projectRoot, role),
+    renderSelectedTemplates(workflow.templateIds, "## Workflow Templates", { projectRoot })
+  ].join("\n");
+}
diff --git a/templates/accessibility_requirements_template.md b/templates/accessibility_requirements_template.md
new file mode 100644
index 0000000..6ffcc52
--- /dev/null
+++ b/templates/accessibility_requirements_template.md
@@ -0,0 +1,15 @@
+# Purpose
+
+Define accessibility requirements for input, visuals, audio, text, and difficulty.
+
+# Inputs
+
+- Target platforms, player needs, UI/UX flows, gameplay constraints, and localization notes.
+
+# Outputs
+
+- Requirements, acceptance checks, implementation notes, and test evidence needs.
+
+# Validation
+
+- Requirements are testable and distinguish must-have blockers from nice-to-have improvements.
diff --git a/templates/adr_template.md b/templates/adr_template.md
new file mode 100644
index 0000000..d74ae2e
--- /dev/null
+++ b/templates/adr_template.md
@@ -0,0 +1,15 @@
+# Purpose
+
+Record a technical architecture decision with options and consequences.
+
+# Inputs
+
+- Problem statement, forces, engine constraints, and candidate options.
+
+# Outputs
+
+- Decision, consequences, verification plan, and review owners.
+
+# Validation
+
+- Decision links to at least one verification step and known risk.
diff --git a/templates/architecture_traceability_template.md b/templates/architecture_traceability_template.md
new file mode 100644
index 0000000..021908f
--- /dev/null
+++ b/templates/architecture_traceability_template.md
@@ -0,0 +1,15 @@
+# Purpose
+
+Trace product/design claims through architecture, implementation files, and verification.
+
+# Inputs
+
+- Design promise, decision records, impacted files, and test or playtest evidence.
+
+# Outputs
+
+- Trace table linking claims to code paths, tests, and unresolved gaps.
+
+# Validation
+
+- Every shipped claim has evidence or is marked as a gap with an owner.
diff --git a/templates/art_bible_template.md b/templates/art_bible_template.md
new file mode 100644
index 0000000..a1b96fb
--- /dev/null
+++ b/templates/art_bible_template.md
@@ -0,0 +1,15 @@
+# Purpose
+
+Define the visual production bible for art style and asset consistency.
+
+# Inputs
+
+- Art pillars, references, palette, camera/view constraints, and target platforms.
+
+# Outputs
+
+- Style rules, asset taxonomy, production constraints, and review checklist.
+
+# Validation
+
+- Asset rules are concrete enough for another contributor to produce matching work.
diff --git a/templates/difficulty_curve_template.md b/templates/difficulty_curve_template.md
new file mode 100644
index 0000000..1c2f2ec
--- /dev/null
+++ b/templates/difficulty_curve_template.md
@@ -0,0 +1,15 @@
+# Purpose
+
+Describe challenge progression, assists, failure states, and tuning validation.
+
+# Inputs
+
+- Target audience, core mechanics, levels/encounters, skill assumptions, and accessibility needs.
+
+# Outputs
+
+- Difficulty curve, challenge beats, assist rules, failure recovery, and playtest checks.
+
+# Validation
+
+- Curve has measurable validation signals and avoids one-size-fits-all difficulty claims.
diff --git a/templates/economy_model_template.md b/templates/economy_model_template.md
new file mode 100644
index 0000000..6f45cb7
--- /dev/null
+++ b/templates/economy_model_template.md
@@ -0,0 +1,15 @@
+# Purpose
+
+Model resources, progression, sinks, sources, pricing, and balance risks.
+
+# Inputs
+
+- Core loop, player rewards, currencies/resources, progression goals, and monetization constraints.
+
+# Outputs
+
+- Economy diagram/table, balance assumptions, tuning ranges, risks, and telemetry needs.
+
+# Validation
+
+- Model identifies exploits, runaway loops, grind risks, and validation scenarios.
diff --git a/templates/pitch_document_template.md b/templates/pitch_document_template.md
new file mode 100644
index 0000000..1c25112
--- /dev/null
+++ b/templates/pitch_document_template.md
@@ -0,0 +1,15 @@
+# Purpose
+
+Summarize a game concept for audience, differentiation, feasibility, and production promise.
+
+# Inputs
+
+- Concept, target audience, references, competitors, platform, genre, team capacity, and risks.
+
+# Outputs
+
+- Elevator pitch, pillars, differentiators, visual/audio hook, production scope, and validation asks.
+
+# Validation
+
+- Pitch is specific, falsifiable, and clear about prototype vs full-production promises.
diff --git a/templates/player_journey_template.md b/templates/player_journey_template.md
new file mode 100644
index 0000000..74df2b1
--- /dev/null
+++ b/templates/player_journey_template.md
@@ -0,0 +1,15 @@
+# Purpose
+
+Map the player journey across onboarding, motivation, friction, and retention beats.
+
+# Inputs
+
+- Target audience, fantasy, first-session goals, core loop, UI flows, and emotional beats.
+
+# Outputs
+
+- Journey stages, player questions, friction points, delight moments, and retention risks.
+
+# Validation
+
+- Journey identifies testable assumptions and moments requiring design or UX evidence.
diff --git a/templates/postmortem_template.md b/templates/postmortem_template.md
new file mode 100644
index 0000000..3ea4db1
--- /dev/null
+++ b/templates/postmortem_template.md
@@ -0,0 +1,15 @@
+# Purpose
+
+Capture production learning after a milestone, sprint, release, or incident.
+
+# Inputs
+
+- Goals, outcomes, shipped artifacts, metrics/evidence, team notes, and unresolved risks.
+
+# Outputs
+
+- What worked, what failed, root causes, decisions, and follow-up actions.
+
+# Validation
+
+- Follow-ups are assigned and separated from retrospective narrative.
diff --git a/templates/release_notes_template.md b/templates/release_notes_template.md
new file mode 100644
index 0000000..87b3568
--- /dev/null
+++ b/templates/release_notes_template.md
@@ -0,0 +1,15 @@
+# Purpose
+
+Prepare human-readable release notes for a build, milestone, or hotfix.
+
+# Inputs
+
+- Version/build, audience, highlights, fixes, known issues, compatibility, and validation status.
+
+# Outputs
+
+- Release summary, change list, known issues, upgrade notes, and support guidance.
+
+# Validation
+
+- Notes avoid unsupported claims and link known issues to owner or acceptance decisions.
diff --git a/templates/risk_register_template.md b/templates/risk_register_template.md
new file mode 100644
index 0000000..e07da01
--- /dev/null
+++ b/templates/risk_register_template.md
@@ -0,0 +1,15 @@
+# Purpose
+
+Track project, production, technical, release, and design risks.
+
+# Inputs
+
+- Current milestone, owner roles, dependencies, assumptions, known blockers, and external constraints.
+
+# Outputs
+
+- Risk table with impact, probability, mitigation, owner, trigger, and status.
+
+# Validation
+
+- High-impact risks have mitigation or explicit acceptance decisions.
diff --git a/templates/sound_bible_template.md b/templates/sound_bible_template.md
new file mode 100644
index 0000000..f7d179c
--- /dev/null
+++ b/templates/sound_bible_template.md
@@ -0,0 +1,15 @@
+# Purpose
+
+Define the audio production bible for music, SFX, voice, and mix consistency.
+
+# Inputs
+
+- Audio pillars, references, gameplay states, accessibility needs, and engine constraints.
+
+# Outputs
+
+- Music direction, SFX taxonomy, voice/subtitle notes, mix rules, and risks.
+
+# Validation
+
+- Audio rules are tied to gameplay feedback and validation scenarios.
diff --git a/templates/sprint_plan_template.md b/templates/sprint_plan_template.md
new file mode 100644
index 0000000..de8d342
--- /dev/null
+++ b/templates/sprint_plan_template.md
@@ -0,0 +1,15 @@
+# Purpose
+
+Plan a bounded sprint or iteration for game production.
+
+# Inputs
+
+- Milestone goal, available contributors, open risks, backlog candidates, and validation needs.
+
+# Outputs
+
+- Committed goals, stories, owners, non-goals, risks, and verification gates.
+
+# Validation
+
+- Commitments are small enough to validate within the iteration.
diff --git a/templates/technical_design_template.md b/templates/technical_design_template.md
new file mode 100644
index 0000000..2ccb9ad
--- /dev/null
+++ b/templates/technical_design_template.md
@@ -0,0 +1,15 @@
+# Purpose
+
+Describe a bounded technical design for a game feature or system.
+
+# Inputs
+
+- Feature goal, existing files, engine constraints, API/data requirements, and risks.
+
+# Outputs
+
+- Component design, data flow, integration notes, and test strategy.
+
+# Validation
+
+- Design names failure modes, validation commands, and rollback or simplification path.
diff --git a/templates/test_evidence_template.md b/templates/test_evidence_template.md
new file mode 100644
index 0000000..c33353d
--- /dev/null
+++ b/templates/test_evidence_template.md
@@ -0,0 +1,15 @@
+# Purpose
+
+Record executed validation evidence and follow-up actions.
+
+# Inputs
+
+- Test plan, build/version, commands run, manual scenarios, and artifact links or paths.
+
+# Outputs
+
+- Pass/fail table, defects found, blockers, warnings, and next owners.
+
+# Validation
+
+- Evidence distinguishes observed results from intended or unrun checks.
diff --git a/templates/test_plan_template.md b/templates/test_plan_template.md
new file mode 100644
index 0000000..cd1ab5c
--- /dev/null
+++ b/templates/test_plan_template.md
@@ -0,0 +1,15 @@
+# Purpose
+
+Plan QA coverage for gameplay, UI, engine integration, content, and release risks.
+
+# Inputs
+
+- Feature scope, risk areas, target builds, devices/platforms, and prior defects.
+
+# Outputs
+
+- Manual scenarios, automated checks, data needs, exit criteria, and owner assignments.
+
+# Validation
+
+- Plan covers positive, negative, regression, and release-critical paths.
diff --git a/templates/ux_spec_template.md b/templates/ux_spec_template.md
new file mode 100644
index 0000000..74f5b2b
--- /dev/null
+++ b/templates/ux_spec_template.md
@@ -0,0 +1,15 @@
+# Purpose
+
+Specify player-facing flows, screens, states, and interaction requirements.
+
+# Inputs
+
+- Player goals, target screens, control scheme, user journeys, and edge cases.
+
+# Outputs
+
+- Flow map, screen states, error states, copy needs, and usability risks.
+
+# Validation
+
+- Each flow has acceptance criteria and at least one usability/accessibility check.
diff --git a/templates/vertical_slice_report_template.md b/templates/vertical_slice_report_template.md
new file mode 100644
index 0000000..b7df410
--- /dev/null
+++ b/templates/vertical_slice_report_template.md
@@ -0,0 +1,15 @@
+# Purpose
+
+Report the state of a playable vertical slice or prototype.
+
+# Inputs
+
+- Slice goal, target loop, implemented artifacts, build status, and playtest evidence.
+
+# Outputs
+
+- Completed scope, missing scope, risks, validation results, and next-slice recommendations.
+
+# Validation
+
+- Report distinguishes playable evidence from plans or aspirational scope.
diff --git a/tests/agents-templates.test.ts b/tests/agents-templates.test.ts
index a5c3701..7f2bfd2 100644
--- a/tests/agents-templates.test.ts
+++ b/tests/agents-templates.test.ts
@@ -27,20 +27,43 @@ describe("config, agents, and templates", () => {
     expect(validateBaseAgents()).toEqual([]);
     expect(validateTemplateFiles()).toEqual([]);
     expect(listTemplates().map((t) => t.id).sort()).toEqual([
+      "accessibility_requirements",
+      "adr",
       "analytics_setup",
+      "architecture_traceability",
+      "art_bible",
       "art_direction",
+      "difficulty_curve",
+      "economy_model",
       "engine_setup",
       "feature_spec",
       "game_feel_tuning",
       "gdd",
       "handoff",
       "market_analysis",
+      "pitch_document",
+      "player_journey",
       "playtest_report",
+      "postmortem",
       "production_milestone",
       "project_config",
+      "release_notes",
+      "risk_register",
       "ship_check",
-      "ui_ux_review"
+      "sound_bible",
+      "sprint_plan",
+      "technical_design",
+      "test_evidence",
+      "test_plan",
+      "ui_ux_review",
+      "ux_spec",
+      "vertical_slice_report"
     ]);
+    for (const template of listTemplates()) {
+      expect(template.description.length).toBeGreaterThan(20);
+      expect(template.roles.length).toBeGreaterThan(0);
+      expect(template.workflows.length).toBeGreaterThan(0);
+    }
   });
 
   test("template selection is bounded", () => {
@@ -49,7 +72,11 @@ describe("config, agents, and templates", () => {
     expect(selectTemplates("qa-playtester", "Review validation readiness")).toEqual(["playtest_report"]);
     expect(selectTemplates("producer", "handoff coordination")).toEqual(["handoff"]);
     expect(selectTemplates("qa-playtester", "Review UI usability")).toEqual(["playtest_report", "ui_ux_review"]);
-    expect(selectTemplates("release-manager", "Check package")).toEqual(["ship_check"]);
+    expect(selectTemplates("release-manager", "Check package")).toEqual(["ship_check", "release_notes"]);
+    expect(selectTemplates("technical-director", "Draft architecture decision and technical design")).toEqual(["adr", "technical_design", "architecture_traceability"]);
+    expect(selectTemplates("audio-director", "Create sound bible for audio style")).toEqual(["sound_bible"]);
+    expect(selectTemplates("accessibility-specialist", "Define accessibility requirements")).toEqual(["accessibility_requirements"]);
+    expect(selectTemplates("producer", "Plan sprint risks and release notes")).toEqual(["sprint_plan", "release_notes", "ship_check", "risk_register"]);
   });
 
   test("template show includes discoverability metadata before body", () => {
@@ -57,7 +84,9 @@ describe("config, agents, and templates", () => {
     expect(output).toContain("ID: gdd");
     expect(output).toContain("Category: design");
     expect(output).toContain("Path: templates/gdd_template.md");
+    expect(output).toContain("Description:");
     expect(output).toContain("Roles: game-designer, creative-director");
+    expect(output).toContain("Workflows:");
     expect(output).toContain("# Purpose");
   });
 
@@ -67,17 +96,46 @@ describe("config, agents, and templates", () => {
     const gameplay = renderProjectRolePrompt("gameplay-programmer", unity, engines);
 
     expect(gameplay).toContain("docs/engine-reference/unity/VERSION.md");
+    expect(gameplay).toContain("docs/engine-reference/unity/current-best-practices.md");
     expect(gameplay).toContain("docs/engine-reference/unity/gameplay.md");
+    expect(gameplay).not.toContain("docs/engine-reference/unity/modules/audio.md");
     expect(gameplay).not.toContain("docs/engine-reference/unreal/");
 
     expect(studioRoleIds).toContain("godot-specialist");
     const godot = defaultProjectConfig({ name: "Godot Specialist Game", engine: "godot", mode: "prototype", nonInteractive: true });
     const specialist = renderProjectRolePrompt("godot-specialist", godot, engines);
     expect(specialist).toContain("docs/engine-reference/godot/VERSION.md");
+    expect(specialist).toContain("docs/engine-reference/godot/current-best-practices.md");
     expect(specialist).toContain("docs/engine-reference/godot/specialist.md");
+    expect(specialist).not.toContain("docs/engine-reference/godot/modules/audio.md");
     expect(specialist).not.toContain("docs/engine-reference/unity/");
   });
 
+  test("generated project role prompts render structured contracts and stay bounded", () => {
+    const engines = loadEngineConfigs(packageAssetPath("engine_configs"));
+    const config = defaultProjectConfig({ name: "Prompt Depth Game", engine: "godot", mode: "development", nonInteractive: true });
+    const release = renderProjectRolePrompt("release-manager", config, engines);
+
+    for (const section of [
+      "## Responsibilities",
+      "## Inputs To Inspect",
+      "## Output Format",
+      "## Quality Gates",
+      "## Collaboration Notes",
+      "## Stop Conditions"
+    ]) {
+      expect(release).toContain(section);
+    }
+    expect(release).toContain("Release decision");
+    expect(release).toContain("Blocking issues");
+    expect(release).toContain("Validation evidence");
+    expect(release).toContain("Stop and report a blocker");
+    expect(release.length).toBeLessThan(15000);
+    expect(release).not.toContain("# Gameplay Programmer");
+    expect(release).not.toContain("templates/gdd_template.md");
+    expect(release).not.toContain("docs/engine-reference/unity/");
+  });
+
   test("generated project prompts and AGENTS.md include only the active engine specialist", () => {
     const cwd = mkdtempSync(path.join(tmpdir(), "ogs-specialist-"));
     const { projectRoot } = initProject({ name: "Godot Prompt Scope", engine: "godot", mode: "prototype", nonInteractive: true }, cwd);
diff --git a/tests/behavioral-evaluation.test.ts b/tests/behavioral-evaluation.test.ts
new file mode 100644
index 0000000..030e3d3
--- /dev/null
+++ b/tests/behavioral-evaluation.test.ts
@@ -0,0 +1,66 @@
+import { describe, expect, test } from "vitest";
+import { mkdtempSync } from "node:fs";
+import { tmpdir } from "node:os";
+import path from "node:path";
+import { behavioralEvaluationScenarios, evaluateBehavioralScenario, runBehavioralEvaluations } from "../src/behavioral-evaluation.js";
+import { initProject } from "../src/projects.js";
+
+const scenarioIds = behavioralEvaluationScenarios.map((scenario) => scenario.id);
+
+describe("behavioral evaluation", () => {
+  test("defines deterministic local representative scenarios", () => {
+    expect(scenarioIds).toEqual([
+      "role.gameplay-programmer.contract",
+      "role.qa-playtester.contract",
+      "role.release-manager.contract",
+      "workflow.ship-check.release-readiness",
+      "workflow.playtest.issue-evidence",
+      "workflow.market-analysis.positioning"
+    ]);
+    for (const scenario of behavioralEvaluationScenarios) {
+      expect(scenario.requiredPhrases.length).toBeGreaterThan(0);
+      expect(scenario.forbiddenPhrases).toEqual(expect.arrayContaining(["CODEX.md", "telemetry", "hidden memory"]));
+      expect(scenario.expectedContextCategories.length).toBeGreaterThan(0);
+    }
+  });
+
+  test("built-in role contract scenarios pass without hosted evaluators", () => {
+    const results = runBehavioralEvaluations().filter((result) => result.id.startsWith("role."));
+    expect(results).toHaveLength(3);
+    for (const result of results) {
+      expect(result.status).toBe("pass");
+      expect(result.localDeterministic).toBe(true);
+      expect(result.usesHostedEvaluator).toBe(false);
+      expect(result.usesLlmCall).toBe(false);
+      expect(result.missingRequiredPhrases).toEqual([]);
+      expect(result.presentForbiddenPhrases).toEqual([]);
+      expect(result.promptLength).toBeGreaterThan(500);
+    }
+  });
+
+  test("workflow scenarios pass against generated project prompts and selected templates", () => {
+    const cwd = mkdtempSync(path.join(tmpdir(), "ogs-behavioral-"));
+    const { projectRoot } = initProject({ name: "Behavioral Game", engine: "godot", mode: "development", nonInteractive: true }, cwd);
+    const results = runBehavioralEvaluations({ projectRoot }).filter((result) => result.id.startsWith("workflow."));
+    expect(results).toHaveLength(3);
+    for (const result of results) {
+      expect(result.status).toBe("pass");
+      expect(result.missingRequiredPhrases).toEqual([]);
+      expect(result.missingContextCategories).toEqual([]);
+      expect(result.missingTemplateIds).toEqual([]);
+      expect(result.presentForbiddenTemplateIds).toEqual([]);
+      expect(result.presentForbiddenPhrases).toEqual([]);
+    }
+  });
+
+  test("negative checks fail when required text is missing or forbidden drift appears", () => {
+    const scenario = behavioralEvaluationScenarios[0];
+    const missing = evaluateBehavioralScenario({ ...scenario, requiredPhrases: ["this phrase is intentionally absent"] });
+    expect(missing.status).toBe("fail");
+    expect(missing.missingRequiredPhrases).toEqual(["this phrase is intentionally absent"]);
+
+    const forbidden = evaluateBehavioralScenario({ ...scenario, forbiddenPhrases: ["Role: Gameplay Programmer"] });
+    expect(forbidden.status).toBe("fail");
+    expect(forbidden.presentForbiddenPhrases).toEqual(["Role: Gameplay Programmer"]);
+  });
+});
diff --git a/tests/codex-context-files.test.ts b/tests/codex-context-files.test.ts
index cd3464a..ac97cf5 100644
--- a/tests/codex-context-files.test.ts
+++ b/tests/codex-context-files.test.ts
@@ -162,7 +162,24 @@ describe("Codex context files", () => {
 
     const sources = manifest.manifest.entries.map((entry) => entry.sourcePath);
     expect(sources).toContain("docs/engine-reference/unity/VERSION.md");
+    expect(sources).toContain("docs/engine-reference/unity/current-best-practices.md");
     expect(sources).toContain("docs/engine-reference/unity/gameplay.md");
     expect(sources.some((source) => source.startsWith("docs/engine-reference/unreal/"))).toBe(false);
   });
+
+  test("role runs and workflow prompts select task-relevant engine references without broad loading", () => {
+    const cwd = mkdtempSync(path.join(tmpdir(), "ogs-context-engine-task-"));
+    const { projectRoot } = initProject({ name: "Godot Netcode Game", engine: "godot", mode: "prototype", nonInteractive: true }, cwd);
+
+    const run = prepareRun("gameplay-programmer", { project: projectRoot, task: "Implement rollback networking input sync", printPrompt: true }, cwd);
+    expect(run.contextFiles).toContain("docs/engine-reference/godot/modules/networking.md");
+    expect(run.contextFiles).toContain("docs/engine-reference/godot/modules/input.md");
+    expect(run.contextFiles).not.toContain("docs/engine-reference/godot/modules/audio.md");
+    expect(run.contextFiles.some((source) => source.startsWith("docs/engine-reference/unity/"))).toBe(false);
+
+    const workflow = renderWorkflowPrompt(projectRoot, "bugfix");
+    expect(workflow).toContain("docs/engine-reference/godot/current-best-practices.md");
+    expect(workflow).not.toContain("docs/engine-reference/godot/modules/audio.md");
+  });
+
 });
diff --git a/tests/codex-prompts.test.ts b/tests/codex-prompts.test.ts
index 219f08d..17a4584 100644
--- a/tests/codex-prompts.test.ts
+++ b/tests/codex-prompts.test.ts
@@ -15,6 +15,8 @@ describe("Codex prompt renderer", () => {
     });
     const prompt = renderCodexPrompt(session);
     expect(prompt).toContain("Role: Gameplay Programmer");
+    expect(prompt).toContain("Role ID: gameplay-programmer");
+    expect(prompt).toContain("Context Strategy: focused");
     expect(prompt).toContain("Objective: Implement movement");
     expect(prompt).toContain("Phase: implement");
     expect(prompt).toContain("AGENTS.md");
@@ -26,4 +28,33 @@ describe("Codex prompt renderer", () => {
     expect(prompt).toContain("changed files");
     expect(prompt).toContain("verification results");
   });
+
+  test("renders structured role contract sections without broad prompt bloat", () => {
+    const session = createCodexStudioSession({
+      projectRoot: "/repo/projects/ship-game",
+      role: "release-manager",
+      objective: "Prepare release checklist",
+      phase: "review",
+      engine: "unity",
+      contextFiles: ["AGENTS.md", ".codex/studio.json", "docs/engine-reference/unity/VERSION.md"]
+    });
+
+    const prompt = renderCodexPrompt(session);
+
+    expect(prompt).toContain("## Responsibilities");
+    expect(prompt).toContain("## Inputs To Inspect");
+    expect(prompt).toContain("## Output Format");
+    expect(prompt).toContain("## Quality Gates");
+    expect(prompt).toContain("## Collaboration Notes");
+    expect(prompt).toContain("## Stop Conditions");
+    expect(prompt).toContain("Release decision");
+    expect(prompt).toContain("Blocking issues");
+    expect(prompt).toContain("Validation evidence");
+    expect(prompt).toContain("Stop and report a blocker");
+    expect(prompt.length).toBeLessThan(12000);
+    expect(prompt).not.toContain("# Gameplay Programmer");
+    expect(prompt).not.toContain("# QA Playtester");
+    expect(prompt).not.toContain("templates/gdd_template.md");
+    expect(prompt).not.toContain("docs/engine-reference/unreal/");
+  });
 });
diff --git a/tests/customization.test.ts b/tests/customization.test.ts
new file mode 100644
index 0000000..9e09c7f
--- /dev/null
+++ b/tests/customization.test.ts
@@ -0,0 +1,134 @@
+import { existsSync, mkdirSync, readFileSync, writeFileSync } from "node:fs";
+import { execFileSync } from "node:child_process";
+import { mkdtempSync } from "node:fs";
+import { tmpdir } from "node:os";
+import path from "node:path";
+import { describe, expect, test } from "vitest";
+import { customizationConfigPath, readProjectCustomization } from "../src/customization.js";
+import { initProject, statusProject } from "../src/projects.js";
+import { prepareRun } from "../src/runner.js";
+import { formatTemplateShow, listTemplates } from "../src/templates.js";
+import { validateProject } from "../src/validation.js";
+import { renderWorkflowPrompt } from "../src/workflows.js";
+
+function writeValidCustomPack(projectRoot: string): void {
+  mkdirSync(path.join(projectRoot, ".codex", "custom", "roles"), { recursive: true });
+  mkdirSync(path.join(projectRoot, "documentation", "templates"), { recursive: true });
+  writeFileSync(path.join(projectRoot, ".codex", "custom", "roles", "boss-designer.md"), "# Boss Designer Prompt\n\nDesign readable boss fights with phases, tells, counters, accessibility notes, and verification gates.\n");
+  writeFileSync(path.join(projectRoot, "documentation", "templates", "boss-brief.md"), "# Purpose\n\nCapture a boss encounter brief.\n\n# Inputs\n\nProject fantasy and combat constraints.\n\n# Outputs\n\nPhases, tells, counters, risks, and tests.\n\n# Validation\n\nPlaytest the encounter for readability.\n");
+  writeFileSync(
+    customizationConfigPath(projectRoot),
+    `${JSON.stringify(
+      {
+        schemaVersion: 1,
+        policy: { merge: "extend-only" },
+        roles: [
+          {
+            id: "custom-boss-designer",
+            displayName: "Boss Designer",
+            promptFile: ".codex/custom/roles/boss-designer.md",
+            contextStrategy: "focused",
+            phase: "plan",
+            expectedOutputs: ["Boss encounter brief", "Readability risks", "Playtest checks"],
+            reviewChecklist: ["Boss phases are readable", "Counterplay is explicit", "Verification is concrete"]
+          }
+        ],
+        templates: [
+          {
+            id: "custom-boss-brief",
+            category: "design",
+            path: "documentation/templates/boss-brief.md",
+            description: "Project-local boss encounter brief template.",
+            roles: ["custom-boss-designer"],
+            workflows: ["custom-boss-review"],
+            tags: ["boss", "encounter", "custom"],
+            requiredSections: ["# Purpose", "# Inputs", "# Outputs", "# Validation"]
+          }
+        ],
+        workflows: [
+          {
+            id: "custom-boss-review",
+            role: "custom-boss-designer",
+            phase: "plan",
+            objective: "Draft or review a boss encounter for readable phases, counterplay, accessibility, and test evidence.",
+            file: ".codex/workflows/custom-boss-review.md",
+            contextFiles: ["AGENTS.md", ".codex/studio.json", ".codex/custom/roles/boss-designer.md"],
+            templateIds: ["custom-boss-brief"],
+            aliases: ["boss-review"]
+          }
+        ]
+      },
+      null,
+      2
+    )}\n`
+  );
+}
+
+describe("project-local customization packs", () => {
+  test("init seeds a reviewable customization config and status summarizes it", () => {
+    const cwd = mkdtempSync(path.join(tmpdir(), "ogs-custom-init-"));
+    const { projectRoot } = initProject({ name: "Custom Seed", engine: "godot", mode: "prototype", nonInteractive: true }, cwd);
+    expect(existsSync(customizationConfigPath(projectRoot))).toBe(true);
+    expect(readProjectCustomization(projectRoot)).toMatchObject({ schemaVersion: 1, roles: [], workflows: [], templates: [], policy: { merge: "extend-only" } });
+    expect(statusProject(projectRoot, cwd)).toContain("custom roles: 0, workflows: 0, templates: 0");
+    expect(validateProject(projectRoot)).toContainEqual(expect.objectContaining({ id: "codex.customization.config", status: "pass" }));
+  });
+
+  test("valid local role workflow and template packs merge with built-ins without loading broad context", () => {
+    const cwd = mkdtempSync(path.join(tmpdir(), "ogs-custom-valid-"));
+    const { projectRoot } = initProject({ name: "Boss Game", engine: "godot", mode: "development", nonInteractive: true }, cwd);
+    writeValidCustomPack(projectRoot);
+    const checks = validateProject(projectRoot);
+    expect(checks).toContainEqual(expect.objectContaining({ id: "codex.customization.role.custom-boss-designer", status: "pass" }));
+    expect(checks).toContainEqual(expect.objectContaining({ id: "codex.customization.workflow.custom-boss-review", status: "pass" }));
+    expect(checks).toContainEqual(expect.objectContaining({ id: "codex.customization.template.custom-boss-brief", status: "pass" }));
+    expect(checks.filter((check) => check.id.startsWith("codex.customization") && check.status === "fail")).toEqual([]);
+    expect(listTemplates(projectRoot).map((template) => template.id)).toContain("custom-boss-brief");
+    expect(formatTemplateShow("custom-boss-brief", { projectRoot })).toContain("Project-local boss encounter brief template");
+    const workflowPrompt = renderWorkflowPrompt(projectRoot, "custom-boss-review");
+    expect(workflowPrompt).toContain("Boss Designer");
+    expect(workflowPrompt).toContain("Draft or review a boss encounter");
+    expect(workflowPrompt).toContain("Template: custom-boss-brief");
+    expect(workflowPrompt).not.toContain("Template: market_analysis");
+    const run = prepareRun("custom-boss-designer", { project: projectRoot, task: "Draft a boss fight brief with phase readability", printPrompt: true }, cwd);
+    expect(run.output).toContain("Role: Boss Designer");
+    expect(run.output).toContain("Role ID: custom-boss-designer");
+    expect(run.output).toContain("Boss Designer Prompt");
+    expect(run.output).toContain("Template: custom-boss-brief");
+  });
+
+  test("customization validation rejects unsafe paths and built-in id conflicts", () => {
+    const cwd = mkdtempSync(path.join(tmpdir(), "ogs-custom-invalid-"));
+    const { projectRoot } = initProject({ name: "Invalid Custom", engine: "godot", mode: "prototype", nonInteractive: true }, cwd);
+    writeFileSync(
+      customizationConfigPath(projectRoot),
+      `${JSON.stringify(
+        {
+          schemaVersion: 1,
+          policy: { merge: "extend-only" },
+          roles: [{ id: "producer", displayName: "Producer Override", promptFile: ".codex/custom/roles/producer.md", contextStrategy: "focused", phase: "plan", expectedOutputs: ["Override"], reviewChecklist: ["Override"] }],
+          templates: [{ id: "custom-escape-template", category: "design", path: "../escape.md", description: "Unsafe template path.", roles: ["producer"], workflows: ["vertical-slice"], tags: ["unsafe"], requiredSections: ["# Purpose"] }],
+          workflows: []
+        },
+        null,
+        2
+      )}\n`
+    );
+    const failures = validateProject(projectRoot).filter((check) => check.id.startsWith("codex.customization") && check.status === "fail");
+    expect(failures.map((failure) => failure.id)).toEqual(expect.arrayContaining(["codex.customization.role.producer", "codex.customization.template.custom-escape-template"]));
+    expect(failures.map((failure) => failure.message).join("\n")).toMatch(/built-in|escape|project root/i);
+  });
+
+  test("CLI templates and workflow commands can inspect project-local packs", () => {
+    const cwd = mkdtempSync(path.join(tmpdir(), "ogs-custom-cli-"));
+    const { projectRoot } = initProject({ name: "CLI Custom", engine: "godot", mode: "prototype", nonInteractive: true }, cwd);
+    writeValidCustomPack(projectRoot);
+    const cli = path.join(process.cwd(), "src", "cli.ts");
+    const tsx = path.join(process.cwd(), "node_modules", ".bin", "tsx");
+    const templates = execFileSync(tsx, [cli, "templates", "list", "--project", projectRoot], { cwd, encoding: "utf8" });
+    expect(templates).toContain("custom-boss-brief");
+    const workflow = execFileSync(tsx, [cli, "workflow", "custom-boss-review", "--project", projectRoot, "--dry-run"], { cwd, encoding: "utf8" });
+    expect(workflow).toContain("Boss Designer");
+    expect(workflow).toContain("Template: custom-boss-brief");
+  });
+});
diff --git a/tests/engine-system.test.ts b/tests/engine-system.test.ts
index ced9be7..d29cf42 100644
--- a/tests/engine-system.test.ts
+++ b/tests/engine-system.test.ts
@@ -50,12 +50,23 @@ describe("engine registry", () => {
     for (const [engine, pack] of Object.entries(engineReferenceRegistry)) {
       expect(pack.packageRoot).toBe(`engine_reference/${engine}`);
       expect(pack.projectRoot).toBe(`docs/engine-reference/${engine}`);
-      expect(pack.requiredFiles).toContain("VERSION.md");
+      expect(pack.requiredFiles).toEqual(expect.arrayContaining(["VERSION.md", "current-best-practices.md", "deprecated-apis.md", "breaking-changes.md", "gameplay.md", "specialist.md"]));
+      expect(pack.moduleFiles).toEqual([
+        "modules/animation.md",
+        "modules/audio.md",
+        "modules/input.md",
+        "modules/navigation.md",
+        "modules/networking.md",
+        "modules/physics.md",
+        "modules/rendering.md",
+        "modules/ui.md"
+      ]);
       expect(pack.promptReferences.some((reference) => reference.path === "VERSION.md" && reference.required)).toBe(true);
-      for (const file of pack.requiredFiles) {
+      expect(pack.promptReferences.some((reference) => reference.path === "current-best-practices.md" && reference.required)).toBe(true);
+      for (const file of [...pack.requiredFiles, ...pack.moduleFiles, ...pack.pluginFiles]) {
         expect(pack.projectPath(file)).toBe(`docs/engine-reference/${engine}/${file}`);
       }
-      expect(pack.validation.requiredMetadata).toEqual(["reviewer", "date", "source-link"]);
+      expect(pack.validation.requiredMetadata).toEqual(["reviewer", "date", "source-link", "engine", "version-reviewed", "tags", "roles", "workflows"]);
       expect(pack.packageSmokeFiles.length).toBeGreaterThan(0);
     }
   });
@@ -64,8 +75,8 @@ describe("engine registry", () => {
     const checks = validateEngineReferencePacks(packageAssetPath("."));
     expect(checks.filter((check) => check.status === "fail")).toEqual([]);
     expect(checks).toContainEqual(expect.objectContaining({ id: "engine_reference.godot.VERSION.md.metadata", status: "pass" }));
-    expect(checks).toContainEqual(expect.objectContaining({ id: "engine_reference.unity.VERSION.md.metadata", status: "pass" }));
-    expect(checks).toContainEqual(expect.objectContaining({ id: "engine_reference.unreal.VERSION.md.metadata", status: "pass" }));
+    expect(checks).toContainEqual(expect.objectContaining({ id: "engine_reference.unity.modules/networking.md.metadata", status: "pass" }));
+    expect(checks).toContainEqual(expect.objectContaining({ id: "engine_reference.unreal.plugins/gas.md.metadata", status: "pass" }));
   });
 
   test("engine reference assets are included in npm pack", () => {
@@ -73,9 +84,11 @@ describe("engine registry", () => {
     const packInfo = JSON.parse(raw)[0] as { filename: string; files: { path: string }[] };
     try {
       const packed = new Set(packInfo.files.map((file) => file.path));
-      expect(packed.has("engine_reference/godot/VERSION.md")).toBe(true);
-      expect(packed.has("engine_reference/unity/VERSION.md")).toBe(true);
-      expect(packed.has("engine_reference/unreal/VERSION.md")).toBe(true);
+      for (const pack of Object.values(engineReferenceRegistry)) {
+        for (const file of [...pack.requiredFiles, ...pack.moduleFiles, ...pack.pluginFiles, ...pack.specialistFiles]) {
+          expect(packed.has(`${pack.packageRoot}/${file}`)).toBe(true);
+        }
+      }
     } finally {
       unlinkSync(path.join(process.cwd(), packInfo.filename));
     }
diff --git a/tests/functionality-gap-pass.test.ts b/tests/functionality-gap-pass.test.ts
index 2e0a059..b4ed64c 100644
--- a/tests/functionality-gap-pass.test.ts
+++ b/tests/functionality-gap-pass.test.ts
@@ -8,7 +8,7 @@ import { initProject, statusProject } from "../src/projects.js";
 import { projectRoleIdsForEngine, rolePackages, studioRoleIds } from "../src/roles.js";
 import { readTemplate, templateRegistry } from "../src/templates.js";
 import { validateProject } from "../src/validation.js";
-import { renderWorkflowPrompt, workflowRegistry } from "../src/workflows.js";
+import { renderWorkflowPrompt, workflowAliases, workflowRegistry } from "../src/workflows.js";
 
 const requiredRoles = [
   "studio-orchestrator",
@@ -19,18 +19,70 @@ const requiredRoles = [
   "senior-game-designer",
   "game-designer",
   "narrative-designer",
+  "writer",
+  "world-builder",
+  "level-designer",
   "game-feel-designer",
+  "systems-designer",
+  "economy-designer",
   "gameplay-programmer",
+  "ai-programmer",
+  "network-programmer",
+  "ui-programmer",
   "engine-programmer",
   "godot-specialist",
   "unity-specialist",
   "unreal-specialist",
   "tools-programmer",
+  "technical-director",
+  "devops-engineer",
+  "security-engineer",
+  "performance-analyst",
   "senior-game-artist",
   "technical-artist",
+  "audio-director",
+  "sound-designer",
   "ui-ux-designer",
+  "accessibility-specialist",
   "qa-playtester",
+  "localization-lead",
+  "live-ops-designer",
+  "community-manager",
   "release-manager"
+ ] as const;
+
+const requiredWorkflowIds = [
+  "vertical-slice",
+  "bugfix",
+  "playtest",
+  "market-analysis",
+  "analytics-setup",
+  "design-spec",
+  "game-feel-tuning",
+  "art-direction",
+  "ui-ux-review",
+  "production-milestone",
+  "handoff",
+  "review",
+  "ship-check",
+  "onboard",
+  "brainstorm",
+  "prototype",
+  "architecture-decision",
+  "architecture-review",
+  "create-epics",
+  "create-stories",
+  "sprint-plan",
+  "sprint-status",
+  "story-readiness",
+  "story-done",
+  "qa-plan",
+  "regression-suite",
+  "security-audit",
+  "perf-profile",
+  "release-checklist",
+  "hotfix",
+  "localization-plan"
 ] as const;
 
 describe("functionality gap pass", () => {
@@ -46,6 +98,23 @@ describe("functionality gap pass", () => {
     expect(studioRoleIds).not.toContain("master_orchestrator");
   });
 
+  it("exposes a curated prompt-only workflow catalog", () => {
+    expect(Object.keys(workflowRegistry)).toEqual(requiredWorkflowIds);
+    const categories = new Map(Object.values(workflowRegistry).map((workflow) => [workflow.id, workflow.category]));
+    expect(new Set(categories.values())).toEqual(
+      new Set(["onboarding-discovery", "design-architecture", "implementation-planning", "qa-testing", "release-hotfix", "localization-accessibility", "team-coordination"])
+    );
+
+    for (const workflow of Object.values(workflowRegistry)) {
+      expect(workflow.gapCoverage.length).toBeGreaterThan(0);
+      expect(workflow.file).toBe(`.codex/workflows/${workflow.id}.md`);
+    }
+
+    expect(workflowAliases(workflowRegistry.onboard)).toEqual(expect.arrayContaining(["start", "onboard"]));
+    expect(workflowAliases(workflowRegistry["release-checklist"])).toEqual(expect.arrayContaining(["release-checklist"]));
+    expect(workflowRegistry.hotfix.phase).toBe("review");
+  });
+
   it("selects market, analytics, orchestration, and mode-specific roles", () => {
     for (const mode of ["design", "prototype", "development"] as const) {
       expect(activeAgentsForMode(mode)).toEqual(
@@ -54,13 +123,43 @@ describe("functionality gap pass", () => {
     }
 
     expect(activeAgentsForMode("design")).toEqual(
-      expect.arrayContaining(["creative-director", "senior-game-designer", "game-designer", "narrative-designer", "senior-game-artist", "ui-ux-designer"])
+      expect.arrayContaining([
+        "creative-director",
+        "senior-game-designer",
+        "game-designer",
+        "narrative-designer",
+        "writer",
+        "world-builder",
+        "level-designer",
+        "systems-designer",
+        "economy-designer",
+        "audio-director",
+        "senior-game-artist",
+        "ui-ux-designer",
+        "accessibility-specialist"
+      ])
     );
     expect(activeAgentsForMode("prototype")).toEqual(
-      expect.arrayContaining(["senior-game-designer", "game-feel-designer", "gameplay-programmer", "qa-playtester"])
+      expect.arrayContaining(["senior-game-designer", "systems-designer", "level-designer", "game-feel-designer", "gameplay-programmer", "ui-programmer", "sound-designer", "qa-playtester", "accessibility-specialist"])
     );
     expect(activeAgentsForMode("development")).toEqual(
-      expect.arrayContaining(["game-feel-designer", "engine-programmer", "tools-programmer", "technical-artist", "ui-ux-designer", "release-manager"])
+      expect.arrayContaining([
+        "technical-director",
+        "game-feel-designer",
+        "engine-programmer",
+        "tools-programmer",
+        "ai-programmer",
+        "network-programmer",
+        "ui-programmer",
+        "devops-engineer",
+        "security-engineer",
+        "performance-analyst",
+        "technical-artist",
+        "localization-lead",
+        "live-ops-designer",
+        "community-manager",
+        "release-manager"
+      ])
     );
   });
 
@@ -89,6 +188,12 @@ describe("functionality gap pass", () => {
     expect(promptBody).toContain("source-input-sha256");
     expect(promptBody).toContain("rendered-body-sha256");
 
+    const networkPromptBody = readFileSync(path.join(projectRoot, ".codex", "prompts", "network-programmer.md"), "utf8");
+    expect(networkPromptBody).toContain("Role: Network Programmer");
+    expect(networkPromptBody).toContain("Context Strategy: broad");
+    expect(networkPromptBody).toContain("Expected Outputs");
+    expect(networkPromptBody).toContain("Review Checklist");
+
     for (const workflow of Object.keys(workflowRegistry)) {
       expect(existsSync(path.join(projectRoot, workflowRegistry[workflow as keyof typeof workflowRegistry].file))).toBe(true);
       expect(renderWorkflowPrompt(projectRoot, workflow as keyof typeof workflowRegistry)).toContain(workflow);
@@ -96,6 +201,9 @@ describe("functionality gap pass", () => {
     const workflowBody = readFileSync(path.join(projectRoot, ".codex", "workflows", "ui-ux-review.md"), "utf8");
     expect(workflowBody).toContain("source-input-sha256");
     expect(workflowBody).toContain("rendered-body-sha256");
+    expect(workflowBody).toContain("## Taxonomy");
+    expect(readFileSync(path.join(projectRoot, ".codex", "workflows", "release-checklist.md"), "utf8")).toContain("release-hotfix");
+    expect(readFileSync(path.join(projectRoot, ".codex", "workflows", "localization-plan.md"), "utf8")).toContain("localization-accessibility");
     expect(existsSync(path.join(projectRoot, "project_orchestrator.md"))).toBe(false);
     expect(existsSync(path.join(projectRoot, "CODEX.md"))).toBe(false);
     expect(existsSync(path.join(projectRoot, ".gamestudio", "runs"))).toBe(false);
@@ -131,6 +239,24 @@ describe("functionality gap pass", () => {
     expect(renderWorkflowPrompt(projectRoot, "ui-ux-review")).toContain("Template: ui_ux_review");
     expect(renderWorkflowPrompt(projectRoot, "production-milestone")).toContain("Template: production_milestone");
     expect(renderWorkflowPrompt(projectRoot, "ship-check")).toContain("Template: ship_check");
+    expect(renderWorkflowPrompt(projectRoot, "ship-check")).toContain("Template: release_notes");
+    expect(renderWorkflowPrompt(projectRoot, "ship-check")).toContain("Template: risk_register");
+    const architectureDecision = renderWorkflowPrompt(projectRoot, "architecture-decision");
+    expect(architectureDecision).toContain("Template: adr");
+    expect(architectureDecision).toContain("Template: technical_design");
+    expect(architectureDecision).toContain("Template: architecture_traceability");
+    expect(architectureDecision).not.toContain("Template: art_bible");
+    const qaPlan = renderWorkflowPrompt(projectRoot, "qa-plan");
+    expect(qaPlan).toContain("Template: test_plan");
+    expect(qaPlan).toContain("Template: test_evidence");
+    expect(renderWorkflowPrompt(projectRoot, "sprint-plan")).toContain("Template: sprint_plan");
+    expect(renderWorkflowPrompt(projectRoot, "art-direction")).toContain("Template: art_bible");
+    expect(renderWorkflowPrompt(projectRoot, "localization-plan")).toContain("Template: accessibility_requirements");
+    expect(renderWorkflowPrompt(projectRoot, "prototype")).toContain("Template: vertical_slice_report");
+    expect(renderWorkflowPrompt(projectRoot, "brainstorm")).toContain("Template: pitch_document");
+    expect(renderWorkflowPrompt(projectRoot, "security-audit")).toContain("Security Engineer");
+    expect(renderWorkflowPrompt(projectRoot, "security-audit")).not.toContain("## Workflow Templates");
+    expect(renderWorkflowPrompt(projectRoot, "localization-plan")).toContain("Localization Lead");
     expect(renderWorkflowPrompt(projectRoot, "review")).not.toContain("## Workflow Templates");
     expect(renderWorkflowPrompt(projectRoot, "ui-ux-review")).not.toContain("Template: market_analysis");
     expect(renderWorkflowPrompt(projectRoot, "ship-check")).not.toContain("Template: analytics_setup");
@@ -143,18 +269,45 @@ describe("functionality gap pass", () => {
     const cli = path.join(process.cwd(), "src", "cli.ts");
     const tsx = path.join(process.cwd(), "node_modules", ".bin", "tsx");
     const help = execFileSync(tsx, [cli, "--help"], { encoding: "utf8" });
-    for (const alias of ["market", "analytics", "design-spec", "feel-review", "art-direction", "ui-review", "milestone", "handoff"]) {
+    for (const alias of [
+      "market",
+      "analytics",
+      "design-spec",
+      "feel-review",
+      "art-direction",
+      "ui-review",
+      "milestone",
+      "handoff",
+      "start",
+      "onboard",
+      "brainstorm",
+      "prototype",
+      "architecture-decision",
+      "architecture-review",
+      "create-epics",
+      "create-stories",
+      "sprint-plan",
+      "sprint-status",
+      "story-readiness",
+      "story-done",
+      "qa-plan",
+      "regression-suite",
+      "security-audit",
+      "perf-profile",
+      "release-checklist",
+      "hotfix",
+      "localization-plan"
+    ]) {
       expect(help).toContain(alias);
     }
-    expect(help).not.toMatch(/\bplan\b/);
     expect(help).not.toMatch(/\bnext\b/);
     expect(help).not.toMatch(/\btelemetry\b/);
     expect(help).not.toMatch(/\bparallel\b/);
 
     process.env.CODEX_BIN = "/missing/codex";
     try {
-      for (const workflow of Object.values(workflowRegistry).filter((entry) => entry.cliAlias)) {
-        for (const args of [[workflow.cliAlias!], [workflow.cliAlias!, "--dry-run"]]) {
+      for (const workflow of Object.values(workflowRegistry).filter((entry) => workflowAliases(entry).length > 0)) {
+        for (const alias of workflowAliases(workflow)) for (const args of [[alias], [alias, "--dry-run"]]) {
           const before = readdirSync(path.join(projectRoot, ".codex", "runs"));
           const output = execFileSync(tsx, [cli, ...args, "--project", projectRoot], { cwd, encoding: "utf8" });
           expect(output).toContain(`Role: ${rolePackages[workflow.role].displayName}`);
diff --git a/tests/roles.test.ts b/tests/roles.test.ts
index cfb93a9..10e0683 100644
--- a/tests/roles.test.ts
+++ b/tests/roles.test.ts
@@ -12,17 +12,35 @@ describe("Codex role packages", () => {
       "senior-game-designer",
       "game-designer",
       "narrative-designer",
+      "writer",
+      "world-builder",
+      "level-designer",
       "game-feel-designer",
+      "systems-designer",
+      "economy-designer",
       "gameplay-programmer",
+      "ai-programmer",
+      "network-programmer",
+      "ui-programmer",
       "engine-programmer",
       "godot-specialist",
       "unity-specialist",
       "unreal-specialist",
       "tools-programmer",
+      "technical-director",
+      "devops-engineer",
+      "security-engineer",
+      "performance-analyst",
       "senior-game-artist",
       "technical-artist",
+      "audio-director",
+      "sound-designer",
       "ui-ux-designer",
+      "accessibility-specialist",
       "qa-playtester",
+      "localization-lead",
+      "live-ops-designer",
+      "community-manager",
       "release-manager"
     ]);
     expect(Object.keys(rolePackages).sort()).toEqual([...studioRoleIds].sort());
@@ -38,6 +56,52 @@ describe("Codex role packages", () => {
     }
   });
 
+
+  test("role packages cover bounded specialist domain clusters", () => {
+    const clusters = {
+      audio: ["audio-director", "sound-designer"],
+      content: ["writer", "world-builder", "level-designer"],
+      systems: ["systems-designer", "economy-designer"],
+      operations: ["live-ops-designer", "community-manager", "localization-lead", "accessibility-specialist"],
+      technical: ["technical-director", "devops-engineer", "security-engineer", "performance-analyst", "network-programmer", "ai-programmer", "ui-programmer"]
+    } as const;
+
+    for (const roles of Object.values(clusters)) {
+      for (const role of roles) {
+        expect(studioRoleIds).toContain(role);
+        expect(rolePackages[role].expectedOutputs.length).toBeGreaterThanOrEqual(2);
+        expect(rolePackages[role].reviewChecklist.length).toBeGreaterThanOrEqual(2);
+      }
+    }
+
+    expect(rolePackages["audio-director"].systemPrompt).toContain("audio");
+    expect(rolePackages["network-programmer"].systemPrompt).toContain("network");
+    expect(rolePackages["accessibility-specialist"].systemPrompt).toContain("accessibility");
+  });
+
+
+
+  test("role packages expose structured compact role contracts", () => {
+    for (const role of Object.values(rolePackages)) {
+      expect(role.responsibilities.length).toBeGreaterThanOrEqual(2);
+      expect(role.inputsToInspect.length).toBeGreaterThanOrEqual(2);
+      expect(role.qualityGates.length).toBeGreaterThanOrEqual(2);
+      expect(role.stopConditions.length).toBeGreaterThanOrEqual(1);
+      expect(role.sharedFragments).toBeDefined();
+      expect(new Set(role.sharedFragments).size).toBe(role.sharedFragments.length);
+    }
+
+    expect(rolePackages["gameplay-programmer"].outputSchema).toEqual(
+      expect.arrayContaining(["Changed files", "Implementation notes", "Verification evidence", "Risks or follow-ups"])
+    );
+    expect(rolePackages["qa-playtester"].outputSchema).toEqual(
+      expect.arrayContaining(["Issue ID", "Severity", "Reproduction steps", "Expected result", "Actual result", "Evidence"])
+    );
+    expect(rolePackages["release-manager"].outputSchema).toEqual(
+      expect.arrayContaining(["Release decision", "Blocking issues", "Warnings", "Validation evidence", "Rollback notes"])
+    );
+  });
+
   test("legacy underscore aliases are rejected with guidance", () => {
     for (const alias of ["producer_agent", "qa_agent", "master_orchestrator"]) {
       expect(isStudioRoleId(alias)).toBe(false);
diff --git a/tests/validation.test.ts b/tests/validation.test.ts
index 2d849ca..d5a1344 100644
--- a/tests/validation.test.ts
+++ b/tests/validation.test.ts
@@ -12,6 +12,7 @@ import { hashGeneratedBody, stableHash, stripGeneratedMetadata } from "../src/ge
 import { loadEngineConfigs } from "../src/engines.js";
 import { engineReferenceRegistry } from "../src/engine-reference.js";
 import { rolePackages } from "../src/roles.js";
+import { behavioralEvaluationScenarios } from "../src/behavioral-evaluation.js";
 
 const validApprovalRecord = {
   id: "appr_test",
@@ -172,7 +173,7 @@ describe("validation", () => {
     const cwd = mkdtempSync(path.join(tmpdir(), "ogs-val-engine-reference-"));
     const { projectRoot } = initProject({ name: "Unity Reference Valid", engine: "unity", mode: "prototype", nonInteractive: true }, cwd);
 
-    for (const file of engineReferenceRegistry.unity.requiredFiles) {
+    for (const file of [...engineReferenceRegistry.unity.requiredFiles, ...engineReferenceRegistry.unity.moduleFiles, ...engineReferenceRegistry.unity.pluginFiles]) {
       expect(existsSync(path.join(projectRoot, engineReferenceRegistry.unity.projectPath(file)))).toBe(true);
     }
     expect(existsSync(path.join(projectRoot, "docs", "engine-reference", "unreal", "VERSION.md"))).toBe(false);
@@ -180,7 +181,9 @@ describe("validation", () => {
     const checks = validateProject(projectRoot);
     expect(checks.filter((c) => c.id.startsWith("engine_reference.") && c.status === "fail")).toEqual([]);
     expect(checks).toContainEqual(expect.objectContaining({ id: "engine_reference.package.unity.VERSION.md.metadata", status: "pass" }));
+    expect(checks).toContainEqual(expect.objectContaining({ id: "engine_reference.package.unity.modules/networking.md.metadata", status: "pass" }));
     expect(checks).toContainEqual(expect.objectContaining({ id: "engine_reference.project.unity.VERSION.md", status: "pass" }));
+    expect(checks).toContainEqual(expect.objectContaining({ id: "engine_reference.project.unity.modules/networking.md", status: "pass" }));
   });
 
   test("missing materialized engine reference fails project validation", () => {
@@ -300,6 +303,14 @@ describe("validation", () => {
     }
   });
 
+  test("repo validation includes deterministic behavioral evaluation subchecks", async () => {
+    const result = await runValidation();
+    const checks = result.checks.filter((check) => check.id.startsWith("behavioral.scenario."));
+
+    expect(checks.map((check) => check.id)).toEqual(behavioralEvaluationScenarios.map((scenario) => `behavioral.scenario.${scenario.id}`));
+    expect(checks.every((check) => check.status === "pass")).toBe(true);
+  });
+
   test("repo validation reports Codex readiness hard failure when unavailable", async () => {
     const old = process.env.CODEX_BIN;
     process.env.CODEX_BIN = "/missing/codex";