@orderful/droid 0.32.0 → 0.33.1

package/src/tools/project/skills/project/references/loading.md

@@ -6,10 +6,10 @@
 
 ## Procedure
 
-1. **Determine projects directory (pick ONE)**
-   - Read `~/.droid/skills/project/overrides.yaml`
-   - If `projects_dir` is set → use ONLY that path, do NOT search defaults
-   - If not configured → use default for current AI tool (`~/.claude/projects` or `~/.config/opencode/projects`)
+1. **Determine projects directory**
+   - Run `droid config project` and parse the JSON output
+   - Use the `projects_dir` value
+   - If not configured → inform user to create `~/.droid/skills/project/overrides.yaml` with `projects_dir: /path/to/projects`
 
 2. **List projects** in the single configured directory
    - Each subfolder with a `PROJECT.md` is a project

package/src/tools/tech-design/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "droid-tech-design",
-  "version": "0.2.1",
+  "version": "0.2.3",
   "description": "Technical design authoring tool for engineers. Create structured tech design docs with /tech-design start, iterate in brain, publish to codex. Three-document approach: research doc (codebase discoveries) + thought doc (design workspace) + roll-up (clean summary for review).",
   "author": {
     "name": "Orderful",

package/src/tools/tech-design/TOOL.yaml

@@ -1,6 +1,6 @@
 name: tech-design
 description: "Technical design authoring tool for engineers. Create structured tech design docs with /tech-design start, iterate in brain, publish to codex. Three-document approach: research doc (codebase discoveries) + thought doc (design workspace) + roll-up (clean summary for review)."
-version: 0.2.1
+version: 0.2.3
 status: beta
 
 includes:

package/src/tools/tech-design/skills/tech-design/SKILL.md

@@ -28,8 +28,8 @@ The `/tech-design` skill brings tech design authoring into the same AI-augmented
 
 Before using tech-design, verify:
 
-1. **Brain skill configured:** Check if `~/.droid/skills/brain/overrides.yaml` exists
-2. **Codex skill configured:** Check if `~/.droid/skills/codex/overrides.yaml` exists
+1. **Brain skill configured:** Run `droid config brain` and check if `brain_dir` is set
+2. **Codex skill configured:** Run `droid config codex` and check if `codex_repo` is set
 3. **gh CLI:** Required for PR workflows
 
 If prerequisites fail, guide user to configure:
@@ -65,7 +65,7 @@ Tech-design has no configuration of its own. It delegates to:
 2. **Thought doc** = Design workspace
    - References research doc for context
    - Focuses on architectural decisions
-   - Iterates with `@droid`/`@user` comments
+   - Iterates with `@droid`/`@user` comments (the @mention is the **target**: `@droid` = user asking AI, `@user` = AI asking user)
    - Captures the "why" behind choices
 
 3. **Roll-up** = Reviewer artifact

package/src/tools/tech-design/skills/tech-design/references/publish.md

@@ -25,7 +25,7 @@ if [ ! -f "$research_doc_path" ]; then
 fi
 
 # Codex repo must be configured (read from codex skill config)
-codex_repo=$(grep '^codex_repo:' ~/.droid/skills/codex/overrides.yaml | cut -d' ' -f2-)
+codex_repo=$(droid config codex | grep -o '"codex_repo": *"[^"]*"' | cut -d'"' -f4)
 if [ -z "$codex_repo" ]; then
   echo "Error: Codex not configured."
   echo "Set up with: /codex"

package/src/tools/tech-design/skills/tech-design/references/start.md

@@ -12,8 +12,8 @@
 
 Check that required tools are configured:
 
-- **Brain skill:** Check if `~/.droid/skills/brain/overrides.yaml` exists
-- **Codex skill:** Check if `~/.droid/skills/codex/overrides.yaml` exists
+- **Brain skill:** Run `droid config brain` and check if `brain_dir` is set
+- **Codex skill:** Run `droid config codex` and check if `codex_repo` is set
 
 If prerequisites fail, guide user to configure:
 

package/src/tools/wrapup/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "droid-wrapup",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "Session wrap-up that captures decisions, learnings, and open items to persistent docs.",
   "author": {
     "name": "Orderful",

package/src/tools/wrapup/TOOL.yaml

@@ -1,6 +1,6 @@
 name: wrapup
 description: "Session wrap-up that captures decisions, learnings, and open items to persistent docs."
-version: 0.1.0
+version: 0.1.2
 status: alpha
 
 includes:

package/src/tools/wrapup/skills/wrapup/SKILL.md

@@ -15,7 +15,7 @@ To avoid triggering compaction mid-wrapup, offload heavy lifting to fresh-contex
 
 ## Phase 1: Quick Context Extraction
 
-You have the conversation history. Quickly extract and write to `/tmp/wrapup-session-brief.md`:
+You have the conversation history. Generate a unique session ID (e.g., timestamp like `20260118-153042`) and write to `/tmp/wrapup-{session-id}.md`:
 
 ```markdown
 # Session Brief
@@ -41,9 +41,11 @@ You have the conversation history. Quickly extract and write to `/tmp/wrapup-ses
 
 Do this IMMEDIATELY. Don't analyse deeply—just dump what you know.
 
+**Important:** Remember your session brief path for Phase 2 subagents.
+
 ## Phase 2: Artifact Analysis
 
-Spawn subagents **in parallel** to analyse artifacts. Each reads your session brief and analyses one area.
+Spawn subagents **in parallel** to analyse artifacts. Pass your session brief path to each subagent.
 
 | Subagent | Type | Analyses |
 |----------|------|----------|

package/src/tools/wrapup/skills/wrapup/references/subagent-prompts.md

@@ -2,6 +2,8 @@
 
 Detailed prompts for Phase 2 artifact analysis. Spawn these in parallel using the Task tool.
 
+**Note:** Replace `{session_brief_path}` with the actual path from Phase 1 (e.g., `/tmp/wrapup-20260118-153042.md`).
+
 ## Git State Analysis
 
 **Subagent type:** Bash
@@ -24,21 +26,27 @@ Output format:
 
 ## Project File Check
 
-**Subagent type:** Explore
+**Subagent type:** Bash
 
 ```
-Read /tmp/wrapup-session-brief.md for session context.
+Read {session_brief_path} for session context.
 
-Check if ~/.droid/project.md exists. If it does:
-1. Read the current project file
-2. Compare against session brief
-3. Identify:
+First, run `droid config project` to get the project skill configuration.
+Parse the JSON output to find the `projects_dir` value.
+
+If `projects_dir` is not set, skip project file analysis.
+
+If configured:
+1. Search the projects directory for recently modified PROJECT.md files (last 7 days)
+2. Read the most recently modified project file
+3. Compare against session brief
+4. Identify:
    - Stale entries that should be updated or removed
    - New items from the session to add (decisions, blockers, next steps)
    - Status changes (completed items, new blockers)
 
 Output specific proposed updates with exact text to add/change.
-If no project file exists, note that and skip.
+If no active project found, note that and skip.
 ```
 
 ## Brain Doc Check
@@ -46,9 +54,9 @@ If no project file exists, note that and skip.
 **Subagent type:** Explore
 
 ```
-Read /tmp/wrapup-session-brief.md for session context.
+Read {session_brief_path} for session context.
 
-First, check ~/.droid/skills/brain/overrides.yaml for the brain_dir setting.
+First, run `droid config brain` and parse the JSON output for the `brain_dir` setting.
 If not configured, skip brain doc analysis.
 
 If configured:
@@ -68,9 +76,9 @@ Output:
 **Subagent type:** Explore
 
 ```
-Read /tmp/wrapup-session-brief.md for session context.
+Read {session_brief_path} for session context.
 
-Check if the codex skill is installed (~/.droid/skills/codex/overrides.yaml).
+Run `droid config codex` and check if `codex_repo` is set.
 If not configured, skip codex analysis.
 
 If the session involved: