@orderful/droid 0.26.0 → 0.27.0

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

@@ -1,5 +1,5 @@
 ---
-name: droid-project
+name: project
 description: "Persistent project context for AI memory across sessions. Use when working on multi-session features, refactors, or any work that benefits from accumulated context. User prompts like 'load the project', 'update project context', 'what's the current project?'."
 globs:
   - "**/PROJECT.md"
@@ -33,24 +33,25 @@ Chat history disappears. Projects persist.
 - If `projects_dir` is configured → use **ONLY** that path (do NOT also search defaults)
 - If not configured → use the default for current AI tool
 
-| Setting | Default | Description |
-|---------|---------|-------------|
+| Setting        | Default     | Description                                       |
+| -------------- | ----------- | ------------------------------------------------- |
 | `projects_dir` | (see below) | Where projects are stored (use ONE location only) |
-| `preset` | `markdown` | Output format: `markdown` or `obsidian` |
+| `preset`       | `markdown`  | Output format: `markdown` or `obsidian`           |
 
 Default `projects_dir` by AI tool (only if overrides.yaml is missing or lacks `projects_dir`):
+
 - **claude-code**: `~/.claude/projects`
 - **opencode**: `~/.config/opencode/projects`
 
 ## Commands
 
-| Command | Action |
-|---------|--------|
-| `/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 |
+| Command                               | Action                                                 |
+| ------------------------------------- | ------------------------------------------------------ |
+| `/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.
 

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

