@orderful/droid 0.35.2 → 0.35.3

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 (39) hide show
  1. package/.claude-plugin/marketplace.json +6 -6
  2. package/CHANGELOG.md +19 -0
  3. package/dist/tools/brain/.claude-plugin/plugin.json +1 -1
  4. package/dist/tools/brain/TOOL.yaml +1 -1
  5. package/dist/tools/brain/skills/brain/references/workflows.md +14 -1
  6. package/dist/tools/coach/.claude-plugin/plugin.json +1 -1
  7. package/dist/tools/coach/TOOL.yaml +1 -1
  8. package/dist/tools/coach/skills/coach/SKILL.md +1 -1
  9. package/dist/tools/codex/.claude-plugin/plugin.json +1 -1
  10. package/dist/tools/codex/TOOL.yaml +1 -1
  11. package/dist/tools/codex/skills/codex/SKILL.md +1 -0
  12. package/dist/tools/comments/.claude-plugin/plugin.json +1 -1
  13. package/dist/tools/comments/TOOL.yaml +1 -1
  14. package/dist/tools/comments/skills/comments/SKILL.md +1 -1
  15. package/dist/tools/project/.claude-plugin/plugin.json +1 -1
  16. package/dist/tools/project/TOOL.yaml +1 -1
  17. package/dist/tools/project/skills/project/SKILL.md +1 -1
  18. package/dist/tools/tech-design/.claude-plugin/plugin.json +1 -1
  19. package/dist/tools/tech-design/TOOL.yaml +1 -1
  20. package/dist/tools/tech-design/skills/tech-design/SKILL.md +1 -1
  21. package/package.json +1 -1
  22. package/src/tools/brain/.claude-plugin/plugin.json +1 -1
  23. package/src/tools/brain/TOOL.yaml +1 -1
  24. package/src/tools/brain/skills/brain/references/workflows.md +14 -1
  25. package/src/tools/coach/.claude-plugin/plugin.json +1 -1
  26. package/src/tools/coach/TOOL.yaml +1 -1
  27. package/src/tools/coach/skills/coach/SKILL.md +1 -1
  28. package/src/tools/codex/.claude-plugin/plugin.json +1 -1
  29. package/src/tools/codex/TOOL.yaml +1 -1
  30. package/src/tools/codex/skills/codex/SKILL.md +1 -0
  31. package/src/tools/comments/.claude-plugin/plugin.json +1 -1
  32. package/src/tools/comments/TOOL.yaml +1 -1
  33. package/src/tools/comments/skills/comments/SKILL.md +1 -1
  34. package/src/tools/project/.claude-plugin/plugin.json +1 -1
  35. package/src/tools/project/TOOL.yaml +1 -1
  36. package/src/tools/project/skills/project/SKILL.md +1 -1
  37. package/src/tools/tech-design/.claude-plugin/plugin.json +1 -1
  38. package/src/tools/tech-design/TOOL.yaml +1 -1
  39. package/src/tools/tech-design/skills/tech-design/SKILL.md +1 -1
@@ -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",
@@ -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,24 @@
1
1
  # @orderful/droid
2
2
 
3
+ ## 0.35.3
4
+
5
+ ### Patch Changes
6
+
7
+ - [#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
8
+
9
+ 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.
10
+
11
+ - [#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
12
+
13
+ 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.
14
+
15
+ Fixed skills:
16
+ - coach (0.2.4): Added Bash to allowed-tools
17
+ - codex (0.2.2): Added Bash(droid:\*) to allowed-tools
18
+ - comments (0.3.4): Added Bash to allowed-tools
19
+ - tech-design (0.2.4): Added Bash(droid:\*) to allowed-tools
20
+ - project (0.3.4): Added Bash to allowed-tools
21
+
3
22
  ## 0.35.2
4
23
 
5
24
  ### Patch Changes
@@ -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
 
@@ -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-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
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@orderful/droid",
3
- "version": "0.35.2",
3
+ "version": "0.35.3",
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
 
@@ -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-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