opencode-beads 0.5.1 → 0.5.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.
- package/README.md +7 -1
- package/package.json +1 -1
- package/src/vendor.ts +0 -1
- package/vendor/agents/task-agent.md +1 -1
- package/vendor/commands/update.md +1 -1
- package/vendor/commands/workflow.md +2 -2
package/README.md
CHANGED
|
@@ -2,6 +2,12 @@
|
|
|
2
2
|
|
|
3
3
|
[Beads](https://github.com/steveyegge/beads) issue tracker integration for [OpenCode](https://opencode.ai).
|
|
4
4
|
|
|
5
|
+
> [!NOTE]
|
|
6
|
+
> This plugin is intentionally small in scope. The [beads](https://github.com/steveyegge/beads) project is moving quickly and is a moving target — any additional layers on top of it add churn.
|
|
7
|
+
>
|
|
8
|
+
> To minimize maintenance, this plugin defers to beads and limits its scope to bug fixes and syncing upstream vendor plugin content. Feature requests and additional customization are generally out of scope.
|
|
9
|
+
>
|
|
10
|
+
> If you want to customize behavior, the plugin surface area is small — forking or copying it locally is encouraged.
|
|
5
11
|
## Installation
|
|
6
12
|
|
|
7
13
|
Install the beads CLI:
|
|
@@ -26,7 +32,7 @@ Optionally, pin to a specific version for stability:
|
|
|
26
32
|
|
|
27
33
|
```json
|
|
28
34
|
{
|
|
29
|
-
"plugin": ["opencode-beads@0.5.
|
|
35
|
+
"plugin": ["opencode-beads@0.5.3"]
|
|
30
36
|
}
|
|
31
37
|
```
|
|
32
38
|
|
package/package.json
CHANGED
package/src/vendor.ts
CHANGED
|
@@ -104,7 +104,6 @@ Instead, use the \`bash\` tool for all beads operations:
|
|
|
104
104
|
- \`bd list --status open --json\` - List issues
|
|
105
105
|
- \`bd blocked --json\` - Show blocked issues
|
|
106
106
|
- \`bd stats --json\` - Show statistics
|
|
107
|
-
- \`bd sync\` - Sync with git
|
|
108
107
|
|
|
109
108
|
If a tool is not listed above, try \`bd <tool> --help\`.
|
|
110
109
|
|
|
@@ -39,7 +39,7 @@ You are a task-completion agent for beads. Your goal is to find ready work and c
|
|
|
39
39
|
|
|
40
40
|
# Important Guidelines
|
|
41
41
|
|
|
42
|
-
- Always
|
|
42
|
+
- Always claim before working (MCP: set status to `in_progress`; CLI: `--claim` for atomic assignee + status) and close when done
|
|
43
43
|
- Link discovered work with `discovered-from` dependencies
|
|
44
44
|
- Don't close issues unless work is actually complete
|
|
45
45
|
- If blocked, use `update` to set status to `blocked` and explain why
|
|
@@ -19,6 +19,6 @@ Use the beads MCP `update` tool to apply the changes. Show the updated issue to
|
|
|
19
19
|
**Note:** Comments are managed separately with `bd comments add`. The `update` command is for singular, versioned properties (title, status, priority, etc.), while comments form a discussion thread that's appended to, not updated.
|
|
20
20
|
|
|
21
21
|
Common workflows:
|
|
22
|
-
- Start work:
|
|
22
|
+
- Start work: `bd update <id> --claim` (atomic claim + `in_progress`)
|
|
23
23
|
- Mark blocked: Update status to `blocked`
|
|
24
24
|
- Reprioritize: Update priority (0-4)
|
|
@@ -12,8 +12,8 @@ Beads is an issue tracker designed for AI-supervised coding workflows. Here's ho
|
|
|
12
12
|
Use `/beads:ready` or the `ready` MCP tool to see tasks with no blockers.
|
|
13
13
|
|
|
14
14
|
## 2. Claim Your Task
|
|
15
|
-
|
|
16
|
-
- Via command: `/beads:update <id>
|
|
15
|
+
Claim the issue atomically (assignee + `in_progress` in one step):
|
|
16
|
+
- Via command: `/beads:update <id> --claim`
|
|
17
17
|
- Via MCP tool: `update` with `status: "in_progress"`
|
|
18
18
|
|
|
19
19
|
## 3. Work on It
|