@orderful/droid 0.21.0 → 0.22.0

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @orderful/droid
 
+## 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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@orderful/droid",
-  "version": "0.21.0",
+  "version": "0.22.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