@orderful/droid 0.35.2 → 0.35.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (52) hide show
  1. package/.claude-plugin/marketplace.json +7 -7
  2. package/CHANGELOG.md +31 -0
  3. package/README.md +47 -0
  4. package/dist/tools/brain/.claude-plugin/plugin.json +1 -1
  5. package/dist/tools/brain/TOOL.yaml +1 -1
  6. package/dist/tools/brain/skills/brain/references/workflows.md +14 -1
  7. package/dist/tools/coach/.claude-plugin/plugin.json +1 -1
  8. package/dist/tools/coach/TOOL.yaml +1 -1
  9. package/dist/tools/coach/skills/coach/SKILL.md +1 -1
  10. package/dist/tools/codex/.claude-plugin/plugin.json +1 -1
  11. package/dist/tools/codex/TOOL.yaml +1 -1
  12. package/dist/tools/codex/skills/codex/SKILL.md +1 -0
  13. package/dist/tools/codex/skills/codex/scripts/git-finish-write.d.ts +1 -0
  14. package/dist/tools/codex/skills/codex/scripts/git-finish-write.d.ts.map +1 -1
  15. package/dist/tools/codex/skills/codex/scripts/git-finish-write.ts +19 -4
  16. package/dist/tools/comments/.claude-plugin/plugin.json +1 -1
  17. package/dist/tools/comments/TOOL.yaml +1 -1
  18. package/dist/tools/comments/skills/comments/SKILL.md +1 -1
  19. package/dist/tools/plan/.claude-plugin/plugin.json +1 -1
  20. package/dist/tools/plan/TOOL.yaml +1 -1
  21. package/dist/tools/plan/skills/plan/SKILL.md +1 -0
  22. package/dist/tools/project/.claude-plugin/plugin.json +1 -1
  23. package/dist/tools/project/TOOL.yaml +1 -1
  24. package/dist/tools/project/skills/project/SKILL.md +1 -1
  25. package/dist/tools/tech-design/.claude-plugin/plugin.json +1 -1
  26. package/dist/tools/tech-design/TOOL.yaml +1 -1
  27. package/dist/tools/tech-design/skills/tech-design/SKILL.md +15 -11
  28. package/dist/tools/tech-design/skills/tech-design/references/publish.md +3 -2
  29. package/package.json +1 -1
  30. package/src/tools/brain/.claude-plugin/plugin.json +1 -1
  31. package/src/tools/brain/TOOL.yaml +1 -1
  32. package/src/tools/brain/skills/brain/references/workflows.md +14 -1
  33. package/src/tools/coach/.claude-plugin/plugin.json +1 -1
  34. package/src/tools/coach/TOOL.yaml +1 -1
  35. package/src/tools/coach/skills/coach/SKILL.md +1 -1
  36. package/src/tools/codex/.claude-plugin/plugin.json +1 -1
  37. package/src/tools/codex/TOOL.yaml +1 -1
  38. package/src/tools/codex/skills/codex/SKILL.md +1 -0
  39. package/src/tools/codex/skills/codex/scripts/git-finish-write.ts +19 -4
  40. package/src/tools/comments/.claude-plugin/plugin.json +1 -1
  41. package/src/tools/comments/TOOL.yaml +1 -1
  42. package/src/tools/comments/skills/comments/SKILL.md +1 -1
  43. package/src/tools/plan/.claude-plugin/plugin.json +1 -1
  44. package/src/tools/plan/TOOL.yaml +1 -1
  45. package/src/tools/plan/skills/plan/SKILL.md +1 -0
  46. package/src/tools/project/.claude-plugin/plugin.json +1 -1
  47. package/src/tools/project/TOOL.yaml +1 -1
  48. package/src/tools/project/skills/project/SKILL.md +1 -1
  49. package/src/tools/tech-design/.claude-plugin/plugin.json +1 -1
  50. package/src/tools/tech-design/TOOL.yaml +1 -1
  51. package/src/tools/tech-design/skills/tech-design/SKILL.md +15 -11
  52. package/src/tools/tech-design/skills/tech-design/references/publish.md +3 -2