@@ -1,6 +1,6 @@
 {
   "name": "droid-tech-design",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "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,14 +1,15 @@
 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.1.0
+version: 0.2.0
 status: beta
 
 includes:
   skills:
-    - name: droid-tech-design
+    - name: tech-design
       required: true
   commands:
-    - tech-design
+    - name: tech-design
+      is_alias: false
   agents: []
 
 dependencies:

package/src/tools/tech-design/commands/tech-design.md

@@ -1,93 +1,31 @@
 ---
-description: Write, iterate, and publish technical design documents using a two-document approach - messy thought docs in brain, clean roll-ups in codex
+name: tech-design
+description: "Write, iterate, and publish technical design documents using a three-document approach - research doc, thought doc, and roll-up"
 argument-hint: "[start --from codex:{project} | draft [section] | think [topic] | gaps | publish]"
-allowed-tools: [Read, Write, Edit, Glob, Grep, Bash(gh:*), Bash(git:*), Bash(mkdir:*), Task]
 ---
 
 # /tech-design
 
-Entry point for technical design authoring. See the **tech-design skill** for full behavior.
+**User invoked:** `/tech-design $ARGUMENTS`
 
-> Tech designs are where architectural decisions get made. Make them AI-friendly.
-
-## Arguments
-
-$ARGUMENTS
-
-## Why `/tech-design` not `/design`?
-
-Leaves `/design` open for actual design tooling (Figma workflows, design system docs, UI/UX review).
-
-## Prerequisites
-
-Before first use, verify:
-
-1. **Brain configured** - For thought doc drafting
-2. **Codex configured** - For PRD context and publishing
-3. **gh CLI** - For creating PRs
-
-## Usage
-
-```bash
-# Core Authoring (v1)
-/tech-design start --from codex:{project}  # Create thought doc, pull PRD/DESIGN context
-/tech-design draft [section]                # Auto-generate from PRD + codebase research
-/tech-design think [topic]                  # Guided exploration, stress-test ideas
-/tech-design gaps                           # Checklist of missing/empty sections
-/tech-design publish                        # Generate roll-up + thought doc, open PR to codex
-
-# Self-Review & Interaction (v2 - not yet implemented)
-# /tech-design critic [persona]   # Multi-persona review with severity scoring
-# /tech-design respond {question} # Author tool: search thought doc to draft reply
-# /tech-design ask {question}     # Reviewer tool: search both docs to answer questions
-```
-
-## Configuration
-
-Tech-design has no configuration of its own. It delegates to:
-
-- **Brain skill** - Thought doc location (`brain_dir`, `inbox_folder`)
-- **Codex skill** - Repository location (`codex_repo`)
-
-## Behavior
-
-Refer to the tech-design skill for:
-
-- **Starting**: How to create thought doc from codex context
-- **Drafting**: Research-first, structure-second content generation
-- **Thinking**: Guided exploration to stress-test ideas
-- **Gap Analysis**: What sections are missing or empty
-- **Publishing**: Generate clean roll-up and create PR
-
-The skill's `references/` folder contains detailed procedures for each workflow.
-
-## Two-Document Approach
-
-| Document        | Purpose                                 | Location      |
-| --------------- | --------------------------------------- | ------------- |
-| **Thought doc** | Messy iteration, @mentions, exploration | Brain         |
-| **Roll-up**     | Clean, reviewable, decision-focused     | Codex project |
-
-Both documents published to codex on `/tech-design publish` for full transparency.
+**Your task:** Invoke the **tech-design skill** with these arguments.
 
 ## Examples
 
-```bash
-# Start a new tech design from codex project context
-/tech-design start --from codex:transaction-templates
-
-# Draft the entire doc from PRD and codebase research
-/tech-design draft
-
-# Explore a specific idea before committing to it
-/tech-design think "Should we use events or polling for status updates?"
+- `/tech-design start --from codex:billing-v2` → Create research + thought docs from codex project
+- `/tech-design draft rollout` → Auto-generate the rollout section
+- `/tech-design think API design` → Guided exploration of API design, update research doc
+- `/tech-design gaps` → Show checklist of missing/empty sections
+- `/tech-design publish` → Generate roll-up and publish to codex
 
-# Draft just the rollout section
-/tech-design draft rollout
+## Quick Reference
 
-# See what's missing
-/tech-design gaps
-
-# Publish to codex when ready for review
-/tech-design publish
 ```
+/tech-design start --from codex:{project}  # Create research + thought docs
+/tech-design draft [section]               # Auto-generate section
+/tech-design think [topic]                 # Guided exploration
+/tech-design gaps                          # Missing sections checklist
+/tech-design publish                       # Publish to codex
+```
+
+See the **tech-design skill** for complete documentation and procedures.

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

@@ -1,5 +1,5 @@
 ---
-name: droid-tech-design
+name: tech-design
 description: "Technical design authoring with three-document approach - research doc (codebase discoveries), thought doc (design iteration), and roll-up (clean summary). Use when writing tech designs, drafting sections, exploring architectural ideas, or publishing to codex. User prompts like 'start tech design for X', 'draft the rollout section', 'let's think through the API design', 'publish this to codex'."
 globs: []
 alwaysApply: false

package/dist/tools/code-review/skills/droid-code-review/SKILL.md

@@ -1,55 +0,0 @@
----
-name: droid-code-review
-description: "Comprehensive code review using specialized agents. Use when reviewing PRs, checking staged changes, or analysing code quality. User prompts like 'review this PR', 'check my changes', 'review before I commit'."
-globs:
-  - "**/*"
-alwaysApply: false
-allowed-tools: [Read, Grep, Glob, Bash, Task]
----
-
-# Code Review Skill
-
-Run comprehensive code reviews using specialized agents, each focused on a specific concern.
-
-## How It Works
-
-The `/code-review` command orchestrates multiple specialized agents in parallel:
-
-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** - TypeScript type design, interface contracts
-
-Each agent returns issues with confidence scores (0-100). Issues below 80% confidence are filtered out to reduce noise.
-
-## Usage
-
-```bash
-/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
-```
-
-## Output Format
-
-Reviews are presented in prioritized categories:
-
-🔴 **Critical** - Security, data loss, billing errors
-🟠 **Important** - Bugs, missing tests, type issues
-🟡 **Suggestions** - Style, readability improvements
-
-## Post-Review Actions
-
-After presenting findings, you can:
-- Post the review as a PR comment
-- Get suggested fixes for specific issues
-- Check out the branch and fix critical issues
-
-## Domain-Aware Reviews
-
-The EDI Standards Reviewer discovers project conventions by reading:
-- `.claude/CLAUDE.md` or `CLAUDE.md` for team conventions
-- `AGENTS.md` or `docs/` for architecture guidance
-
-This lets it apply your project's specific patterns rather than generic rules.

package/dist/tools/codex/skills/droid-codex/scripts/git-finish-write.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"git-finish-write.d.ts","sourceRoot":"","sources":["../../../../../../src/tools/codex/skills/droid-codex/scripts/git-finish-write.ts"],"names":[],"mappings":";AACA;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG"}

package/dist/tools/codex/skills/droid-codex/scripts/git-preamble.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"git-preamble.d.ts","sourceRoot":"","sources":["../../../../../../src/tools/codex/skills/droid-codex/scripts/git-preamble.ts"],"names":[],"mappings":";AACA;;;;;;;;;;;;;;;;GAgBG"}

package/dist/tools/codex/skills/droid-codex/scripts/git-start-write.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"git-start-write.d.ts","sourceRoot":"","sources":["../../../../../../src/tools/codex/skills/droid-codex/scripts/git-start-write.ts"],"names":[],"mappings":";AACA;;;;;;;;;;;;;;;;;;;GAmBG"}

package/src/tools/code-review/skills/droid-code-review/SKILL.md

@@ -1,55 +0,0 @@
----
-name: droid-code-review
-description: "Comprehensive code review using specialized agents. Use when reviewing PRs, checking staged changes, or analysing code quality. User prompts like 'review this PR', 'check my changes', 'review before I commit'."
-globs:
-  - "**/*"
-alwaysApply: false
-allowed-tools: [Read, Grep, Glob, Bash, Task]
----
-
-# Code Review Skill
-
-Run comprehensive code reviews using specialized agents, each focused on a specific concern.
-
-## How It Works
-
-The `/code-review` command orchestrates multiple specialized agents in parallel:
-
-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** - TypeScript type design, interface contracts
-
-Each agent returns issues with confidence scores (0-100). Issues below 80% confidence are filtered out to reduce noise.
-
-## Usage
-
-```bash
-/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
-```
-
-## Output Format
-
-Reviews are presented in prioritized categories:
-
-🔴 **Critical** - Security, data loss, billing errors
-🟠 **Important** - Bugs, missing tests, type issues
-🟡 **Suggestions** - Style, readability improvements
-
-## Post-Review Actions
-
-After presenting findings, you can:
-- Post the review as a PR comment
-- Get suggested fixes for specific issues
-- Check out the branch and fix critical issues
-
-## Domain-Aware Reviews
-
-The EDI Standards Reviewer discovers project conventions by reading:
-- `.claude/CLAUDE.md` or `CLAUDE.md` for team conventions
-- `AGENTS.md` or `docs/` for architecture guidance
-
-This lets it apply your project's specific patterns rather than generic rules.