@orderful/droid 0.21.0 → 0.23.0

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # @orderful/droid
 
+## 0.23.0
+
+### Minor Changes
+
+- [#115](https://github.com/Orderful/droid/pull/115) [`fc2e182`](https://github.com/Orderful/droid/commit/fc2e18211136ef78f839394d322a1afaae54d2a7) Thanks [@frytyler](https://github.com/frytyler)! - feat(project): add --from codex:{name} to seed projects from shared context
+
+  New command syntax: `/project create --from codex:{name}` creates a personal project seeded with context from the shared organizational codex. Extracts overview from PRD, goals, and technical details from tech design, then links back to the codex source for full context.
+
+## 0.22.0
+
+### Minor Changes
+
+- [#113](https://github.com/Orderful/droid/pull/113) [`37245c2`](https://github.com/Orderful/droid/commit/37245c2a54427dc57f54ec80399d827997089e0a) Thanks [@frytyler](https://github.com/frytyler)! - Add `/codex artifact` command for adding supplementary documents to projects. Artifacts are supporting materials like customer interviews, research notes, and meeting summaries that live in `projects/{name}/artifacts/`.
+
 ## 0.21.0
 
 ### Minor Changes

package/dist/tools/codex/agents/codex-document-processor.md

@@ -14,15 +14,16 @@ You are a document processor for the Orderful codex. Your job is to transform so
 
 You will receive:
 1. **File path** - The source document to process
-2. **Document type** - One of: `prd`, `tech-design`, `topic`, `pattern`
+2. **Document type** - One of: `prd`, `tech-design`, `topic`, `pattern`, `artifact`
 3. **Project/entry name** - Where this should be stored in the codex
 4. **Codex repo path** - The local path to orderful-codex repository
+5. **Artifact filename** (optional, for artifacts) - Name for the artifact file
 
 ## Validation (Do This First)
 
 Before processing, validate all inputs:
 
-1. **Document type** - Must be one of: `prd`, `tech-design`, `topic`, `pattern`. Reject anything else.
+1. **Document type** - Must be one of: `prd`, `tech-design`, `topic`, `pattern`, `artifact`. Reject anything else.
 2. **File path** - Must exist and be readable. Use Read tool to verify.
 3. **Project/entry name** - Must be safe for filesystem paths:
    - Only allow: alphanumeric, dashes, underscores
@@ -44,10 +45,13 @@ From the content, identify:
 - **Title** - The document/feature name
 - **Main content** - The substantive information
 - **Codebase paths** (if tech-design) - Any code paths mentioned
-- **Source** - Default to `confluence` for PRDs/tech-designs, `exploration` for topics
+- **Source** - Default based on type:
+  - PRD/tech-design: `confluence`
+  - Topic/pattern: `exploration`
+  - Artifact: infer from content (`interview`, `transcript`, `notes`, `meeting`, `research`, `spike`, `analysis`)
 - **Status** - Default based on type:
   - PRD/tech-design: `draft` (new imports start as drafts)
-  - Topic/pattern: `active` (explorations are immediately usable)
+  - Topic/pattern/artifact: `active`
 
 ### 3. Read and Apply Frontmatter Template
 
@@ -58,7 +62,8 @@ From the content, identify:
 | `prd` | `{codex_repo}/templates/PRD.md` |
 | `tech-design` | `{codex_repo}/templates/TECH-DESIGN.md` |
 | `topic` | `{codex_repo}/templates/TOPIC.md` |
-| `pattern` | `{codex_repo}/templates/PATTERN.md` (if exists, else use TOPIC.md) |
+| `pattern` | `{codex_repo}/templates/PATTERN.md` |
+| `artifact` | `{codex_repo}/templates/ARTIFACT.md` |
 
 1. Read the appropriate template file
 2. Extract its frontmatter structure
@@ -90,6 +95,9 @@ Write the processed markdown to the correct location:
 | `tech-design` | `{codex_repo}/projects/{name}/TECH-DESIGN.md` |
 | `topic` | `{codex_repo}/topics/{name}.md` |
 | `pattern` | `{codex_repo}/patterns/{name}.md` |
+| `artifact` | `{codex_repo}/projects/{name}/artifacts/{filename}.md` |
+
+For artifacts, derive `{filename}` from the artifact filename input or the source file's name (slugified).
 
 Create the directory if it doesn't exist.
 

package/dist/tools/codex/skills/droid-codex/SKILL.md

@@ -123,6 +123,7 @@ The codex has three categories:
 | `/codex new {name}` | Scaffold new project from templates |
 | `/codex decision {text}` | Append to active project's DECISIONS.md |
 | `/codex snapshot {type} {file} {name}` | Import PDF/markdown to codex (uses agent) |
+| `/codex artifact {file} {project}` | Add supporting artifact to project (uses agent) |
 | `/codex add topic {name}` | Add explored topic with freshness metadata |
 
 ## Loading an Entry
@@ -270,6 +271,32 @@ Full procedure: `references/topics.md`
 The agent handles: PDF reading, content extraction, frontmatter generation, file writing.
 The main conversation handles: git branch, commit, PR creation, user interaction.
 
+## Adding Artifacts
+
+**Trigger:** `/codex artifact {file} {project}` or user wants to add supporting material to a project
+
+Artifacts are supplementary documents that support a project but aren't core document types (PRD, TECH-DESIGN, DECISIONS). Examples:
+- Customer interviews / transcripts
+- Research notes
+- Meeting summaries
+- Spike findings
+- Competitor analysis
+
+**Procedure:**
+
+1. Use the `codex-document-processor` agent with type `artifact`
+2. Agent writes to `{codex_repo}/projects/{project}/artifacts/{filename}.md`
+3. Handle git workflow (branch, commit, PR)
+
+**Example invocations:**
+
+```bash
+/codex artifact ~/Downloads/customer-interview-acme.pdf transaction-templates
+/codex artifact ~/notes/spike-handlebars-perf.md partnership-automation
+```
+
+Artifacts get lighter frontmatter with `type: artifact` and source like `interview`, `transcript`, `notes`, `meeting`, `research`, `spike`, or `analysis`.
+
 ## Creating New Projects
 
 **Trigger:** `/codex new {name}` or user wants to start new project entry

package/dist/tools/project/TOOL.yaml

@@ -1,6 +1,6 @@
 name: project
 description: "Manage project context files for persistent AI memory across sessions. Load, update, or create project context before working on multi-session features."
-version: 0.1.5
+version: 0.2.0
 status: beta
 
 includes:

package/dist/tools/project/skills/droid-project/SKILL.md

@@ -49,6 +49,7 @@ Default `projects_dir` by AI tool (only if overrides.yaml is missing or lacks `p
 | `/project` | List and select a project |
 | `/project {keywords}` | **Search** for existing project (fuzzy-match and load) |
 | `/project create {name}` | Create new project (requires `create` keyword) |
+| `/project create --from codex:{name}` | Create project seeded with codex context |
 | `/project update` | Update from conversation context |
 
 **IMPORTANT:** The default action for `/project {keywords}` is to **SEARCH** for existing projects, NOT create. Only use `/project create {name}` when the user explicitly wants to create a new project.
@@ -77,6 +78,8 @@ Changelog format: `references/changelog.md`
 
 **TLDR:** Create folder in `projects_dir`, generate PROJECT.md + CHANGELOG.md from templates.
 
+**From codex:** Use `--from codex:{name}` to seed with shared organizational context. Extracts overview from PRD, technical details from tech design, and links to codex source.
+
 Full procedure: `references/creating.md`
 Templates: `references/templates.md`
 

package/dist/tools/project/skills/droid-project/references/creating.md

@@ -61,3 +61,101 @@ New projects start minimal and grow organically. Common sections added over time
 - **Roadmap** - Future phases
 
 See `templates.md` for the full initial template.
+
+---
+
+## Creating from Codex
+
+**Trigger:** `/project create --from codex:{name}` or `/project create {name} --from codex:{codex-name}`
+
+Bridge shared organizational knowledge (codex) to personal working memory (project).
+
+### Procedure
+
+1. **Parse arguments**
+   - If only `--from codex:{name}` → use codex name as project name
+   - If `{name} --from codex:{codex-name}` → use custom project name
+
+2. **Load codex entry**
+   - Read `~/.droid/skills/codex/overrides.yaml` for `codex_repo` path
+   - Sync: `git -C {codex_repo} pull --rebase --quiet`
+   - Locate `{codex_repo}/projects/{name}/`
+   - If not found → error with suggestions from available projects
+
+3. **Extract context from codex files**
+
+   **From PRD.md:**
+   - Title from frontmatter or H1
+   - Problem Statement → Overview
+   - Goals section → Goals list
+   - Status from frontmatter
+
+   **From TECH-DESIGN.md:**
+   - Overview section → Technical Details intro
+   - Architecture section → Technical Details (summarised)
+   - `codebase_paths` from frontmatter → Key Paths
+
+   **From DECISIONS.md:**
+   - Count of decisions → mention in Overview
+   - Do not copy content (link to codex instead)
+
+4. **Create project folder** (same as standard create)
+   - Path: `{projects_dir}/{kebab-case-name}/`
+   - Verify folder doesn't already exist
+
+5. **Create files from seeded template** (see `templates.md` - Seeded from Codex)
+   - `PROJECT.md` - Pre-filled with extracted context
+   - `CHANGELOG.md` - Notes codex source
+
+6. **Confirm creation**
+   ```
+   Created project "Transaction Templates" seeded from codex.
+
+   📁 ~/.claude/projects/transaction-templates/
+   ├── PROJECT.md (seeded with codex context)
+   └── CHANGELOG.md
+
+   Codex source: projects/transaction-templates
+
+   The project is pre-filled with:
+   - Overview from PRD problem statement
+   - Goals from PRD
+   - Technical details from tech design
+
+   Full codex docs remain at: {codex_repo}/projects/{name}/
+   Use `/codex {name}` to load the complete shared context.
+   ```
+
+### Error Handling
+
+**Codex project not found:**
+```
+No codex project found for "{name}".
+
+Available projects:
+- partnership-automation
+- generic-scenario-testing
+
+Try: /project create --from codex:partnership-automation
+```
+
+**Project folder already exists:**
+```
+A project named "{name}" already exists at {path}.
+
+Options:
+- Load existing: /project {name}
+- Use different name: /project create other-name --from codex:{codex-name}
+```
+
+**Missing codex files:**
+- If PRD.md missing: warn, proceed with available files
+- If TECH-DESIGN.md missing: warn, proceed with available files
+- If all files missing: error, suggest using standard create
+
+### Key Principles
+
+- **Links, not copies** - PROJECT.md links to codex, doesn't duplicate it
+- **Extracts summaries** - Brief context, not full documents
+- **Links stay live** - `/codex {name}` always loads latest from repo
+- **Independent growth** - PROJECT.md evolves separately during implementation

package/dist/tools/project/skills/droid-project/references/templates.md

@@ -122,3 +122,99 @@ Same as markdown preset.
 | Links | `[text](path)` | `[[path\|text]]` |
 | YAML properties | Minimal (`status`) | Rich (`type`, `created`, `updated`) |
 | Related section | Optional | Included |
+
+---
+
+## Seeded from Codex
+
+When creating with `--from codex:{name}`, use this template variant. Works with both markdown and obsidian presets.
+
+### Additional Variables
+
+| Variable | Expands To |
+|----------|------------|
+| `{codex-name}` | Source codex project name |
+| `{codex_repo}` | Path to codex repository |
+| `{overview}` | Extracted from PRD problem statement |
+| `{goals}` | Extracted from PRD goals (bullet list) |
+| `{tech_details}` | Extracted from tech design overview |
+| `{codebase_paths}` | Paths from tech design frontmatter |
+| `{decision_count}` | Number of decisions in DECISIONS.md |
+
+### PROJECT.md (Seeded)
+
+```markdown
+---
+status: active
+codex_source: projects/{codex-name}
+---
+
+# Project: {Name}
+
+Personal working memory for {Name}, seeded from shared codex context.
+
+| | |
+|---|---|
+| **Version** | 0.1.0 |
+| **Started** | {today} |
+| **Status** | Active |
+| **Codex** | `projects/{codex-name}` |
+
+## Overview
+
+{overview}
+
+## Goals
+
+{goals}
+
+## Technical Details
+
+{tech_details}
+
+### Key Paths
+
+{codebase_paths}
+
+## Current Work
+
+{To be filled during implementation}
+
+## Related
+
+- **Codex project:** `/codex {codex-name}`
+- **PRD:** `{codex_repo}/projects/{codex-name}/PRD.md`
+- **Tech Design:** `{codex_repo}/projects/{codex-name}/TECH-DESIGN.md`
+- **Decisions ({decision_count}):** `{codex_repo}/projects/{codex-name}/DECISIONS.md`
+
+## Changelog
+
+See [CHANGELOG.md](CHANGELOG.md) for full history.
+
+### 0.1.0 - {today}
+- Project created from codex:{codex-name}
+```
+
+### CHANGELOG.md (Seeded)
+
+```markdown
+# Changelog
+
+All notable changes to the {Name} project.
+
+## 0.1.0 - {today}
+- Project created from codex:{codex-name}
+- Seeded with context from PRD, TECH-DESIGN
+```
+
+### Extraction Guidelines
+
+When extracting content from codex files:
+
+1. **Overview** - Look for "Problem Statement", "Overview", or first substantive paragraph in PRD.md
+2. **Goals** - Look for "Goals", "Objectives", or bulleted list in PRD.md
+3. **Tech Details** - Look for "Overview", "Architecture", or "Approach" in TECH-DESIGN.md
+4. **Codebase Paths** - Extract from `codebase_paths` frontmatter field
+
+If a section is missing, use placeholder text:
+- `{To be extracted from codex or filled manually}`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@orderful/droid",
-  "version": "0.21.0",
+  "version": "0.23.0",
   "description": "AI workflow toolkit for sharing skills, commands, and agents across the team",
   "type": "module",
   "bin": {

package/src/tools/codex/agents/codex-document-processor.md

@@ -14,15 +14,16 @@ You are a document processor for the Orderful codex. Your job is to transform so
 
 You will receive:
 1. **File path** - The source document to process
-2. **Document type** - One of: `prd`, `tech-design`, `topic`, `pattern`
+2. **Document type** - One of: `prd`, `tech-design`, `topic`, `pattern`, `artifact`
 3. **Project/entry name** - Where this should be stored in the codex
 4. **Codex repo path** - The local path to orderful-codex repository
+5. **Artifact filename** (optional, for artifacts) - Name for the artifact file
 
 ## Validation (Do This First)
 
 Before processing, validate all inputs:
 
-1. **Document type** - Must be one of: `prd`, `tech-design`, `topic`, `pattern`. Reject anything else.
+1. **Document type** - Must be one of: `prd`, `tech-design`, `topic`, `pattern`, `artifact`. Reject anything else.
 2. **File path** - Must exist and be readable. Use Read tool to verify.
 3. **Project/entry name** - Must be safe for filesystem paths:
    - Only allow: alphanumeric, dashes, underscores
@@ -44,10 +45,13 @@ From the content, identify:
 - **Title** - The document/feature name
 - **Main content** - The substantive information
 - **Codebase paths** (if tech-design) - Any code paths mentioned
-- **Source** - Default to `confluence` for PRDs/tech-designs, `exploration` for topics
+- **Source** - Default based on type:
+  - PRD/tech-design: `confluence`
+  - Topic/pattern: `exploration`
+  - Artifact: infer from content (`interview`, `transcript`, `notes`, `meeting`, `research`, `spike`, `analysis`)
 - **Status** - Default based on type:
   - PRD/tech-design: `draft` (new imports start as drafts)
-  - Topic/pattern: `active` (explorations are immediately usable)
+  - Topic/pattern/artifact: `active`
 
 ### 3. Read and Apply Frontmatter Template
 
@@ -58,7 +62,8 @@ From the content, identify:
 | `prd` | `{codex_repo}/templates/PRD.md` |
 | `tech-design` | `{codex_repo}/templates/TECH-DESIGN.md` |
 | `topic` | `{codex_repo}/templates/TOPIC.md` |
-| `pattern` | `{codex_repo}/templates/PATTERN.md` (if exists, else use TOPIC.md) |
+| `pattern` | `{codex_repo}/templates/PATTERN.md` |
+| `artifact` | `{codex_repo}/templates/ARTIFACT.md` |
 
 1. Read the appropriate template file
 2. Extract its frontmatter structure
@@ -90,6 +95,9 @@ Write the processed markdown to the correct location:
 | `tech-design` | `{codex_repo}/projects/{name}/TECH-DESIGN.md` |
 | `topic` | `{codex_repo}/topics/{name}.md` |
 | `pattern` | `{codex_repo}/patterns/{name}.md` |
+| `artifact` | `{codex_repo}/projects/{name}/artifacts/{filename}.md` |
+
+For artifacts, derive `{filename}` from the artifact filename input or the source file's name (slugified).
 
 Create the directory if it doesn't exist.
 

package/src/tools/codex/skills/droid-codex/SKILL.md

@@ -123,6 +123,7 @@ The codex has three categories:
 | `/codex new {name}` | Scaffold new project from templates |
 | `/codex decision {text}` | Append to active project's DECISIONS.md |
 | `/codex snapshot {type} {file} {name}` | Import PDF/markdown to codex (uses agent) |
+| `/codex artifact {file} {project}` | Add supporting artifact to project (uses agent) |
 | `/codex add topic {name}` | Add explored topic with freshness metadata |
 
 ## Loading an Entry
@@ -270,6 +271,32 @@ Full procedure: `references/topics.md`
 The agent handles: PDF reading, content extraction, frontmatter generation, file writing.
 The main conversation handles: git branch, commit, PR creation, user interaction.
 
+## Adding Artifacts
+
+**Trigger:** `/codex artifact {file} {project}` or user wants to add supporting material to a project
+
+Artifacts are supplementary documents that support a project but aren't core document types (PRD, TECH-DESIGN, DECISIONS). Examples:
+- Customer interviews / transcripts
+- Research notes
+- Meeting summaries
+- Spike findings
+- Competitor analysis
+
+**Procedure:**
+
+1. Use the `codex-document-processor` agent with type `artifact`
+2. Agent writes to `{codex_repo}/projects/{project}/artifacts/{filename}.md`
+3. Handle git workflow (branch, commit, PR)
+
+**Example invocations:**
+
+```bash
+/codex artifact ~/Downloads/customer-interview-acme.pdf transaction-templates
+/codex artifact ~/notes/spike-handlebars-perf.md partnership-automation
+```
+
+Artifacts get lighter frontmatter with `type: artifact` and source like `interview`, `transcript`, `notes`, `meeting`, `research`, `spike`, or `analysis`.
+
 ## Creating New Projects
 
 **Trigger:** `/codex new {name}` or user wants to start new project entry

package/src/tools/project/TOOL.yaml

@@ -1,6 +1,6 @@
 name: project
 description: "Manage project context files for persistent AI memory across sessions. Load, update, or create project context before working on multi-session features."
-version: 0.1.5
+version: 0.2.0
 status: beta
 
 includes:

package/src/tools/project/skills/droid-project/SKILL.md

@@ -49,6 +49,7 @@ Default `projects_dir` by AI tool (only if overrides.yaml is missing or lacks `p
 | `/project` | List and select a project |
 | `/project {keywords}` | **Search** for existing project (fuzzy-match and load) |
 | `/project create {name}` | Create new project (requires `create` keyword) |
+| `/project create --from codex:{name}` | Create project seeded with codex context |
 | `/project update` | Update from conversation context |
 
 **IMPORTANT:** The default action for `/project {keywords}` is to **SEARCH** for existing projects, NOT create. Only use `/project create {name}` when the user explicitly wants to create a new project.
@@ -77,6 +78,8 @@ Changelog format: `references/changelog.md`
 
 **TLDR:** Create folder in `projects_dir`, generate PROJECT.md + CHANGELOG.md from templates.
 
+**From codex:** Use `--from codex:{name}` to seed with shared organizational context. Extracts overview from PRD, technical details from tech design, and links to codex source.
+
 Full procedure: `references/creating.md`
 Templates: `references/templates.md`
 

package/src/tools/project/skills/droid-project/references/creating.md

@@ -61,3 +61,101 @@ New projects start minimal and grow organically. Common sections added over time
 - **Roadmap** - Future phases
 
 See `templates.md` for the full initial template.
+
+---
+
+## Creating from Codex
+
+**Trigger:** `/project create --from codex:{name}` or `/project create {name} --from codex:{codex-name}`
+
+Bridge shared organizational knowledge (codex) to personal working memory (project).
+
+### Procedure
+
+1. **Parse arguments**
+   - If only `--from codex:{name}` → use codex name as project name
+   - If `{name} --from codex:{codex-name}` → use custom project name
+
+2. **Load codex entry**
+   - Read `~/.droid/skills/codex/overrides.yaml` for `codex_repo` path
+   - Sync: `git -C {codex_repo} pull --rebase --quiet`
+   - Locate `{codex_repo}/projects/{name}/`
+   - If not found → error with suggestions from available projects
+
+3. **Extract context from codex files**
+
+   **From PRD.md:**
+   - Title from frontmatter or H1
+   - Problem Statement → Overview
+   - Goals section → Goals list
+   - Status from frontmatter
+
+   **From TECH-DESIGN.md:**
+   - Overview section → Technical Details intro
+   - Architecture section → Technical Details (summarised)
+   - `codebase_paths` from frontmatter → Key Paths
+
+   **From DECISIONS.md:**
+   - Count of decisions → mention in Overview
+   - Do not copy content (link to codex instead)
+
+4. **Create project folder** (same as standard create)
+   - Path: `{projects_dir}/{kebab-case-name}/`
+   - Verify folder doesn't already exist
+
+5. **Create files from seeded template** (see `templates.md` - Seeded from Codex)
+   - `PROJECT.md` - Pre-filled with extracted context
+   - `CHANGELOG.md` - Notes codex source
+
+6. **Confirm creation**
+   ```
+   Created project "Transaction Templates" seeded from codex.
+
+   📁 ~/.claude/projects/transaction-templates/
+   ├── PROJECT.md (seeded with codex context)
+   └── CHANGELOG.md
+
+   Codex source: projects/transaction-templates
+
+   The project is pre-filled with:
+   - Overview from PRD problem statement
+   - Goals from PRD
+   - Technical details from tech design
+
+   Full codex docs remain at: {codex_repo}/projects/{name}/
+   Use `/codex {name}` to load the complete shared context.
+   ```
+
+### Error Handling
+
+**Codex project not found:**
+```
+No codex project found for "{name}".
+
+Available projects:
+- partnership-automation
+- generic-scenario-testing
+
+Try: /project create --from codex:partnership-automation
+```
+
+**Project folder already exists:**
+```
+A project named "{name}" already exists at {path}.
+
+Options:
+- Load existing: /project {name}
+- Use different name: /project create other-name --from codex:{codex-name}
+```
+
+**Missing codex files:**
+- If PRD.md missing: warn, proceed with available files
+- If TECH-DESIGN.md missing: warn, proceed with available files
+- If all files missing: error, suggest using standard create
+
+### Key Principles
+
+- **Links, not copies** - PROJECT.md links to codex, doesn't duplicate it
+- **Extracts summaries** - Brief context, not full documents
+- **Links stay live** - `/codex {name}` always loads latest from repo
+- **Independent growth** - PROJECT.md evolves separately during implementation

package/src/tools/project/skills/droid-project/references/templates.md

@@ -122,3 +122,99 @@ Same as markdown preset.
 | Links | `[text](path)` | `[[path\|text]]` |
 | YAML properties | Minimal (`status`) | Rich (`type`, `created`, `updated`) |
 | Related section | Optional | Included |
+
+---
+
+## Seeded from Codex
+
+When creating with `--from codex:{name}`, use this template variant. Works with both markdown and obsidian presets.
+
+### Additional Variables
+
+| Variable | Expands To |
+|----------|------------|
+| `{codex-name}` | Source codex project name |
+| `{codex_repo}` | Path to codex repository |
+| `{overview}` | Extracted from PRD problem statement |
+| `{goals}` | Extracted from PRD goals (bullet list) |
+| `{tech_details}` | Extracted from tech design overview |
+| `{codebase_paths}` | Paths from tech design frontmatter |
+| `{decision_count}` | Number of decisions in DECISIONS.md |
+
+### PROJECT.md (Seeded)
+
+```markdown
+---
+status: active
+codex_source: projects/{codex-name}
+---
+
+# Project: {Name}
+
+Personal working memory for {Name}, seeded from shared codex context.
+
+| | |
+|---|---|
+| **Version** | 0.1.0 |
+| **Started** | {today} |
+| **Status** | Active |
+| **Codex** | `projects/{codex-name}` |
+
+## Overview
+
+{overview}
+
+## Goals
+
+{goals}
+
+## Technical Details
+
+{tech_details}
+
+### Key Paths
+
+{codebase_paths}
+
+## Current Work
+
+{To be filled during implementation}
+
+## Related
+
+- **Codex project:** `/codex {codex-name}`
+- **PRD:** `{codex_repo}/projects/{codex-name}/PRD.md`
+- **Tech Design:** `{codex_repo}/projects/{codex-name}/TECH-DESIGN.md`
+- **Decisions ({decision_count}):** `{codex_repo}/projects/{codex-name}/DECISIONS.md`
+
+## Changelog
+
+See [CHANGELOG.md](CHANGELOG.md) for full history.
+
+### 0.1.0 - {today}
+- Project created from codex:{codex-name}
+```
+
+### CHANGELOG.md (Seeded)
+
+```markdown
+# Changelog
+
+All notable changes to the {Name} project.
+
+## 0.1.0 - {today}
+- Project created from codex:{codex-name}
+- Seeded with context from PRD, TECH-DESIGN
+```
+
+### Extraction Guidelines
+
+When extracting content from codex files:
+
+1. **Overview** - Look for "Problem Statement", "Overview", or first substantive paragraph in PRD.md
+2. **Goals** - Look for "Goals", "Objectives", or bulleted list in PRD.md
+3. **Tech Details** - Look for "Overview", "Architecture", or "Approach" in TECH-DESIGN.md
+4. **Codebase Paths** - Extract from `codebase_paths` frontmatter field
+
+If a section is missing, use placeholder text:
+- `{To be extracted from codex or filled manually}`