opencode-beads 0.3.2 → 0.5.0

package/README.md

@@ -16,13 +16,21 @@ Add to your OpenCode config (`~/.config/opencode/opencode.json`):
 
 ```json
 {
-  "plugin": ["opencode-beads@0.3.2"]
+  "plugin": ["opencode-beads"]
 }
 ```
 
 Restart OpenCode and you're ready to go.
 
-Pin to a specific version to ensure updates work correctly - OpenCode's lockfile won't re-resolve unpinned versions. To upgrade, change the version and restart.
+Optionally, pin to a specific version for stability:
+
+```json
+{
+  "plugin": ["opencode-beads@0.5.0"]
+}
+```
+
+OpenCode fetches unpinned plugins from npm on each startup; pinned versions are cached and require a manual version bump to update.
 
 ## Features
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-beads",
-  "version": "0.3.2",
+  "version": "0.5.0",
   "type": "module",
   "description": "A plugin for OpenCode that provides integration with the beads issue tracker.",
   "author": "Josh Thomas <josh@joshthomas.dev>",

package/src/vendor.ts

@@ -86,9 +86,12 @@ async function listVendorFiles(relativePath: string): Promise<string[]> {
 
 const BEADS_CLI_USAGE = `## CLI Usage
 
-**Note:** Beads MCP tools are not available in this environment. Use the \`bd\` CLI via bash instead. MCP tool names map directly to \`bd\` commands.
+**IMPORTANT:** There is no \`bd\` tool in this environment. You must use the \`bash\` tool to run the \`bd\` command.
 
-Use the \`bd\` CLI via bash for beads operations:
+**Do not try to call a tool named \`bd\` directly.** It does not exist.
+**Do not try to call MCP tools (like \`ready\`, \`create\`) directly.** They do not exist.
+
+Instead, use the \`bash\` tool for all beads operations:
 
 - \`bd init [prefix]\` - Initialize beads
 - \`bd ready --json\` - List ready tasks
@@ -180,7 +183,7 @@ export async function loadCommands(): Promise<Config["command"]> {
     const parsed = parseMarkdownWithFrontmatter(content);
     if (!parsed) continue;
 
-    const name = `bd-${file.replace(".md", "")}`;
+    const name = `beads:${file.replace(".md", "")}`;
 
     const argHint = parsed.frontmatter["argument-hint"];
     const baseDescription = parsed.frontmatter.description ?? name;

package/vendor/commands/create.md

@@ -5,7 +5,7 @@ argument-hint: [title] [type] [priority]
 
 Create a new beads issue. If arguments are provided:
 - $1: Issue title
-- $2: Issue type (bug, feature, task, epic, chore)
+- $2: Issue type (bug, feature, task, epic, chore, decision)
 - $3: Priority (0-4, where 0=critical, 4=backlog)
 
 If arguments are missing, ask the user for:

package/vendor/commands/daemon.md

@@ -1,6 +1,6 @@
 ---
 description: Manage background sync daemon
-argument-hint: [--start] [--stop] [--status] [--health]
+argument-hint: [start] [stop] [status]
 ---
 
 Manage the per-project background daemon that handles database connections and syncs with git.
@@ -39,10 +39,10 @@ Each project runs its own daemon at `.beads/bd.sock` for complete database isola
 
 ## Common Operations
 
-- **Start**: `bd daemon --start` (or auto-starts on first `bd` command)
-- **Stop**: `bd daemon --stop`
-- **Status**: `bd daemon --status`
-- **Health**: `bd daemon --health` - shows uptime, cache stats, performance metrics
+- **Start**: `bd daemon start` (or auto-starts on first `bd` command)
+- **Stop**: `bd daemon stop`
+- **Status**: `bd daemon status`
+- **Health**: `bd daemon status --all` - shows uptime, cache stats, performance metrics
 - **Metrics**: `bd daemon --metrics` - detailed operational telemetry
 
 ## Sync Options

package/vendor/commands/decision.md

@@ -0,0 +1,111 @@
+---
+description: Record, list, and manage project decisions with rationale tracking
+argument-hint: record|list|show|supersede
+---
+
+Record and track project decisions as beads issues with structured rationale, alternatives considered, and links to affected work.
+
+Decisions use `--type decision`. The description field holds the structured decision record.
+
+## Record a Decision
+
+When the user wants to record a decision (or you invoke `bd decision record`):
+
+1. Gather the following (ask if not provided):
+   - **Title**: Short summary of what was decided (required)
+   - **Rationale**: Why this was chosen (required)
+   - **Alternatives**: What else was considered (optional but encouraged)
+   - **Affects**: Issue IDs this decision impacts (optional)
+   - **Priority**: How important (default P2)
+
+2. Create the issue with structured description:
+
+```bash
+bd create "<title>" --type decision \
+  --description "$(cat <<'EOF'
+## Decision
+
+<one-sentence summary of what was decided>
+
+## Rationale
+
+<why this was chosen>
+
+## Alternatives Considered
+
+- **<alt 1>**: <why rejected>
+- **<alt 2>**: <why rejected>
+
+## Affects
+
+- <issue IDs or area descriptions>
+EOF
+)"
+```
+
+3. If `--affects` issue IDs were provided, link them:
+```bash
+bd dep add <decision-id> <affected-id> --type related
+```
+
+4. Show the created decision to the user.
+
+## List Decisions
+
+```bash
+bd list --type decision
+```
+
+To see all decisions including closed/superseded:
+```bash
+bd list --type decision --all
+```
+
+## Show a Decision
+
+```bash
+bd show <decision-id>
+```
+
+Include comments for discussion history:
+```bash
+bd comments <decision-id>
+```
+
+## Supersede a Decision
+
+When a decision is replaced by a new one:
+
+1. Record the new decision (as above)
+2. Link the new decision to the old one:
+   ```bash
+   bd dep add <new-id> <old-id> --type related
+   ```
+3. Add a comment on the old decision:
+   ```bash
+   bd comments add <old-id> "Superseded by <new-id>: <brief reason>"
+   ```
+4. Close the old decision:
+   ```bash
+   bd close <old-id> --reason "Superseded by <new-id>"
+   ```
+
+## Add Context to an Existing Decision
+
+Use comments to append discussion, implementation notes, or revisit rationale:
+```bash
+bd comments add <decision-id> "Implementation note: ..."
+```
+
+## Search Decisions
+
+```bash
+bd search "keyword" --type decision
+```
+
+## Conventions
+
+- **Status**: `open` = active decision, `closed` = superseded or reversed
+- **Description format**: Use the structured template above for consistency
+- **Linking**: Use `related` dependency type to connect decisions to affected issues
+- **Labels**: Use labels for categorizing decisions (e.g., `architecture`, `tooling`, `process`)

package/vendor/commands/init.md

@@ -12,7 +12,7 @@ Use the beads MCP `init` tool with the prefix parameter (if provided) to set up
 After initialization:
 1. Show the database location
 2. Show the issue prefix that will be used
-3. Explain the basic workflow (or suggest running `/bd-workflow`)
-4. Suggest creating the first issue with `/bd-create`
+3. Explain the basic workflow (or suggest running `/beads:workflow`)
+4. Suggest creating the first issue with `/beads:create`
 
 If beads is already initialized, inform the user and show project stats using the `stats` tool.

package/vendor/commands/list.md

@@ -9,7 +9,7 @@ List beads issues with optional filtering.
 
 - **--status, -s**: Filter by status (open, in_progress, blocked, closed)
 - **--priority, -p**: Filter by priority (0-4: 0=critical, 1=high, 2=medium, 3=low, 4=backlog)
-- **--type, -t**: Filter by type (bug, feature, task, epic, chore)
+- **--type, -t**: Filter by type (bug, feature, task, epic, chore, decision)
 - **--assignee, -a**: Filter by assignee
 - **--label, -l**: Filter by labels (comma-separated, must have ALL labels)
 - **--label-any**: Filter by labels (OR semantics, must have AT LEAST ONE)

package/vendor/commands/search.md

@@ -29,7 +29,7 @@ Unlike `bd list`, which requires you to specify which field to search, `bd searc
 
 - **--status, -s**: Filter by status (open, in_progress, blocked, closed)
 - **--assignee, -a**: Filter by assignee
