@orderful/droid 0.25.2 → 0.27.0

package/dist/tools/brain/TOOL.yaml

@@ -1,18 +1,20 @@
 name: brain
 description: "Your scratchpad (or brain) - a collaborative space for planning and research. Create docs with /brain plan, /brain research, or /brain review. Use @mentions for async discussion. Docs persist across sessions."
-version: 0.2.3
+version: 0.3.0
 status: beta
 
 includes:
   skills:
-    - name: droid-brain
+    - name: brain
       required: true
-    - name: droid-brain-obsidian
+    - name: brain-obsidian
       required: false
       description: "Obsidian vault integration with YAML frontmatter and wikilinks"
   commands:
-    - brain
-    - scratchpad
+    - name: brain
+      is_alias: false
+    - name: scratchpad
+      is_alias: true
   agents: []
 
 dependencies: []

package/dist/tools/brain/commands/brain.md

@@ -1,65 +1,33 @@
 ---
-description: Collaborative scratchpad for planning and research
+name: brain
+description: "Collaborative scratchpad for planning and research"
 argument-hint: "[{topic} | plan|research|review {topic} | idea|add {text} | check|done]"
-allowed-tools: Read, Write, Edit, Glob, Grep, Bash(mkdir:*), Bash(ls:*)
 ---
 
 # /brain
 
-Entry point for brain doc management. See the **brain skill** for full behavior.
+**User invoked:** `/brain $ARGUMENTS`
 
-> **Alias:** This command also works as `/scratchpad` - use whichever feels natural.
-
-## Arguments
-
-$ARGUMENTS
-
-## Default Behavior
+**Your task:** Invoke the **brain skill** with these arguments.
 
-**IMPORTANT:** When given just a topic (e.g., `/brain auth-refactor`), the default action is to **SEARCH** for existing docs, NOT create. Only create docs with explicit `/brain plan {topic}` or `/brain research {topic}`.
-
-## Usage
-
-```
-/brain                      # List recent docs or create new
-/brain {topic}              # SEARCH: Open existing doc (fuzzy match) → active
-/brain plan {topic}         # CREATE: New planning doc → plans/
-/brain research {topic}     # Create research doc → research/
-/brain review {topic}       # Create review doc → reviews/
-/brain idea {text}          # Quick capture → ideas/ (fire-and-forget)
-/brain add {text}           # Append to active doc
-/brain check                # Address @droid comments in active doc
-/brain done                 # Finalize active doc
-```
-
-## Configuration
-
-**ALWAYS read `~/.droid/skills/brain/overrides.yaml` first.** Use configured values if present, only fall back to defaults if missing.
+> **Alias:** This command also works as `/scratchpad` - use whichever feels natural.
 
-- `brain_dir` - Where docs live (default varies by AI tool)
-- `inbox_folder` - Root for type folders (e.g., `0-Inbox`)
+## Examples
 
-## Folder Structure
+- `/brain auth-refactor` → Search for existing doc about "auth-refactor"
+- `/brain plan new-feature` → Create a new planning doc for "new-feature"
+- `/brain add found a bug in the parser` → Append text to active doc
 
-Docs are organized by type:
+## Quick Reference
 
 ```
-{brain_dir}/{inbox_folder}/
-├── plans/
-├── research/
-├── reviews/
-└── ideas/
+/brain {topic}              # SEARCH for existing doc (default action)
+/brain plan {topic}         # CREATE new planning doc
+/brain research {topic}     # CREATE new research doc
+/brain idea {text}          # Quick capture to ideas/
+/brain check                # Address @droid comments
 ```
 
