@orderful/droid 0.44.0 → 0.45.0

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

@@ -49,10 +49,11 @@ plan → AI scaffolds → human implements → AI coaches → iterate → ship
 
 ## Configuration
 
-| Setting              | Default  | Description                                             |
-| -------------------- | -------- | ------------------------------------------------------- |
-| `scaffold_verbosity` | `medium` | How detailed hints are: `minimal`, `medium`, `detailed` |
-| `override`           | (none)   | User-defined behaviour overrides                        |
+| Setting               | Default    | Description                                                                                       |
+| --------------------- | ---------- | ------------------------------------------------------------------------------------------------- |
+| `scaffold_verbosity`  | `medium`   | How detailed hints are: `minimal`, `medium`, `detailed`                                           |
+| `coaching_intensity`  | `moderate` | How Socratic interactions are: `light` (1-2 questions, concise), `moderate` (2-3 questions), `deep` (thorough Socratic exploration) |
+| `override`            | (none)     | User-defined behaviour overrides                                                                  |
 
 **Overrides:** This skill supports user-defined overrides. See `/droid` skill § Skill Overrides.
 
@@ -62,6 +63,26 @@ plan → AI scaffolds → human implements → AI coaches → iterate → ship
 
 Run `droid config --get tools.coach` to get the merged configuration.
 
+## Custom Instructions
+
+Any command accepts a ` -- {instruction}` suffix. Split on the **first** ` -- ` (space-dash-dash-space): left is the command and its args, right is additional context or instruction to carry through the entire execution.
+
+Example: `/coach plan add auth endpoint -- treat me as a junior learning OAuth for the first time`
+
+---
+
+## Output Discipline
+
+Before each coaching interaction, read `coaching_intensity` from config (`droid config --get tools.coach`):
+
+| Intensity  | Questions per turn | Response length                         |
+| ---------- | ------------------ | --------------------------------------- |
+| `light`    | 1–2 targeted       | Concise — one short paragraph per point |
+| `moderate` | 2–3 focused        | Brief — 3–5 points, context per question (default) |
+| `deep`     | 3+                 | Thorough — current behaviour            |
+
+**Regardless of intensity:** Prefer one sharp, well-framed question over three surface-level ones. Limit each response to 3–5 focused points rather than exhaustive lists. Quality of challenge over quantity of questions.
+
 ---
 
 ## /coach plan
@@ -70,7 +91,10 @@ Run `droid config --get tools.coach` to get the merged configuration.
 
 **Behaviour:**
 
-- Ratio: ~40% proposing, ~60% questioning
+- Proposing/questioning ratio by intensity:
+  - `light` — ~60% proposing, ~40% questioning (lead with concrete guidance)
+  - `moderate` — ~50% proposing, ~50% questioning (default)
+  - `deep` — ~40% proposing, ~60% questioning (current Socratic-heavy behaviour)
 - Ask questions that probe requirements, edge cases, and design tradeoffs
 - Propose structure but let human refine
 - Offer to create a brain doc: "Would you like me to create a brain doc to capture this plan?"
@@ -135,6 +159,7 @@ Run `droid config --get tools.coach` to get the merged configuration.
 - Add inline `// @{user} {question}` comments using the comments skill pattern
 - Questions should probe reasoning, not just confirm choices
 - Focus on: design decisions, edge cases, potential issues, alternatives
+- Question density follows `coaching_intensity`: `light` → 1–2 comments per changed block; `moderate` → 2–3; `deep` → as many as warranted
 
 **Example inline comments:**
 
@@ -179,6 +204,7 @@ Run `droid config --get tools.coach` to get the merged configuration.
 
 - Identify alternative approaches the human might not have considered
 - Use Socratic prompting to guide discovery
+- Question density follows `coaching_intensity`: `light` → 1–2 sharp challenges; `moderate` → 2–3 challenges; `deep` → thorough exploration
 - Ask questions like:
   - "What if I told you there's a potential issue here? Can you find it?"
   - "I can think of another way to implement this. What might it be?"

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