-- **--type, -t**: Filter by type (bug, feature, task, epic, chore)
+- **--type, -t**: Filter by type (bug, feature, task, epic, chore, decision)
 - **--label, -l**: Filter by labels (must have ALL specified labels)
 - **--label-any**: Filter by labels (must have AT LEAST ONE)
 - **--limit, -n**: Limit number of results (default: 50)

package/vendor/commands/stats.md

@@ -12,6 +12,6 @@ Use the beads MCP `stats` tool to retrieve project metrics and present them clea
 - Recently updated issues
 
 Optionally suggest actions based on the stats:
-- High number of blocked issues? Run `/bd-blocked` to investigate
-- No in_progress work? Run `/bd-ready` to find tasks
-- Many open issues? Consider prioritizing with `/bd-update`
+- High number of blocked issues? Run `/beads:blocked` to investigate
+- No in_progress work? Run `/beads:ready` to find tasks
+- Many open issues? Consider prioritizing with `/beads:update`

package/vendor/commands/version.md

@@ -19,7 +19,7 @@ Display:
 - Compatibility status (✓ compatible or ⚠️ update needed)
 
 If versions are mismatched, provide instructions:
-- Update bd CLI: `curl -fsSL https://raw.githubusercontent.com/steveyegge/beads/main/install.sh | bash`
+- Update bd CLI: `curl -fsSL https://raw.githubusercontent.com/steveyegge/beads/main/scripts/install.sh | bash`
 - Update plugin: `/plugin update beads`
 - Restart Claude Code after updating
 