-## Behavior
-
-Refer to the brain skill for:
-
-- **Opening**: How to fuzzy-match, handle multiple matches, set active
-- **Creating**: Template structure by preset, naming conventions
-- **Ideas**: Quick capture workflow
-- **Adding**: Append to active doc with timestamp
-- **Checking**: Find and address @droid comments
-- **Finalizing**: Update status, suggest next steps
+**Default behavior:** When given just a topic, SEARCH first (don't create unless plan/research/review keyword is present).
 
-The skill's `references/` folder contains detailed specs for workflows, templates, naming, and metadata.
+See the **brain skill** for complete documentation and procedures.

package/dist/tools/brain/commands/scratchpad.md

@@ -1,65 +1,28 @@
 ---
-description: Collaborative scratchpad for planning and research
-argument-hint: "[{topic} | plan|research|review {topic} | idea|add {text} | check|done]"
-allowed-tools: Read, Write, Edit, Glob, Grep, Bash(mkdir:*), Bash(ls:*)
+name: scratchpad
+description: "Alias for brain. See brain skill for full behavior."
 ---
 
 # /scratchpad
 
-Your scratchpad for planning, research, and design. See the **brain skill** for full behavior.
+**User invoked:** `/scratchpad $ARGUMENTS`
 
-> **Alias:** This command also works as `/brain` - use whichever feels natural.
+**Your task:** Invoke the **brain skill** with these arguments (scratchpad is an alias for brain).
 
-## Arguments
+## Examples
 
-$ARGUMENTS
+- `/scratchpad auth-refactor` → Search for existing doc about "auth-refactor"
+- `/scratchpad plan new-feature` → Create a new planning doc for "new-feature"
 
-## Default Behavior
+## Quick Reference
 
-**IMPORTANT:** When given just a topic (e.g., `/scratchpad auth-refactor`), the default action is to **SEARCH** for existing docs, NOT create. Only create docs with explicit `/scratchpad plan {topic}` or `/scratchpad research {topic}`.
-
-## Usage
+Same as `/brain` - use whichever name feels natural:
 
 ```
-/scratchpad                      # List recent docs or create new
-/scratchpad {topic}              # SEARCH: Open existing doc (fuzzy match) → active
-/scratchpad plan {topic}         # CREATE: New planning doc → plans/
-/scratchpad research {topic}     # Create research doc → research/
-/scratchpad review {topic}       # Create review doc → reviews/
-/scratchpad idea {text}          # Quick capture → ideas/ (fire-and-forget)
-/scratchpad add {text}           # Append to active doc
-/scratchpad check                # Address @droid comments in active doc
-/scratchpad done                 # Finalize active doc
+/scratchpad {topic}         # SEARCH for existing doc
+/scratchpad plan {topic}    # CREATE new planning doc
 ```
 
-## Configuration
-
-**ALWAYS read `~/.droid/skills/brain/overrides.yaml` first.** Use configured values if present, only fall back to defaults if missing.
-
-- `brain_dir` - Where docs live (default varies by AI tool)
-- `inbox_folder` - Root for type folders (e.g., `0-Inbox`)
-
-## Folder Structure
-
-Docs are organized by type:
-
-```
-{brain_dir}/{inbox_folder}/
-├── plans/
-├── research/
-├── reviews/
-└── ideas/
-```
-
-## Behavior
-
-Refer to the brain skill for:
-
-- **Opening**: How to fuzzy-match, handle multiple matches, set active
-- **Creating**: Template structure by preset, naming conventions
-- **Ideas**: Quick capture workflow
-- **Adding**: Append to active doc with timestamp
-- **Checking**: Find and address @droid comments
-- **Finalizing**: Update status, suggest next steps
+**Default behavior:** SEARCH first, don't create unless plan/research/review keyword is present.
 
-The skill's `references/` folder contains detailed specs for workflows, templates, naming, and metadata.
+See `/brain` or the **brain skill** for complete documentation.

package/{src/tools/brain/skills/droid-brain → dist/tools/brain/skills/brain}/SKILL.md

@@ -1,10 +1,10 @@
 ---
-name: droid-brain
+name: brain
 description: "Collaborative scratchpad for planning and research. Use when planning a feature, exploring a problem, or capturing thinking that should persist across sessions. User prompts like 'let's think through', 'open a scratchpad', 'plan this out', 'use our brain'."
 globs:
   - "**/brain/**/*.md"
 alwaysApply: false
-allowed-tools: Read, Write, Glob, Grep, Bash
+allowed-tools: [Read, Write, Glob, Grep, Bash]
 ---
 
 # Brain Skill
@@ -39,10 +39,10 @@ Ideas develop through iteration, not single prompts.
 
 **IMPORTANT:** Before using any default paths, ALWAYS read `~/.droid/skills/brain/overrides.yaml` first. If `brain_dir` is configured there, use that path. Only fall back to defaults if the file doesn't exist or lacks a `brain_dir` setting.
 
-| Setting        | Default     | Description                                   |
-| -------------- | ----------- | --------------------------------------------- |
-| `brain_dir`    | (see below) | Where docs are stored                         |
-| `inbox_folder` | (empty)     | Root folder for new docs (e.g., `0-Inbox`)    |
+| Setting        | Default     | Description                                |
+| -------------- | ----------- | ------------------------------------------ |
+| `brain_dir`    | (see below) | Where docs are stored                      |
+| `inbox_folder` | (empty)     | Root folder for new docs (e.g., `0-Inbox`) |
 
 Default `brain_dir` by AI tool (only if not configured):
 

package/dist/tools/brain/skills/{droid-brain-obsidian → brain-obsidian}/SKILL.md

@@ -1,10 +1,10 @@
 ---
-name: droid-brain-obsidian
+name: brain-obsidian
 description: "Obsidian extension for brain skill with YAML frontmatter, wikilinks, and PARA folder organization. Use when your brain docs live in an Obsidian vault."
 globs:
   - "**/brain/**/*.md"
 alwaysApply: false
-allowed-tools: Read, Write, Glob, Grep, Bash
+allowed-tools: [Read, Write, Glob, Grep, Bash]
 ---
 
 # Brain Obsidian Extension
@@ -114,10 +114,10 @@ When running `/brain done`:
 
 Same commands as brain skill, but with Obsidian output:
 
-| Command                   | Obsidian Behavior                             |
-| ------------------------- | --------------------------------------------- |
-| `/brain plan {topic}`     | Creates in `plans/` with frontmatter          |
-| `/brain research {topic}` | Creates in `research/` with frontmatter       |
-| `/brain review {topic}`   | Creates in `reviews/` with frontmatter        |
-| `/brain idea {text}`      | Quick capture to `ideas/`                     |
-| `/brain done`             | Updates status, suggests archive/PARA move    |
+| Command                   | Obsidian Behavior                          |
+| ------------------------- | ------------------------------------------ |
+| `/brain plan {topic}`     | Creates in `plans/` with frontmatter       |
+| `/brain research {topic}` | Creates in `research/` with frontmatter    |
+| `/brain review {topic}`   | Creates in `reviews/` with frontmatter     |
+| `/brain idea {text}`      | Quick capture to `ideas/`                  |
+| `/brain done`             | Updates status, suggests archive/PARA move |

package/dist/tools/coach/.claude-plugin/plugin.json

@@ -0,0 +1,16 @@
+{
+  "name": "droid-coach",
+  "version": "0.2.0",
+  "description": "Learning-mode AI assistance - AI as coach, not crutch. Use /coach plan for co-authored planning, /coach scaffold for structure with hints, /coach review for Socratic questions.",
+  "author": {
+    "name": "Orderful",
+    "url": "https://github.com/orderful"
+  },
+  "repository": "https://github.com/orderful/droid",
+  "license": "MIT",
+  "keywords": [
+    "droid",
+    "ai",
+    "coach"
+  ]
+}

package/dist/tools/coach/TOOL.yaml

@@ -1,14 +1,15 @@
 name: coach
 description: "Learning-mode AI assistance - AI as coach, not crutch. Use /coach plan for co-authored planning, /coach scaffold for structure with hints, /coach review for Socratic questions."
-version: 0.1.3
+version: 0.2.0
 status: beta
 
 includes:
   skills:
-    - name: droid-coach
+    - name: coach
       required: true
   commands:
-    - coach
+    - name: coach
+      is_alias: false
   agents: []
 
 dependencies:

package/dist/tools/coach/commands/coach.md

@@ -1,71 +1,31 @@
 ---
+name: coach
 description: "Learning-mode AI assistance - scaffolds don't implement, questions don't fix"
 argument-hint: "[plan {task} | scaffold [{path}] | review [{path}] | check | challenge [{path}]]"
-allowed-tools: Read, Write, Edit, Glob, Grep, Bash(ls:*)
 ---
 
 # /coach
 
-Entry point for learning-mode AI assistance. See the **coach skill** for full behaviour.
+**User invoked:** `/coach $ARGUMENTS`
 
-## Arguments
+**Your task:** Invoke the **coach skill** with these arguments.
 
-$ARGUMENTS
+**Philosophy:** "AI as coach, not crutch" - preserves learning-through-doing while leveraging AI for guardrails and feedback.
 
-## Philosophy
+## Examples
 
-**"AI as coach, not crutch"** - preserves learning-through-doing while leveraging AI for guardrails and feedback.
+- `/coach plan refactor auth` → Co-authored planning with Socratic questions
+- `/coach scaffold src/lib/auth.ts` → Generate types/signatures for that file
+- `/coach review` → Review recent changes with inline questions
+- `/coach challenge --staged` → Challenge on staged changes
 
-## Usage
+## Quick Reference
 
 ```
 /coach plan {task}          # Co-authored planning with Socratic questions
-/coach scaffold             # Generate types/signatures for current context
-/coach scaffold {path}      # Generate scaffold for specific file/feature
-/coach review               # Review recent changes with inline questions
-/coach review {path}        # Review specific file with inline questions
-/coach check                # Process comment responses (defers to /comments check)
-/coach challenge            # Productive struggle on current file
-/coach challenge {path}     # Challenge on specific file
-/coach challenge --staged   # Challenge on staged changes
+/coach scaffold [{path}]    # Generate types/signatures
+/coach review [{path}]      # Review with inline questions
+/coach challenge [{path}]   # Productive struggle mode
 ```
 
-## Mode Behaviour
-
-### plan
-
-- Co-author, don't dictate
-- ~30% proposing, ~70% questioning
-- Offer to create brain doc for persistence
-
-### scaffold
-
-- Types, signatures, stubs with hint comments
-- Points at what to think about, not the answer
-- Human fills in the actual logic
-
-### review
-
-- Uses comments skill for inline `// @{user}` questions
-- Socratic - probe reasoning, don't fix code
-- Vary questions based on context
-
-### check
-
-- Defers to `/comments check`
-
-### challenge
-
-- Productive struggle - find what you missed
-- Guide discovery, don't give answers
-- Opt-in for those seeking growth
-
-## Configuration
-
-Read `~/.droid/skills/coach/overrides.yaml` for:
-
-- `scaffold_verbosity` - `minimal` | `medium` | `detailed`
-
-## The Golden Rule
-
-**Never write code unless explicitly asked.** Only ask questions, explain tradeoffs, provide hints, or generate structure.
+See the **coach skill** for complete documentation and procedures.

package/{src/tools/coach/skills/droid-coach → dist/tools/coach/skills/coach}/SKILL.md

@@ -1,8 +1,8 @@
 ---
-name: droid-coach
+name: coach
 description: "Learning-mode AI assistance - scaffolds don't implement, questions don't fix. Use when learning a new codebase, wanting to understand deeply, or building skills to retain. User prompts like 'coach me on', 'help me think through', 'I want to learn how to', 'don't just give me the answer'."
 alwaysApply: false
-allowed-tools: Read, Grep, Glob
+allowed-tools: [Read, Grep, Glob]
 ---
 
 # Coach Skill
@@ -40,7 +40,7 @@ plan → AI scaffolds → human implements → AI coaches → iterate → ship
 ## Commands
 
 | Command            | Purpose                                                 |
-|--------------------|---------------------------------------------------------|
+| ------------------ | ------------------------------------------------------- |
 | `/coach plan`      | Co-authored planning with Socratic questions            |
 | `/coach scaffold`  | Generate types/signatures/stubs with hints              |
 | `/coach review`    | Inline questions via comments skill                     |
@@ -50,7 +50,7 @@ plan → AI scaffolds → human implements → AI coaches → iterate → ship
 ## Configuration
 
 | Setting              | Default  | Description                                             |
-|----------------------|----------|---------------------------------------------------------|
+| -------------------- | -------- | ------------------------------------------------------- |
 | `scaffold_verbosity` | `medium` | How detailed hints are: `minimal`, `medium`, `detailed` |
 
 > @fry Not yet - droid currently shows config as free text input. But we could add an `enum` type to the config schema that presents as a select dropdown in the TUI. Good feature request - want me to create an issue for it?
@@ -139,6 +139,7 @@ Read from `~/.droid/skills/coach/overrides.yaml` if present.
 // @fry What happens if this promise rejects?
 // @fry I notice you're mutating state directly - was that intentional?
 ```
+
 > @droid is it worth mentioning using the correct comment syntax for the file language? We typically use TS but could be others
 
 **Key principle:** Vary questions based on specific code and context. Avoid formulaic patterns. Questions show the _spirit_, not a script.

package/dist/tools/code-review/.claude-plugin/plugin.json

@@ -0,0 +1,16 @@
+{
+  "name": "droid-code-review",
+  "version": "0.2.0",
+  "description": "Comprehensive code review using specialized agents. Reviews PRs, staged changes, branches, or specific files with confidence scoring.",
+  "author": {
+    "name": "Orderful",
+    "url": "https://github.com/orderful"
+  },
+  "repository": "https://github.com/orderful/droid",
+  "license": "MIT",
+  "keywords": [
+    "droid",
+    "ai",
+    "code-review"
+  ]
+}

package/dist/tools/code-review/TOOL.yaml

@@ -1,14 +1,15 @@
 name: code-review
 description: "Comprehensive code review using specialized agents. Reviews PRs, staged changes, branches, or specific files with confidence scoring."
-version: 0.1.2
+version: 0.2.0
 status: alpha
 
 includes:
   skills:
-    - name: droid-code-review
+    - name: code-review
       required: true
   commands:
-    - code-review
+    - name: code-review
+      is_alias: false
   agents:
     - edi-standards-reviewer
     - error-handling-reviewer

package/dist/tools/code-review/commands/code-review.md

@@ -1,113 +1,29 @@
 ---
-description: Run comprehensive code review using specialized agents. Accepts PR number, 'staged', 'branch', or file path.
+name: code-review
+description: "Run comprehensive code review using specialized agents. Accepts PR number, 'staged', 'branch', or file path."
 argument-hint: "[#123 | staged | branch | path/to/file.ts]"
-allowed-tools: Task, Bash(git:*), Bash(gh:*), Read, Glob
 ---
 
-# /code-review - Run comprehensive code review using specialized agents
+# /code-review
 
-Review target: $ARGUMENTS
+**User invoked:** `/code-review $ARGUMENTS`
 
-## Usage
+**Your task:** Invoke the **code-review skill** with these arguments.
 
-```
-/code-review #123           # Review PR #123
-/code-review staged         # Review staged changes
-/code-review branch         # Review current branch vs main
-/code-review path/to/file   # Review specific file
-```
-
-### Step 0: Check for Brain Integration
-
-**If the `brain` skill is installed** (check for `~/.claude/skills/brain/SKILL.md` or `~/.config/opencode/skills/brain/SKILL.md`):
-
-Ask the user: **"Would you like the review results saved to a `/brain review` doc?"**
-
-- If yes: Create a brain review doc at the start using `/brain review {PR title or branch name}`
-- The final report will be written to the brain doc instead of just displayed
-- This allows for async discussion via `@droid`/`@{user}` comments
-
-If brain skill is not installed or user declines, proceed with normal terminal output.
-
-### Step 1: Determine Review Scope
-
-Parse the argument to determine what to review:
-
-**If argument starts with `#` or is a number (e.g., `#123` or `123`):**
-
-- This is a PR number
-- Fetch PR details: `gh pr view $PR_NUMBER --json title,body,baseRefName,headRefName,files`
-- Get the diff: `gh pr diff $PR_NUMBER`
-- Note the PR author and description for context
-
-**If argument is `staged` or empty:**
-
-- Review staged changes: `git diff --cached`
-
-**If argument is `branch`:**
-
-- Review current branch vs main: `git diff origin/main...HEAD`
-
-**If argument is a file path:**
-
-- Review specific file: `git diff HEAD -- $FILE_PATH`
-- If no changes, review the entire file for issues
-
-### Step 2: Gather Context
-
-For PR reviews, also fetch:
-
-- PR description (may contain context about the change)
-- Linked issues: `gh pr view $PR_NUMBER --json body` and parse for #issue refs
-- Changed files list for targeted agent assignment
+## Examples
 
-### Step 3: Parallel Agent Reviews
+- `/code-review #123` → Review PR #123 using specialized agents
+- `/code-review staged` → Review currently staged changes
+- `/code-review branch` → Review current branch vs main
+- `/code-review src/lib/auth.ts` → Review specific file
 
-Launch these agents in parallel using the Task tool with `run_in_background: true`:
+## Quick Reference
 
-1. **edi-standards-reviewer**: EDI patterns, partnership handling, billing concerns
-2. **test-coverage-analyzer**: Test completeness and edge cases
-3. **error-handling-reviewer**: Silent failures, missing error handling
-4. **type-reviewer**: Type design, interface contracts
-
-Pass each agent:
-
-1. The diff content
-2. The full file content for changed files (for context)
-3. PR description if available
-
-Use TaskOutput to collect results from all agents.
-
-### Step 4: Confidence Filtering
-
-Each agent returns issues with confidence scores (0-100).
-Filter out issues with confidence < 80.
-
-### Step 5: Synthesize Report
-
-Compile findings into a prioritized report:
-
-**PR #123: "Add partnership billing events"** (if reviewing a PR)
-_Author: @username_
-
-**Critical** (security, data loss, billing errors)
-
-- `file.ts:42` - Issue description
-
-**Important** (bugs, missing tests, type issues)
-
-- `file.ts:67` - Issue description
-
-**Suggestions** (style, readability)
-
-- `file.ts:89` - Issue description
-
-**Summary**: X critical, Y important, Z suggestions across N files.
-
-### Step 6: Offer Actions (for PRs)
-
-After presenting the report, offer:
+```
+/code-review #123           # Review PR
+/code-review staged         # Review staged changes
+/code-review branch         # Review current branch
+/code-review {path}         # Review specific file
+```
 
-- "Would you like me to post this as a PR comment?"
-- "Should I suggest fixes for any of these issues?"
-- "Want me to check out this branch and fix the critical issues?"
+See the **code-review skill** for complete documentation and procedures.