@@ -22,7 +22,7 @@
22
22
  {
23
23
  "name": "droid-brain",
24
24
  "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.",
25
- "version": "0.3.6",
25
+ "version": "0.3.7",
26
26
  "source": {
27
27
  "source": "github",
28
28
  "repo": "orderful/droid",
@@ -35,7 +35,7 @@
35
35
  {
36
36
  "name": "droid-coach",
37
37
  "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.",
38
- "version": "0.2.3",
38
+ "version": "0.2.4",
39
39
  "source": {
40
40
  "source": "github",
41
41
  "repo": "orderful/droid",
@@ -61,7 +61,7 @@
61
61
  {
62
62
  "name": "droid-codex",
63
63
  "description": "Shared organizational knowledge - PRDs, tech designs, domains, proposals, patterns, and explored topics. Use when loading project context, searching codex, capturing decisions, or creating new entries.",
64
- "version": "0.2.1",
64
+ "version": "0.2.2",
65
65
  "source": {
66
66
  "source": "github",
67
67
  "repo": "orderful/droid",
@@ -74,7 +74,7 @@
74
74
  {
75
75
  "name": "droid-comments",
76
76
  "description": "Enable inline conversations using @droid/@user markers. Tag @droid to ask the AI, AI responds with @{your-name}. Use /comments check to address markers, /comments cleanup to remove resolved threads. Ideal for code review notes and async collaboration.",
77
- "version": "0.3.3",
77
+ "version": "0.3.4",
78
78
  "source": {
79
79
  "source": "github",
80
80
  "repo": "orderful/droid",
@@ -87,7 +87,7 @@
87
87
  {
88
88
  "name": "droid-plan",
89
89
  "description": "Task-scoped planning with portable, structured plans. Use when planning implementation for a PR, ticket, or small feature. User prompts like 'let's plan this', 'can we start a plan', 'think through the implementation'.",
90
- "version": "0.1.1",
90
+ "version": "0.1.2",
91
91
  "source": {
92
92
  "source": "github",
93
93
  "repo": "orderful/droid",
@@ -100,7 +100,7 @@
100
100
  {
101
101
  "name": "droid-project",
102
102
  "description": "Manage project context files for persistent AI memory across sessions. Load, update, or create project context before working on multi-session features.",
103
- "version": "0.3.3",
103
+ "version": "0.3.4",
104
104
  "source": {
105
105
  "source": "github",
106
106
  "repo": "orderful/droid",
@@ -113,7 +113,7 @@
113
113
  {
114
114
  "name": "droid-tech-design",
115
115
  "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).",
116
- "version": "0.2.3",
116
+ "version": "0.2.4",
117
117
  "source": {
118
118
  "source": "github",
119
119
  "repo": "orderful/droid",
package/CHANGELOG.md CHANGED
@@ -1,5 +1,36 @@
1
1
  # @orderful/droid
2
2
 
3
+ ## 0.35.4
4
+
5
+ ### Patch Changes
6
+
7
+ - [#220](https://github.com/Orderful/droid/pull/220) [`cbe48f7`](https://github.com/Orderful/droid/commit/cbe48f71f177465886f65f27b914edf990612203) Thanks [@frytyler](https://github.com/frytyler)! - Add argument-hint to plan skill for better CLI discoverability
8
+
9
+ - [#218](https://github.com/Orderful/droid/pull/218) [`47ba4ac`](https://github.com/Orderful/droid/commit/47ba4acf690595ed5c0f20645b5b5c20dcc9610a) Thanks [@frytyler](https://github.com/frytyler)! - Improve tech-design skill documentation and add needs-review label support
10
+ - Add comment convention table clarifying @droid/@user mention semantics
11
+ - Add --labels parameter to git-finish-write script for PR label support
12
+ - Configure tech-design publish to add needs-review label (prevents auto-merge)
13
+ - Remove unimplemented v2 commands from main Commands table
14
+
15
+ ## 0.35.3
16
+
17
+ ### Patch Changes
18
+
19
+ - [#215](https://github.com/Orderful/droid/pull/215) [`5241570`](https://github.com/Orderful/droid/commit/5241570ab1b14bb819c5635834706ad67f0525a2) Thanks [@frytyler](https://github.com/frytyler)! - Fix brain comment responses blockquoting section content
20
+
21
+ When responding to `> @droid` comments in brain docs, Claude was wrapping all subsequent section content in blockquotes. Now only the `> @fry` response line is blockquoted, with substantive content (sections, analysis) in regular markdown for better readability.
22
+
23
+ - [#217](https://github.com/Orderful/droid/pull/217) [`6484016`](https://github.com/Orderful/droid/commit/648401686c3e6c5f59ccb08d55947beb3170d352) Thanks [@frytyler](https://github.com/frytyler)! - fix(skills): add Bash to allowed-tools for skills using droid config commands
24
+
25
+ Multiple skills require running `droid config --get` commands but didn't have Bash in their allowed-tools list. This caused them to fail when trying to read configuration.
26
+
27
+ Fixed skills:
28
+ - coach (0.2.4): Added Bash to allowed-tools
29
+ - codex (0.2.2): Added Bash(droid:\*) to allowed-tools
30
+ - comments (0.3.4): Added Bash to allowed-tools
31
+ - tech-design (0.2.4): Added Bash(droid:\*) to allowed-tools
32
+ - project (0.3.4): Added Bash to allowed-tools
33
+
3
34
  ## 0.35.2
4
35
 
5
36
  ### Patch Changes
package/README.md CHANGED
@@ -12,6 +12,53 @@ AI workflow toolkit for sharing tools, commands, and agents across the engineeri
12
12
  - **Share what works** - Power users discover great workflows, everyone benefits
13
13
  - **Consistent experience** - Common patterns like `@droid`/`@user` comments work the same across the team
14
14
 
15
+ ## Prerequisites
16
+
17
+ Before installing droid:
18
+
19
+ | Requirement | Why | Install |
20
+ |-------------|-----|---------|
21
+ | **npm login to @orderful** | Droid is published to our private npm org | `npm login` (use Orderful credentials) |
22
+ | **bun** | Required for `droid exec` scripts | [bun.sh](https://bun.sh) |
23
+ | **gh** (GitHub CLI) | Highly recommended for PR workflows | [cli.github.com](https://cli.github.com) |
24
+ | **Obsidian** | Recommended for brain/codex markdown editing | [obsidian.md](https://obsidian.md) |
25
+
26
+ ## Setup Gotchas
27
+
28
+ Things that trip people up:
29
+
30
+ ### Claude Code not found after install
31
+
32
+ If `claude` command isn't found in new terminal windows, add to your shell rc file (`.bashrc`, `.zshrc`):
33
+
34
+ ```bash
35
+ export PATH="$HOME/.local/bin:$PATH"
36
+ ```
37
+
38
+ Then restart your terminal or `source` the file.
39
+
40
+ ### Check your settings before diving in
41
+
42
+ After install, review your configuration before starting a session:
43
+
44
+ ```bash
45
+ droid config # View global settings
46
+ droid # TUI → Settings tab for tool-specific config
47
+ ```
48
+
49
+ Make sure username, paths, and tool settings match what you want.
50
+
51
+ ### Updates require restart
52
+
53
+ When droid auto-updates (or you run `droid update`), the package updates but you need to:
54
+
55
+ 1. Restart droid to pick up the new version
56
+ 2. Run tool updates separately if needed (`droid update` in TUI)
57
+
58
+ ### Cursor support
59
+
60
+ Cursor integration currently requires the **nightly build** of Cursor.
61
+
15
62
  ## Quick Start
16
63
 
17
64
  ### Option A: Claude Code Plugin (Recommended for Claude Code users)
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "droid-brain",
3
- "version": "0.3.6",
3
+ "version": "0.3.7",
4
4
  "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.",
5
5
  "author": {
6
6
  "name": "Orderful",
@@ -1,6 +1,6 @@
1
1
  name: brain
2
2
  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."
3
- version: 0.3.6
3
+ version: 0.3.7
4
4
  status: beta
5
5
 
6
6
  includes:
@@ -177,8 +177,21 @@ Detailed procedures for each brain operation.
177
177
  - Add response as blockquote with user's mention (from `droid config --get tools.brain`): `> @{user_mention} Your response here`
178
178
  - Example: `> @{user} Yes, the index covers that query pattern.`
179
179
  - **CRITICAL:** NEVER use `@droid` in your responses. Use `@{user_mention}` from config (e.g., `@{user}`)
180
- - **CRITICAL:** Always include the `>` prefix to maintain blockquote formatting
180
+ - **CRITICAL:** Always include the `>` prefix for the @mention response line to maintain blockquote formatting
181
181
  - **CRITICAL:** If `preserve_comments: true`, keep the original `@droid` comment and add your response below it. Do NOT remove the original comment.
182
+ - **CRITICAL:** When adding substantive content (sections, analysis, etc.) AFTER your `> @{user_mention}` response, use regular markdown formatting (NOT blockquoted). Only the @mention line should be blockquoted.
183
+
184
+ **Format example:**
185
+ ```markdown
186
+ > @droid Show me the architecture section
187
+
188
+ > @{user_mention} Here's the architecture section.
189
+
190
+ ## Architecture
191
+
192
+ The system uses a three-tier architecture...
193
+ (regular markdown, NOT blockquoted)
194
+ ```
182
195
 
183
196
  6. **Update the doc** with responses
184
197
 
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "droid-coach",
3
- "version": "0.2.3",
3
+ "version": "0.2.4",
4
4
  "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.",
5
5
  "author": {
6
6
  "name": "Orderful",
@@ -1,6 +1,6 @@
1
1
  name: coach
2
2
  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."
3
- version: 0.2.3
3
+ version: 0.2.4
4
4
  status: beta
5
5
 
6
6
  includes:
@@ -2,7 +2,7 @@
2
2
  name: coach
3
3
  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'."
4
4
  argument-hint: "[plan {task} | scaffold [{path}] | review [{path}] | check | challenge [{path}]]"
5
- allowed-tools: [Read, Grep, Glob]
5
+ allowed-tools: [Read, Grep, Glob, Bash]
6
6
  ---
7
7
 
8
8
  # Coach Skill
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "droid-codex",
3
- "version": "0.2.1",
3
+ "version": "0.2.2",
4
4
  "description": "Shared organizational knowledge - PRDs, tech designs, domains, proposals, patterns, and explored topics. Use when loading project context, searching codex, capturing decisions, or creating new entries.",
5
5
  "author": {
6
6
  "name": "Orderful",
@@ -1,6 +1,6 @@
1
1
  name: codex
2
2
  description: "Shared organizational knowledge - PRDs, tech designs, domains, proposals, patterns, and explored topics. Use when loading project context, searching codex, capturing decisions, or creating new entries."
3
- version: 0.2.1
3
+ version: 0.2.2
4
4
  status: beta
5
5
 
6
6
  includes:
@@ -13,6 +13,7 @@ allowed-tools:
13
13
  Bash(git:*),
14
14
  Bash(ls:*),
15
15
  Bash(mkdir:*),
16
+ Bash(droid:*),
16
17
  ]
17
18
  ---
18
19
 
@@ -16,6 +16,7 @@
16
16
  * --message <text> Commit message (required)
17
17
  * --pr-title <text> PR title (required)
18
18
  * --pr-body <text> PR body (optional, defaults to commit message)
19
+ * --labels <text> Comma-separated labels (optional)
19
20
  *
20
21
  * What it does:
21
22
  * 1. Stage all changes
@@ -1 +1 @@
1
- {"version":3,"file":"git-finish-write.d.ts","sourceRoot":"","sources":["../../../../../../src/tools/codex/skills/codex/scripts/git-finish-write.ts"],"names":[],"mappings":";AACA;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG"}
1
+ {"version":3,"file":"git-finish-write.d.ts","sourceRoot":"","sources":["../../../../../../src/tools/codex/skills/codex/scripts/git-finish-write.ts"],"names":[],"mappings":";AACA;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG"}
@@ -16,6 +16,7 @@
16
16
  * --message <text> Commit message (required)
17
17
  * --pr-title <text> PR title (required)
18
18
  * --pr-body <text> PR body (optional, defaults to commit message)
19
+ * --labels <text> Comma-separated labels (optional)
19
20
  *
20
21
  * What it does:
21
22
  * 1. Stage all changes
@@ -47,11 +48,13 @@ function parseArgs(args: string[]): {
47
48
  message: string | null;
48
49
  prTitle: string | null;
49
50
  prBody: string | null;
51
+ labels: string | null;
50
52
  } {
51
53
  let config: Config | null = null;
52
54
  let message: string | null = null;
53
55
  let prTitle: string | null = null;
54
56
  let prBody: string | null = null;
57
+ let labels: string | null = null;
55
58
 
56
59
  for (let i = 0; i < args.length; i++) {
57
60
  const arg = args[i];
@@ -69,10 +72,12 @@ function parseArgs(args: string[]): {
69
72
  prTitle = args[++i];
70
73
  } else if (arg === '--pr-body' && args[i + 1]) {
71
74
  prBody = args[++i];
75
+ } else if (arg === '--labels' && args[i + 1]) {
76
+ labels = args[++i];
72
77
  }
73
78
  }
74
79
 
75
- return { config, message, prTitle, prBody };
80
+ return { config, message, prTitle, prBody, labels };
76
81
  }
77
82
 
78
83
  function expandPath(p: string): string {
@@ -100,7 +105,8 @@ function gitFinishWrite(
100
105
  repoPath: string,
101
106
  commitMessage: string,
102
107
  prTitle: string,
103
- prBody: string
108
+ prBody: string,
109
+ labels?: string
104
110
  ): Result {
105
111
  const cwd = expandPath(repoPath);
106
112
 
@@ -173,6 +179,14 @@ function gitFinishWrite(
173
179
  }
174
180
  }
175
181
 
182
+ // 4.5. Add labels if specified
183
+ if (labels) {
184
+ const addLabels = run(`gh pr edit --add-label "${labels}"`, cwd);
185
+ if (!addLabels.ok) {
186
+ console.error(`Warning: Failed to add labels: ${addLabels.output}`);
187
+ }
188
+ }
189
+
176
190
  // 5. Return to main
177
191
  const checkoutMain = run('git checkout main', cwd);
178
192
  if (!checkoutMain.ok) {
@@ -189,7 +203,7 @@ function gitFinishWrite(
189
203
 
190
204
  // Main
191
205
  const args = process.argv.slice(2);
192
- const { config, message, prTitle, prBody } = parseArgs(args);
206
+ const { config, message, prTitle, prBody, labels } = parseArgs(args);
193
207
 
194
208
  if (!config) {
195
209
  console.log(JSON.stringify({
@@ -227,7 +241,8 @@ const result = gitFinishWrite(
227
241
  config.codex_repo,
228
242
  message,
229
243
  prTitle,
230
- prBody || message
244
+ prBody || message,
245
+ labels || undefined
231
246
  );
232
247
  console.log(JSON.stringify(result, null, 2));
233
248
 
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "droid-comments",
3
- "version": "0.3.3",
3
+ "version": "0.3.4",
4
4
  "description": "Enable inline conversations using @droid/@user markers. Tag @droid to ask the AI, AI responds with @{your-name}. Use /comments check to address markers, /comments cleanup to remove resolved threads. Ideal for code review notes and async collaboration.",
5
5
  "author": {
6
6
  "name": "Orderful",
@@ -1,6 +1,6 @@
1
1
  name: comments
2
2
  description: "Enable inline conversations using @droid/@user markers. Tag @droid to ask the AI, AI responds with @{your-name}. Use /comments check to address markers, /comments cleanup to remove resolved threads. Ideal for code review notes and async collaboration."
3
- version: 0.3.3
3
+ version: 0.3.4
4
4
  status: beta
5
5
 
6
6
  includes:
@@ -2,7 +2,7 @@
2
2
  name: comments
3
3
  description: "Inline conversations using @droid/@user markers in any file. Use when leaving async questions in code or having discussion that should stay near the code. User prompts like 'check for comments', 'address the @droid markers', 'clean up resolved comments'."
4
4
  argument-hint: "[check [{path}] | cleanup]"
5
- allowed-tools: [Read, Grep, Glob, Edit]
5
+ allowed-tools: [Read, Grep, Glob, Edit, Bash]
6
6
  ---
7
7
 
8
8
  # Comments Skill
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "droid-plan",
3
- "version": "0.1.1",
3
+ "version": "0.1.2",
4
4
  "description": "Task-scoped planning with portable, structured plans. Use when planning implementation for a PR, ticket, or small feature. User prompts like 'let's plan this', 'can we start a plan', 'think through the implementation'.",
5
5
  "author": {
6
6
  "name": "Orderful",
@@ -1,6 +1,6 @@
1
1
  name: plan
2
2
  description: "Task-scoped planning with portable, structured plans. Use when planning implementation for a PR, ticket, or small feature. User prompts like 'let's plan this', 'can we start a plan', 'think through the implementation'."
3
- version: 0.1.1
3
+ version: 0.1.2
4
4
  status: alpha
5
5
 
6
6
  includes:
@@ -1,6 +1,7 @@
1
1
  ---
2
2
  name: plan
3
3
  description: "Task-scoped planning with portable, structured plans. Use when planning implementation for a PR, ticket, or small feature. User prompts like 'let's plan this', 'can we start a plan', 'think through the implementation'."
4
+ argument-hint: "[new {topic} | search {topic} | check | ready | implement]"
4
5
  allowed-tools: [Read, Edit, Write, Glob, Grep, Bash, Task, AskUserQuestion]
5
6
  ---
6
7
 
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "droid-project",
3
- "version": "0.3.3",
3
+ "version": "0.3.4",
4
4
  "description": "Manage project context files for persistent AI memory across sessions. Load, update, or create project context before working on multi-session features.",
5
5
  "author": {
6
6
  "name": "Orderful",
@@ -1,6 +1,6 @@
1
1
  name: project
2
2
  description: "Manage project context files for persistent AI memory across sessions. Load, update, or create project context before working on multi-session features."
3
- version: 0.3.3
3
+ version: 0.3.4
4
4
  status: beta
5
5
 
6
6
  includes:
@@ -2,7 +2,7 @@
2
2
  name: project
3
3
  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?'."
4
4
  argument-hint: "[{keywords} | update | create {name}]"
5
- allowed-tools: [Read, Write, Glob, Grep]
5
+ allowed-tools: [Read, Write, Glob, Grep, Bash]
6
6
  ---
7
7
 
8
8
  # Project Skill
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "droid-tech-design",
3
- "version": "0.2.3",
3
+ "version": "0.2.4",
4
4
  "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).",
5
5
  "author": {
6
6
  "name": "Orderful",
@@ -1,6 +1,6 @@
1
1
  name: tech-design
2
2
  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)."
3
- version: 0.2.3
3
+ version: 0.2.4
4
4
  status: beta
5
5
 
6
6
  includes:
@@ -3,7 +3,7 @@ name: tech-design
3
3
  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'."
4
4
  argument-hint: "[start --from codex:{project} | draft [section] | think [topic] | gaps | publish]"
5
5
  allowed-tools:
6
- [Read, Write, Edit, Glob, Grep, Bash(gh:*), Bash(git:*), Bash(mkdir:*), Task]
6
+ [Read, Write, Edit, Glob, Grep, Bash(gh:*), Bash(git:*), Bash(mkdir:*), Bash(droid:*), Task]
7
7
  ---
8
8
 
9
9
  # Tech Design Skill
@@ -68,6 +68,13 @@ Tech-design has no configuration of its own. It delegates to:
68
68
  - Iterates with `@droid`/`@user` comments (the @mention is the **target**: `@droid` = user asking AI, `@user` = AI asking user)
69
69
  - Captures the "why" behind choices
70
70
 
71
+ **Comment conventions for async back-and-forth:**
72
+
73
+ | Comment | Author | Target | Meaning |
74
+ | -------------- | ------ | ------ | -------------------------- |
75
+ | `> @droid ...` | User | AI | User asking/telling the AI |
76
+ | `> @user ...` | AI | User | AI asking/telling the user |
77
+
71
78
  3. **Roll-up** = Reviewer artifact
72
79
  - Synthesized from thought doc
73
80
  - Decision-focused, no exploration noise
@@ -79,16 +86,13 @@ Both thought doc and roll-up are published to codex. Research doc stays in brain
79
86
 
80
87
  ## Commands
81
88
 
82
- | Command | Action | Status |
83
- | ------------------------------------------- | -------------------------------------------------------- | ------ |
84
- | `/tech-design start --from codex:{project}` | Create research + thought docs, pull PRD/DESIGN context | v1 |
85
- | `/tech-design draft [section]` | Auto-generate from research doc + codebase exploration | v1 |
86
- | `/tech-design think [topic]` | Guided exploration, updates research doc with findings | v1 |
87
- | `/tech-design gaps` | Checklist of missing/empty sections | v1 |
88
- | `/tech-design publish` | Generate roll-up, publish thought doc + roll-up to codex | v1 |
89
- | `/tech-design critic [persona]` | Multi-persona review with severity scoring | v2 |
90
- | `/tech-design respond {question}` | Author tool: search thought doc to draft reply | v2 |
91
- | `/tech-design ask {question}` | Reviewer tool: search both docs to answer questions | v2 |
89
+ | Command | Action |
90
+ | ------------------------------------------- | -------------------------------------------------------- |
91
+ | `/tech-design start --from codex:{project}` | Create research + thought docs, pull PRD/DESIGN context |
92
+ | `/tech-design draft [section]` | Auto-generate from research doc + codebase exploration |
93
+ | `/tech-design think [topic]` | Guided exploration, updates research doc with findings |
94
+ | `/tech-design gaps` | Checklist of missing/empty sections |
95
+ | `/tech-design publish` | Generate roll-up, publish thought doc + roll-up to codex |
92
96
 
93
97
  ## Conversational Skill Matching
94
98
 
@@ -231,12 +231,13 @@ After approval:
231
231
  - [ ] Add key decisions to DECISIONS.md
232
232
  - [ ] Begin implementation"
233
233
 
234
- # Use codex skill's git-finish-write script
234
+ # Use codex skill's git-finish-write script with needs-review label
235
235
  droid config --get tools.codex | droid exec droid-codex git-finish-write \
236
236
  --config - \
237
237
  --message "$commit_msg" \
238
238
  --pr-title "$pr_title" \
239
- --pr-body "$pr_body"
239
+ --pr-body "$pr_body" \
240
+ --labels "needs-review"
240
241
  ```
241
242
 
242
243
  ### 8. Output Success
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@orderful/droid",
3
- "version": "0.35.2",
3
+ "version": "0.35.4",
4
4
  "description": "AI workflow toolkit for sharing skills, commands, and agents across the team",
5
5
  "type": "module",
6
6
  "bin": {
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "droid-brain",
3
- "version": "0.3.6",
3
+ "version": "0.3.7",
4
4
  "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.",
5
5
  "author": {
6
6
  "name": "Orderful",
@@ -1,6 +1,6 @@
1
1
  name: brain
2
2
  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."
3
- version: 0.3.6
3
+ version: 0.3.7
4
4
  status: beta
5
5
 
6
6
  includes:
@@ -177,8 +177,21 @@ Detailed procedures for each brain operation.
177
177
  - Add response as blockquote with user's mention (from `droid config --get tools.brain`): `> @{user_mention} Your response here`
178
178
  - Example: `> @{user} Yes, the index covers that query pattern.`
179
179
  - **CRITICAL:** NEVER use `@droid` in your responses. Use `@{user_mention}` from config (e.g., `@{user}`)
180
- - **CRITICAL:** Always include the `>` prefix to maintain blockquote formatting
180
+ - **CRITICAL:** Always include the `>` prefix for the @mention response line to maintain blockquote formatting
181
181
  - **CRITICAL:** If `preserve_comments: true`, keep the original `@droid` comment and add your response below it. Do NOT remove the original comment.
182
+ - **CRITICAL:** When adding substantive content (sections, analysis, etc.) AFTER your `> @{user_mention}` response, use regular markdown formatting (NOT blockquoted). Only the @mention line should be blockquoted.
183
+
184
+ **Format example:**
185
+ ```markdown
186
+ > @droid Show me the architecture section
187
+
188
+ > @{user_mention} Here's the architecture section.
189
+
190
+ ## Architecture
191
+
192
+ The system uses a three-tier architecture...
193
+ (regular markdown, NOT blockquoted)
194
+ ```
182
195
 
183
196
  6. **Update the doc** with responses
184
197
 
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "droid-coach",
3
- "version": "0.2.3",
3
+ "version": "0.2.4",
4
4
  "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.",
5
5
  "author": {
6
6
  "name": "Orderful",
@@ -1,6 +1,6 @@
1
1
  name: coach
2
2
  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."
3
- version: 0.2.3
3
+ version: 0.2.4
4
4
  status: beta
5
5
 
6
6
  includes:
@@ -2,7 +2,7 @@
2
2
  name: coach
3
3
  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'."
4
4
  argument-hint: "[plan {task} | scaffold [{path}] | review [{path}] | check | challenge [{path}]]"
5
- allowed-tools: [Read, Grep, Glob]
5
+ allowed-tools: [Read, Grep, Glob, Bash]
6
6
  ---
7
7
 
8
8
  # Coach Skill
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "droid-codex",
3
- "version": "0.2.1",
3
+ "version": "0.2.2",
4
4
  "description": "Shared organizational knowledge - PRDs, tech designs, domains, proposals, patterns, and explored topics. Use when loading project context, searching codex, capturing decisions, or creating new entries.",
5
5
  "author": {
6
6
  "name": "Orderful",
@@ -1,6 +1,6 @@
1
1
  name: codex
2
2
  description: "Shared organizational knowledge - PRDs, tech designs, domains, proposals, patterns, and explored topics. Use when loading project context, searching codex, capturing decisions, or creating new entries."
3
- version: 0.2.1
3
+ version: 0.2.2
4
4
  status: beta
5
5
 
6
6
  includes:
@@ -13,6 +13,7 @@ allowed-tools:
13
13
  Bash(git:*),
14
14
  Bash(ls:*),
15
15
  Bash(mkdir:*),
16
+ Bash(droid:*),
16
17
  ]
17
18
  ---
18
19
 
@@ -16,6 +16,7 @@
16
16
  * --message <text> Commit message (required)
17
17
  * --pr-title <text> PR title (required)
18
18
  * --pr-body <text> PR body (optional, defaults to commit message)
19
+ * --labels <text> Comma-separated labels (optional)
19
20
  *
20
21
  * What it does:
21
22
  * 1. Stage all changes
@@ -47,11 +48,13 @@ function parseArgs(args: string[]): {
47
48
  message: string | null;
48
49
  prTitle: string | null;
49
50
  prBody: string | null;
51
+ labels: string | null;
50
52
  } {
51
53
  let config: Config | null = null;
52
54
  let message: string | null = null;
53
55
  let prTitle: string | null = null;
54
56
  let prBody: string | null = null;
57
+ let labels: string | null = null;
55
58
 
56
59
  for (let i = 0; i < args.length; i++) {
57
60
  const arg = args[i];
@@ -69,10 +72,12 @@ function parseArgs(args: string[]): {
69
72
  prTitle = args[++i];
70
73
  } else if (arg === '--pr-body' && args[i + 1]) {
71
74
  prBody = args[++i];
75
+ } else if (arg === '--labels' && args[i + 1]) {
76
+ labels = args[++i];
72
77
  }
73
78
  }
74
79
 
75
- return { config, message, prTitle, prBody };
80
+ return { config, message, prTitle, prBody, labels };
76
81
  }
77
82
 
78
83
  function expandPath(p: string): string {
@@ -100,7 +105,8 @@ function gitFinishWrite(
100
105
  repoPath: string,
101
106
  commitMessage: string,
102
107
  prTitle: string,
103
- prBody: string
108
+ prBody: string,
109
+ labels?: string
104
110
  ): Result {
105
111
  const cwd = expandPath(repoPath);
106
112
 
@@ -173,6 +179,14 @@ function gitFinishWrite(
173
179
  }
174
180
  }
175
181
 
182
+ // 4.5. Add labels if specified
183
+ if (labels) {
184
+ const addLabels = run(`gh pr edit --add-label "${labels}"`, cwd);
185
+ if (!addLabels.ok) {
186
+ console.error(`Warning: Failed to add labels: ${addLabels.output}`);
187
+ }
188
+ }
189
+
176
190
  // 5. Return to main
177
191
  const checkoutMain = run('git checkout main', cwd);
178
192
  if (!checkoutMain.ok) {
@@ -189,7 +203,7 @@ function gitFinishWrite(
189
203
 
190
204
  // Main
191
205
  const args = process.argv.slice(2);
192
- const { config, message, prTitle, prBody } = parseArgs(args);
206
+ const { config, message, prTitle, prBody, labels } = parseArgs(args);
193
207
 
194
208
  if (!config) {
195
209
  console.log(JSON.stringify({
@@ -227,7 +241,8 @@ const result = gitFinishWrite(
227
241
  config.codex_repo,
228
242
  message,
229
243
  prTitle,
230
- prBody || message
244
+ prBody || message,
245
+ labels || undefined
231
246
  );
232
247
  console.log(JSON.stringify(result, null, 2));
233
248
 
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "droid-comments",
3
- "version": "0.3.3",
3
+ "version": "0.3.4",
4
4
  "description": "Enable inline conversations using @droid/@user markers. Tag @droid to ask the AI, AI responds with @{your-name}. Use /comments check to address markers, /comments cleanup to remove resolved threads. Ideal for code review notes and async collaboration.",
5
5
  "author": {
6
6
  "name": "Orderful",
@@ -1,6 +1,6 @@
1
1
  name: comments
2
2
  description: "Enable inline conversations using @droid/@user markers. Tag @droid to ask the AI, AI responds with @{your-name}. Use /comments check to address markers, /comments cleanup to remove resolved threads. Ideal for code review notes and async collaboration."
3
- version: 0.3.3
3
+ version: 0.3.4
4
4
  status: beta
5
5
 
6
6
  includes:
@@ -2,7 +2,7 @@
2
2
  name: comments
3
3
  description: "Inline conversations using @droid/@user markers in any file. Use when leaving async questions in code or having discussion that should stay near the code. User prompts like 'check for comments', 'address the @droid markers', 'clean up resolved comments'."
4
4
  argument-hint: "[check [{path}] | cleanup]"
5
- allowed-tools: [Read, Grep, Glob, Edit]
5
+ allowed-tools: [Read, Grep, Glob, Edit, Bash]
6
6
  ---
7
7
 
8
8
  # Comments Skill
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "droid-plan",
3
- "version": "0.1.1",
3
+ "version": "0.1.2",
4
4
  "description": "Task-scoped planning with portable, structured plans. Use when planning implementation for a PR, ticket, or small feature. User prompts like 'let's plan this', 'can we start a plan', 'think through the implementation'.",
5
5
  "author": {
6
6
  "name": "Orderful",
@@ -1,6 +1,6 @@
1
1
  name: plan
2
2
  description: "Task-scoped planning with portable, structured plans. Use when planning implementation for a PR, ticket, or small feature. User prompts like 'let's plan this', 'can we start a plan', 'think through the implementation'."
3
- version: 0.1.1
3
+ version: 0.1.2
4
4
  status: alpha
5
5
 
6
6
  includes:
@@ -1,6 +1,7 @@
1
1
  ---
2
2
  name: plan
3
3
  description: "Task-scoped planning with portable, structured plans. Use when planning implementation for a PR, ticket, or small feature. User prompts like 'let's plan this', 'can we start a plan', 'think through the implementation'."
4
+ argument-hint: "[new {topic} | search {topic} | check | ready | implement]"
4
5
  allowed-tools: [Read, Edit, Write, Glob, Grep, Bash, Task, AskUserQuestion]
5
6
  ---
6
7
 
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "droid-project",
3
- "version": "0.3.3",
3
+ "version": "0.3.4",
4
4
  "description": "Manage project context files for persistent AI memory across sessions. Load, update, or create project context before working on multi-session features.",
5
5
  "author": {
6
6
  "name": "Orderful",
@@ -1,6 +1,6 @@
1
1
  name: project
2
2
  description: "Manage project context files for persistent AI memory across sessions. Load, update, or create project context before working on multi-session features."
3
- version: 0.3.3
3
+ version: 0.3.4
4
4
  status: beta
5
5
 
6
6
  includes:
@@ -2,7 +2,7 @@
2
2
  name: project
3
3
  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?'."
4
4
  argument-hint: "[{keywords} | update | create {name}]"
5
- allowed-tools: [Read, Write, Glob, Grep]
5
+ allowed-tools: [Read, Write, Glob, Grep, Bash]
6
6
  ---
7
7
 
8
8
  # Project Skill
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "droid-tech-design",
3
- "version": "0.2.3",
3
+ "version": "0.2.4",
4
4
  "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).",
5
5
  "author": {
6
6
  "name": "Orderful",
@@ -1,6 +1,6 @@
1
1
  name: tech-design
2
2
  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)."
3
- version: 0.2.3
3
+ version: 0.2.4
4
4
  status: beta
5
5
 
6
6
  includes:
@@ -3,7 +3,7 @@ name: tech-design
3
3
  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'."
4
4
  argument-hint: "[start --from codex:{project} | draft [section] | think [topic] | gaps | publish]"
5
5
  allowed-tools:
6
- [Read, Write, Edit, Glob, Grep, Bash(gh:*), Bash(git:*), Bash(mkdir:*), Task]
6
+ [Read, Write, Edit, Glob, Grep, Bash(gh:*), Bash(git:*), Bash(mkdir:*), Bash(droid:*), Task]
7
7
  ---
8
8
 
9
9
  # Tech Design Skill
@@ -68,6 +68,13 @@ Tech-design has no configuration of its own. It delegates to:
68
68
  - Iterates with `@droid`/`@user` comments (the @mention is the **target**: `@droid` = user asking AI, `@user` = AI asking user)
69
69
  - Captures the "why" behind choices
70
70
 
71
+ **Comment conventions for async back-and-forth:**
72
+
73
+ | Comment | Author | Target | Meaning |
74
+ | -------------- | ------ | ------ | -------------------------- |
75
+ | `> @droid ...` | User | AI | User asking/telling the AI |
76
+ | `> @user ...` | AI | User | AI asking/telling the user |
77
+
71
78
  3. **Roll-up** = Reviewer artifact
72
79
  - Synthesized from thought doc
73
80
  - Decision-focused, no exploration noise
@@ -79,16 +86,13 @@ Both thought doc and roll-up are published to codex. Research doc stays in brain
79
86
 
80
87
  ## Commands
81
88
 
82
- | Command | Action | Status |
83
- | ------------------------------------------- | -------------------------------------------------------- | ------ |
84
- | `/tech-design start --from codex:{project}` | Create research + thought docs, pull PRD/DESIGN context | v1 |
85
- | `/tech-design draft [section]` | Auto-generate from research doc + codebase exploration | v1 |
86
- | `/tech-design think [topic]` | Guided exploration, updates research doc with findings | v1 |
87
- | `/tech-design gaps` | Checklist of missing/empty sections | v1 |
88
- | `/tech-design publish` | Generate roll-up, publish thought doc + roll-up to codex | v1 |
89
- | `/tech-design critic [persona]` | Multi-persona review with severity scoring | v2 |
90
- | `/tech-design respond {question}` | Author tool: search thought doc to draft reply | v2 |
91
- | `/tech-design ask {question}` | Reviewer tool: search both docs to answer questions | v2 |
89
+ | Command | Action |
90
+ | ------------------------------------------- | -------------------------------------------------------- |
91
+ | `/tech-design start --from codex:{project}` | Create research + thought docs, pull PRD/DESIGN context |
92
+ | `/tech-design draft [section]` | Auto-generate from research doc + codebase exploration |
93
+ | `/tech-design think [topic]` | Guided exploration, updates research doc with findings |
94
+ | `/tech-design gaps` | Checklist of missing/empty sections |
95
+ | `/tech-design publish` | Generate roll-up, publish thought doc + roll-up to codex |
92
96
 
93
97
  ## Conversational Skill Matching
94
98
 
@@ -231,12 +231,13 @@ After approval:
231
231
  - [ ] Add key decisions to DECISIONS.md
232
232
  - [ ] Begin implementation"
233
233
 
234
- # Use codex skill's git-finish-write script
234
+ # Use codex skill's git-finish-write script with needs-review label
235
235
  droid config --get tools.codex | droid exec droid-codex git-finish-write \
236
236
  --config - \
237
237
  --message "$commit_msg" \
238
238
  --pr-title "$pr_title" \
239
- --pr-body "$pr_body"
239
+ --pr-body "$pr_body" \
240
+ --labels "needs-review"
240
241
  ```
241
242
 
242
243
  ### 8. Output Success