@@ -1,6 +1,6 @@
 {
   "name": "droid-code-review",
-  "version": "0.2.3",
+  "version": "0.2.4",
   "description": "Comprehensive code review using specialized agents. Reviews PRs, staged changes, branches, or specific files with confidence scoring.",
   "author": {
     "name": "Orderful",

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

@@ -1,6 +1,6 @@
 name: code-review
 description: "Comprehensive code review using specialized agents. Reviews PRs, staged changes, branches, or specific files with confidence scoring."
-version: 0.2.3
+version: 0.2.4
 status: alpha
 
 includes:

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

@@ -18,6 +18,12 @@ Code-review has no configuration of its own. Optional integration with other too
 
 **Overrides:** This skill supports user-defined overrides. See `/droid` skill § Skill Overrides.
 
+## Custom Instructions
+
+Any command accepts a ` -- {instruction}` suffix. Split on the **first** ` -- ` (space-dash-dash-space): left is the command and its args, right is additional context or instruction to carry through the entire execution.
+
+Example: `/code-review #123 -- pay close attention to SQL injection risks`
+
 ## How It Works
 
 The `/code-review` command orchestrates multiple specialized agents in parallel:

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

@@ -1,6 +1,6 @@
 {
   "name": "droid-codex",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "Shared organizational knowledge - PRDs, tech designs, domains, proposals, patterns, and explored topics. Self-describing: structure and workflows defined in codex repo. Use when loading project context, searching codex, capturing decisions, or creating new entries.",
   "author": {
     "name": "Orderful",

package/src/tools/codex/TOOL.yaml

@@ -1,6 +1,6 @@
 name: codex
 description: "Shared organizational knowledge - PRDs, tech designs, domains, proposals, patterns, and explored topics. Self-describing: structure and workflows defined in codex repo. Use when loading project context, searching codex, capturing decisions, or creating new entries."
-version: 0.3.0
+version: 0.3.1
 status: beta
 
 includes:

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

@@ -86,6 +86,12 @@ If prerequisites fail, guide user to fix:
 
 **Overrides:** This skill supports user-defined overrides. See `/droid` skill § Skill Overrides.
 
+## Custom Instructions
+
+Any command accepts a ` -- {instruction}` suffix. Split on the **first** ` -- ` (space-dash-dash-space): left is the command and its args, right is additional context or instruction to carry through the entire execution.
+
+Example: `/codex search webhook -- focus on the retry logic patterns`
+
 ## Commands
 
 All codex operations follow workflows defined in the codex repo's `.codex/workflows/` folder.

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

@@ -1,6 +1,6 @@
 {
   "name": "droid-comments",
-  "version": "0.3.5",
+  "version": "0.3.6",
   "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.",
   "author": {
     "name": "Orderful",

package/src/tools/comments/TOOL.yaml

@@ -1,6 +1,6 @@
 name: comments
 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."
-version: 0.3.5
+version: 0.3.6
 status: beta
 
 includes:

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

@@ -63,6 +63,12 @@ Think of it like addressing someone in conversation:
 
 Inline comments shine for localized questions and actions within a file. For longer back-and-forth discussions in documents, they work great too - just be mindful that very long threads may be better moved to dedicated docs.
 
+## Custom Instructions
+
+Any command accepts a ` -- {instruction}` suffix. Split on the **first** ` -- ` (space-dash-dash-space): left is the command and its args, right is additional context or instruction to carry through the entire execution.
+
+Example: `/comments check -- keep responses brief, we're in a tight review cycle`
+
 ## Context Gathering
 
 When you find a `@droid` marker:

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

@@ -1,6 +1,6 @@
 {
   "name": "droid-meeting",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Work with meeting notes, summaries, and transcripts. List recent meetings, search content, generate context-aware summaries, export to codex. Backed by Granola MCP.",
   "author": {
     "name": "Orderful",

package/src/tools/meeting/TOOL.yaml

@@ -1,6 +1,6 @@
 name: meeting
 description: "Work with meeting notes, summaries, and transcripts. List recent meetings, search content, generate context-aware summaries, export to codex. Backed by Granola MCP."
-version: 0.1.1
+version: 0.1.2
 status: beta
 
 includes:

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

@@ -35,6 +35,12 @@ If not configured, tell user:
 
 If connected, proceed.
 
+## Custom Instructions
+
+Any command accepts a ` -- {instruction}` suffix. Split on the **first** ` -- ` (space-dash-dash-space): left is the command and its args, right is additional context or instruction to carry through the entire execution. Note: flag-style `--all` uses `--flag` syntax (no surrounding spaces) and is distinct from this separator.
+
+Example: `/meeting search partner testing review -- extract action items only`
+
 ## Commands
 
 | Command | Action |

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

@@ -1,6 +1,6 @@
 {
   "name": "droid-plan",
-  "version": "0.1.4",
+  "version": "0.1.5",
   "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'.",
   "author": {
     "name": "Orderful",

package/src/tools/plan/TOOL.yaml

@@ -1,6 +1,6 @@
 name: plan
 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'."
-version: 0.1.4
+version: 0.1.5
 status: alpha
 
 includes:

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

@@ -30,6 +30,12 @@ Uses config from dependencies:
 
 **Overrides:** This skill supports user-defined overrides. See `/droid` skill § Skill Overrides.
 
+## Custom Instructions
+
+Any command accepts a ` -- {instruction}` suffix. Split on the **first** ` -- ` (space-dash-dash-space): left is the command and its args, right is additional context or instruction to carry through the entire execution.
+
+Example: `/plan new auth-refactor -- we must stay backward compatible with v1 clients`
+
 ## Commands
 
 | Command                | Action                                              |

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

@@ -1,6 +1,6 @@
 {
   "name": "droid-project",
-  "version": "0.3.4",
+  "version": "0.3.6",
   "description": "Manage project context files for persistent AI memory across sessions. Load, update, or create project context before working on multi-session features.",
   "author": {
     "name": "Orderful",

package/src/tools/project/TOOL.yaml

@@ -1,6 +1,6 @@
 name: project
 description: "Manage project context files for persistent AI memory across sessions. Load, update, or create project context before working on multi-session features."
-version: 0.3.4
+version: 0.3.6
 status: beta
 
 includes:

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

@@ -36,6 +36,12 @@ Chat history disappears. Projects persist.
 
 **Overrides:** This skill supports user-defined overrides. See `/droid` skill § Skill Overrides.
 
+## Custom Instructions
+
+Any command accepts a ` -- {instruction}` suffix. Split on the **first** ` -- ` (space-dash-dash-space): left is the command and its args, right is additional context or instruction to carry through the entire execution.
+
+Example: `/project search droid -- show me what changed last week`
+
 If `projects_dir` is not configured, inform the user they need to set it up:
 ```bash
 mkdir -p ~/.droid/skills/project

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

@@ -32,6 +32,7 @@
    - Confirm which project was loaded
    - Summarize key context (2-3 sentences)
    - Use project contents for all subsequent work in the session
+   - **Do NOT read CHANGELOG.md** — it exists for on-demand lookup only. PROJECT.md already references it; that is enough context.
 
 7. **If `-- {instruction}` provided:** Execute the follow-up instruction against the loaded project
 

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

@@ -1,6 +1,6 @@
 {
   "name": "droid-release",
-  "version": "0.1.0",
+  "version": "0.2.2",
   "description": "Release ceremony automation — create release PRs, check status, notify Slack.",
   "author": {
     "name": "Orderful",

package/src/tools/release/TOOL.yaml

@@ -1,6 +1,6 @@
 name: release
 description: "Release ceremony automation — create release PRs, check status, notify Slack."
-version: 0.1.0
+version: 0.2.2
 status: alpha
 
 includes:
@@ -18,4 +18,4 @@ config_schema:
   slack_channel:
     type: string
     description: "Slack channel for release notifications"
-    default: "#release-management"
+    default: "#release_management"

package/src/tools/release/commands/release.md

@@ -1,7 +1,7 @@
 ---
 name: release
-description: "Release ceremony automation"
-argument-hint: "[start [repo] | status | complete [repo]]"
+description: "Release ceremony automation and branch locking"
+argument-hint: "[start [repo] [--no-lock] | merge [repo] | lock [repo] | unlock [repo] | status | complete [repo]]"
 ---
 
 # /release
@@ -12,17 +12,25 @@ argument-hint: "[start [repo] | status | complete [repo]]"
 
 ## Examples
 
-- `/release start` → Create release PR for current repo
+- `/release start` → Create release PR + auto-lock branch
 - `/release start orderful-workspace` → Create release PR for a specific repo
-- `/release status` → Check CI state across release repos
-- `/release complete` → Post "release complete" to Slack
+- `/release start --no-lock` → Create release PR without locking
+- `/release merge` → Merge release PR (checks must be green)
+- `/release lock` → Manually lock the release branch
+- `/release unlock` → Unlock the release branch
+- `/release status` → Check CI and lock state across release repos
+- `/release complete` → Post "release complete" to Slack, auto-unlock if locked
 
 ## Quick Reference
 
 ```
-/release start [repo]       # Create release PR + notify Slack
-/release status             # CI state across repos
-/release complete [repo]    # Notify Slack, close out release
+/release start [repo]        # Create release PR + auto-lock + notify Slack
+/release start --no-lock    # Create release PR without locking
+/release merge [repo]       # Merge release PR (checks must pass)
+/release lock [repo]        # Manually lock release branch
+/release unlock [repo]      # Unlock release branch
+/release status             # CI + lock state across repos
+/release complete [repo]    # Notify Slack + auto-unlock
 ```
 
 See the **release skill** for complete documentation.

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

@@ -1,20 +1,21 @@
 ---
 name: release
-description: "Release ceremony automation for dev-to-master releases. Use when starting a release, merging a release, checking release status, or completing a release. User prompts like 'start a release', 'merge the release', 'release status', 'release complete'."
-argument-hint: "[start [repo] | merge [repo] | status | complete [repo]]"
+description: "Release ceremony automation for dev-to-master releases. Use when starting a release, merging a release, locking a branch, checking release status, or completing a release. User prompts like 'start a release', 'merge the release', 'lock dev', 'release status', 'unlock the branch'."
+argument-hint: "[start [repo] | merge [repo] | lock [repo] | unlock [repo] | status | complete [repo]]"
 allowed-tools: [Read, Write, Glob, Grep, Bash, Edit]
 ---
 
 # Release Skill
 
-Automate dev → master release ceremonies: create release PRs, notify Slack, and track status.
+Automate dev → master release ceremonies: create release PRs, lock branches during CI, notify Slack, and track status.
 
 ## When to Use
 
 - User wants to start a release (create PR from dev → master)
-- User asks about release status (open PRs, CI checks)
+- User wants to lock or unlock a branch during a release
+- User asks about release status (open PRs, lock state, CI checks)
 - User says "release complete" or wants to close out a release
-- Natural language like "start a release", "what's the release status?"
+- Natural language like "start a release", "lock dev", "what's the release status?"
 
 ## When NOT to Use
 
@@ -26,6 +27,7 @@ Automate dev → master release ceremonies: create release PRs, notify Slack, an
 
 1. **`gh` CLI** — authenticated with access to target repos
 2. **Slack integration** — `droid integrations slack post` configured (optional, falls back to terminal)
+3. **`branch-lock.yml`** — GitHub Action deployed to target repo (required for auto-lock on start + lock/unlock commands)
 
 ## Configuration
 
@@ -37,20 +39,28 @@ droid config --get repos
 ```
 
 - **Repos:** Filter `repos` array for entries with `release_branch` set — these are release repos
-- **Slack channel:** From `tools.release.slack_channel` (default: `#release-management`)
+- **Slack channel:** From `tools.release.slack_channel` (default: `#release_management`)
 - **Repo detection:** Match cwd against repo paths, or ask user if ambiguous
 
 If no repos have `release_branch` set, tell user:
 > "No release repos configured. Run `droid repos add` and set a release branch to get started."
 
+## Custom Instructions
+
+Any command accepts a ` -- {instruction}` suffix. Split on the **first** ` -- ` (space-dash-dash-space): left is the command and its args, right is additional context or instruction to carry through the entire execution. Note: flag-style `--no-lock` uses `--flag` syntax (no surrounding spaces) and is distinct from this separator.
+
+Example: `/release start -- notify #releases-eng channel instead of the default`
+
 ## Commands
 
 | Command | Action |
 |---------|--------|
-| `/release start [repo]` | Create release PR + notify Slack |
+| `/release start [repo] [--no-lock]` | Create release PR + auto-lock branch + notify Slack |
 | `/release merge [repo]` | Merge release PR (only if checks pass) + notify Slack |
-| `/release status` | Check open release PRs + CI state |
-| `/release complete [repo]` | Post completion to Slack |
+| `/release lock [repo]` | Lock release branch (confirms first) |
+| `/release unlock [repo]` | Unlock release branch |
+| `/release status` | Check open release PRs + CI state + lock state |
+| `/release complete [repo]` | Post completion to Slack + auto-unlock |
 
 See `references/workflows.md` for detailed step-by-step procedures and exact `gh` commands.
 
@@ -69,6 +79,9 @@ See `references/templates.md` for Slack message and PR body templates.
 |-------|--------|
 | No release repos configured | Suggest `droid repos add` with release branch |
 | `gh` CLI not authenticated | Suggest `gh auth login` |
+| `branch-lock.yml` not found in repo | Tell user to add the `branch-lock.yml` workflow to the repo |
 | Slack not configured | Print message to terminal, suggest `droid integrations setup slack` |
+| Branch already locked | Warn user, offer to unlock first |
 | Release PR already exists | Show existing PR, ask if user wants to proceed |
 | CI checks failing | Show status, do not auto-merge |
+| High-risk label present at merge | Show extra confirmation prompt before standard merge confirmation; do not auto-skip |

package/src/tools/release/skills/release/references/templates.md

@@ -6,20 +6,30 @@ Slack mrkdwn and PR body templates for release notifications.
 
 All Slack messages are posted via `droid integrations slack post`. Format as Slack mrkdwn (not GitHub markdown).
 
-### Release Started
+### Release Open for Review
 
 ```
-:rocket: *Release started — {repo_name}*
+:rocket: *Release open for review — {repo_name}*
 
 *Risk:* {risk_emoji} {risk_level}
 *PR:* <{pr_url}|#{pr_number}>
 *Branch:* `{release_branch}` → `{production_branch}`
+:lock: `{release_branch}` is locked — no merges until release completes
 
 {pr_summary}
 
 Posted with :droid:
 ```
 
+If `--no-lock` was used, omit the lock line.
+
+If `HIGH_RISK_PRS` is non-empty, append the following block after `{pr_summary}` (before `Posted with :droid:`):
+```
+⚠️ *High-risk PRs:*
+- <{pr_url}|#{number}> {title} (@{author})
+```
+(one line per high-risk PR)
+
 Risk emojis:
 - Low Risk: `:large_green_circle:`
 - High Risk: `:warning:`
@@ -37,6 +47,26 @@ Monitoring deployment :eyes:
 Posted with :droid:
 ```
 
+### Branch Locked
+
+```
+:lock: *Branch locked — {repo_name}*
+
+`{branch}` is now read-only. No merges until unlocked.
+
+Posted with :droid:
+```
+
+### Branch Unlocked
+
+```
+:unlock: *Branch unlocked — {repo_name}*
+
+`{branch}` is open for merges.
+
+Posted with :droid:
+```
+
 ### Release Complete
 
 ```
@@ -48,6 +78,11 @@ Posted with :droid:
 Posted with :droid:
 ```
 
+If auto-unlocked, append:
+```
+:unlock: Auto-unlocked `{release_branch}`
+```
+
 ---
 
 ## Release PR Body
@@ -75,18 +110,36 @@ Where `{pr_list}` is a bulleted list of merged PRs:
 - #{number} {title} (@{author})
 ```
 
+If `HIGH_RISK_PRS` is non-empty, insert the following section between `{pr_list}` and the `---` divider:
+```markdown
+### ⚠️ High-Risk PRs
+
+The following PRs in this release are labelled `high-risk`. Coordinate with the authors before deploying.
+
+- #{number} {title} (@{author})
+```
+(one line per high-risk PR)
+
 ---
 
 ## Terminal Fallback
 
 When Slack is not configured, print a plain-text version to terminal:
 
-### Release Started (terminal)
+### Release Open for Review (terminal)
 ```
-Release started — {repo_name}
+Release open for review — {repo_name}
   Risk: {risk_level}
   PR:   {pr_url}
   Branch: {release_branch} -> {production_branch}
+  Lock: {release_branch} locked (no merges until release completes)
+```
+
+If `--no-lock` was used, omit the Lock line.
+
+If `HIGH_RISK_PRS` is non-empty, append:
+```
+  ⚠️  High-risk PRs: #{number} {title} (@{author}), ...
 ```
 
 ### Release Merged (terminal)
@@ -97,6 +150,18 @@ Release merged — {repo_name}
   Monitoring deployment...
 ```
 
+### Branch Locked (terminal)
+```
+Branch locked — {repo_name}
+  {branch} is now read-only
+```
+
+### Branch Unlocked (terminal)
+```
+Branch unlocked — {repo_name}
+  {branch} is open for merges
+```
+
 ### Release Complete (terminal)
 ```
 Release complete — {repo_name}