opencode-beads 0.4.0 → 0.5.0

package/README.md

@@ -26,7 +26,7 @@ Optionally, pin to a specific version for stability:
 
 ```json
 {
-  "plugin": ["opencode-beads@0.4.0"]
+  "plugin": ["opencode-beads@0.5.0"]
 }
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-beads",
-  "version": "0.4.0",
+  "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/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/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/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)