package/vendor/commands/workflow.md

@@ -9,11 +9,11 @@ Display the beads workflow for AI agents and developers.
 Beads is an issue tracker designed for AI-supervised coding workflows. Here's how to use it effectively:
 
 ## 1. Find Ready Work
-Use `/bd-ready` or the `ready` MCP tool to see tasks with no blockers.
+Use `/beads:ready` or the `ready` MCP tool to see tasks with no blockers.
 
 ## 2. Claim Your Task
 Update the issue status to `in_progress`:
-- Via command: `/bd-update <id> in_progress`
+- Via command: `/beads:update <id> in_progress`
 - Via MCP tool: `update` with `status: "in_progress"`
 
 ## 3. Work on It
@@ -21,18 +21,18 @@ Implement, test, and document the feature or fix.
 
 ## 4. Discover New Work
 As you work, you'll often find bugs, TODOs, or related work:
-- Create issues: `/bd-create` or `create` MCP tool
+- Create issues: `/beads:create` or `create` MCP tool
 - Link them: Use `dep` MCP tool with `type: "discovered-from"`
 - This maintains context and work history
 
 ## 5. Complete the Task
 Close the issue when done:
-- Via command: `/bd-close <id> "Completed: <summary>"`
+- Via command: `/beads:close <id> "Completed: <summary>"`
 - Via MCP tool: `close` with reason
 
 ## 6. Check What's Unblocked
 After closing, check if other work became ready:
-- Use `/bd-ready` to see newly unblocked tasks
+- Use `/beads:ready` to see newly unblocked tasks
 - Start the cycle again
 
 ## Tips
@@ -43,12 +43,12 @@ After closing, check if other work became ready:
 - **Git workflow**: After `git pull`, JSONL auto-imports if newer than DB
 
 ## Available Commands
-- `/bd-ready` - Find unblocked work
-- `/bd-create` - Create new issue
-- `/bd-show` - Show issue details
-- `/bd-update` - Update issue
-- `/bd-close` - Close issue
-- `/bd-workflow` - Show this guide (you are here!)
+- `/beads:ready` - Find unblocked work
+- `/beads:create` - Create new issue
+- `/beads:show` - Show issue details
+- `/beads:update` - Update issue
+- `/beads:close` - Close issue
+- `/beads:workflow` - Show this guide (you are here!)
 
 ## MCP Tools Available
 Use these via the beads MCP server: