clikit-plugin 0.3.11 → 0.3.13

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/AGENTS.md CHANGED
@@ -77,7 +77,6 @@ Load `session-management` skill for full threshold handling (including handoff t
77
77
  bun install # dependencies
78
78
  bun run build # compile plugin
79
79
  bun run typecheck # type check
80
- bun run test # unit tests
81
80
  bun run verify # full local verification
82
81
  bun run dev # watch mode
83
82
  ```
@@ -108,23 +107,21 @@ tilth CLI → read → grep → glob
108
107
 
109
108
  This is a documented agent rule, not a hard runtime block.
110
109
 
111
- ## Issue Tracking with bd (beads)
110
+ ## Issue Tracking with Beads Rust (`br`)
112
111
 
113
- **IMPORTANT**: This project uses **bd (beads)** for ALL issue tracking. Do NOT use markdown TODOs, task lists, or other tracking methods.
112
+ **IMPORTANT**: This project now prefers **Beads Rust** (`br`) with local `.beads/` storage for persistent task tracking. Do NOT use markdown TODOs or ad-hoc task lists as the source of truth.
114
113
 
115
- ### Two Interfaces
114
+ ### Preferred Interface
116
115
 
117
116
  | Interface | Who Uses It | How |
118
117
  |-----------|-------------|-----|
119
- | **`bd` CLI** | User in terminal | `bd create`, `bd ready`, `bd close` |
120
- | **`beads-village_*` MCP** | AI agents in OpenCode | `beads-village_add`, `beads-village_claim` |
121
-
122
- **AI agents must use `beads-village_*` MCP tools — never shell `bd` commands.**
118
+ | **`br` CLI** | User and agents | `br init`, `br ready --json`, `br create`, `br update`, `br close`, `br sync` |
119
+ | **`beads-village_*` MCP** | Optional legacy compatibility | Use only if already installed and explicitly needed for reservations/messages |
123
120
 
124
121
  ### Agent Core Cycle
125
122
 
126
123
  ```
127
- beads-village_initstatus/inbox → ls(ready) → show → add (if needed) → claim reservations reserve → work → verify → done → sync
124
+ br init br ready --json br show/list --json br create (if needed) → br update --status in_progress --claim → work → verify → br close br sync --flush-only
128
125
  ```
129
126
 
130
127
  In compressed workflow, the execution unit is a **Task Packet**:
@@ -137,36 +134,32 @@ In compressed workflow, the execution unit is a **Task Packet**:
137
134
 
138
135
  | Tool | Purpose |
139
136
  |------|---------|
140
- | `beads-village_init` | Join workspace call FIRST every session |
141
- | `beads-village_add(title, typ, pri, tags, deps)` | Create issue |
142
- | `beads-village_claim` | Claim next ready task (filtered by role) |
143
- | `beads-village_reserve(paths, reason)` | Lock files before editing |
144
- | `beads-village_done(id, msg)` | Complete task, auto-release locks |
145
- | `beads-village_ls(status="ready")` | List claimable tasks |
146
- | `beads-village_show(id)` | Get task details |
147
- | `beads-village_status(include_agents=true)` | Workspace overview + agent discovery |
148
- | `beads-village_msg(subj, global=true, to="all")` | Broadcast to team |
149
- | `beads-village_inbox(unread=true)` | Read messages |
150
- | `beads-village_sync` | Push/pull git changes |
151
-
152
- ### v1.3 API Changes (avoid old names)
153
-
154
- | Old (broken) | Correct |
155
- |---|---|
156
- | `beads-village_ready` | `beads-village_ls(status="ready")` |
157
- | `beads-village_broadcast` | `beads-village_msg(global=true, to="all")` |
158
- | `beads-village_discover` | `beads-village_status(include_agents=true)` |
137
+ | `br init` | Initialize `.beads/` for the project |
138
+ | `br ready --json` | List unblocked claimable work |
139
+ | `br create --title ... --description ... --type ... --priority ...` | Create issue |
140
+ | `br update <id> --status in_progress --claim` | Claim / start work |
141
+ | `br show <id> --json` | Read task details |
142
+ | `br list --json` | Inspect task inventory |
143
+ | `br close <id> --reason "Completed" --json` | Close completed work |
144
+ | `br sync --flush-only` | Flush `.beads/` state before git commit/push |
145
+ | `br sync --import-only` | Re-import `.beads/` state after pull/rebase |
146
+
147
+ ### Legacy compatibility note
148
+
149
+ - `beads-village_*` is no longer the default required workflow in this repo.
150
+ - If a local setup still depends on `beads-village` for reservations or inbox-style coordination, treat it as optional compatibility, not the primary task tracker.
151
+ - This repo does **not** currently provide a full MCP replacement for `br`; use the CLI-first workflow above.
159
152
 
160
153
  ### Policy
161
154
 
162
155
  - Trivial (< 2 min, 1-line fix): skip Beads, just do it
163
- - Non-trivial: create issue first → claim → work → done
164
- - `todowrite` = in-session UI display only — Beads is the persistent and authoritative execution state
156
+ - Non-trivial: prefer `br` issue first → claim/start → work → close
157
+ - `todowrite` = in-session UI display only — `.beads/` is the persistent execution state when task tracking is in use
165
158
  - Work in the shared checkout on the repo default branch — no git worktrees or per-task branches unless the user explicitly requests them
166
159
  - Check `git status --short --branch` before editing; if overlapping local changes already exist in your scope, stop and coordinate instead of isolating the work
167
- - Use `beads-village_reserve` to surface conflicts early in the shared workspace
168
- - Always `reserve` files before editing in multi-agent contexts
169
- - Call `done` before ending a completed session; for mid-task handoff, leave the issue open and hand off without `done`
160
+ - If optional `beads-village` reservations are available, you may use them to surface conflicts early in the shared workspace
161
+ - Otherwise coordinate through git state, handoffs, and explicit file scope instead of assuming reservations exist
162
+ - Call `br close` before ending a completed tracked session; for mid-task handoff, leave the issue open and hand off without closing it
170
163
 
171
164
  ### Nested Repository Note
172
165
 
package/README.md CHANGED
@@ -1,11 +1,90 @@
1
1
  # CliKit Plugin for OpenCode
2
2
 
3
- Curated agents, commands, skills, and memory system for OpenCode.
3
+ Turn raw OpenCode into a disciplined delivery workflow: **discuss → create → start → verify → ship**.
4
+
5
+ CliKit is the workflow layer for OpenCode — curated agents, slash commands, runtime hooks, memory artifacts, and quality gates that help you move from vague request to verified change without inventing your process every session.
6
+
7
+ _README structure inspired by [GSD / get-shit-done](https://github.com/gsd-build/get-shit-done) and [OpenCodeKit](https://opencodekit.xyz/)._
8
+
9
+ ## Why CliKit exists
10
+
11
+ OpenCode is powerful, but the hard part is not calling a model — it is keeping planning, execution, verification, and handoff aligned as the task gets bigger.
12
+
13
+ CliKit adds that missing structure:
14
+
15
+ - **Workflow orchestration** — opinionated commands for discuss/create/start/verify/ship
16
+ - **Agent library** — specialized roles for build, plan, explore, review, research, oracle, and vision
17
+ - **Memory system** — discussion, plan, research, review, and handoff artifacts that survive across sessions
18
+ - **Safety + quality hooks** — git guard, security checks, truncation, memory digest, and prompt-context helpers
19
+ - **Verification loop** — compressed packet execution plus explicit verification before landing changes
20
+
21
+ ## Start here
22
+
23
+ ### Install in 3 steps
24
+
25
+ ```bash
26
+ # 1) Install Beads Rust for local task tracking
27
+ br --version
28
+
29
+ # 2) Initialize tracker state in your project
30
+ br init
31
+
32
+ # 3) Install CliKit for OpenCode
33
+ bun x clikit-plugin install
34
+ ```
35
+
36
+ Need the full install notes, Windows binary path, or MCP details? Jump to [Installation](#installation).
37
+
38
+ ### Pick a workflow
39
+
40
+ **Quick feature / fix**
41
+ ```text
42
+ /discuss → /create → /start → /verify → /ship
43
+ ```
44
+
45
+ **Deeper feature / research-heavy change**
46
+ ```text
47
+ /discuss → /create → /design → /start → /verify → /ship
48
+ ```
49
+
50
+ **Audit existing work before landing**
51
+ ```text
52
+ /verify → /ship
53
+ ```
54
+
55
+ ## What you get
56
+
57
+ - **7 specialized agents** — build, plan, explore, review, vision, oracle, research
58
+ - **15 slash commands** — including `/discuss`, `/create`, `/start`, `/verify`, `/ship`, `/augment`, `/debug`, `/research`, `/design`, `/status`
59
+ - **26 workflow skills** — planning, debugging, testing, integration, and session-management skills
60
+ - **11 runtime hooks/modules** — git guard, security check, truncator, memory digest, beads context, tilth reading, and more
61
+ - **Structured memory** — templates plus saved discussions, plans, research, reviews, handoffs, and PRDs
62
+ - **Configurable runtime** — per-agent overrides, hook toggles, workflow mode selection, and extended permissions
63
+
64
+ ## Trust & compatibility
65
+
66
+ - **OpenCode-first** plugin architecture
67
+ - **Compressed workflow** with packetized execution and embedded verification
68
+ - **Beads Rust (`br`)** as the preferred local tracker workflow
69
+ - **Shared-workspace friendly** defaults with optional legacy `beads-village` compatibility
70
+ - **Published package**: [`clikit-plugin` on npm](https://www.npmjs.com/package/clikit-plugin)
71
+
72
+ ## Docs map
73
+
74
+ - `README.md` — install, workflows, commands, skills, config
75
+ - `AGENTS.md` — repo-wide execution policy and tracker workflow
76
+ - `command/` — slash command definitions and execution rules
77
+ - `src/agents/` — agent prompts and behavior contracts
78
+ - `skill/` — reusable workflow skills
79
+ - `schemas.md` — canonical packet / artifact / tracker schemas
80
+ - `memory/_templates/` — discussion, plan, research, review, PRD, and handoff templates
81
+
82
+ ---
4
83
 
5
84
  ## Features
6
85
 
7
86
  - **7 Specialized Agents**: build, plan, explore, review, vision, oracle, research
8
- - **14 Slash Commands**: /discuss, /create, /start, /ship, /verify, /debug, /design, /research, /commit, /pr, and more
87
+ - **15 Slash Commands**: /discuss, /create, /start, /ship, /verify, /augment, /debug, /design, /research, /commit, /pr, and more
9
88
  - **26 Workflow Skills**: TDD, debugging, research, integrations, ritual-workflow, and more
10
89
  - **7 Internal Utilities**: memory (read/search/get/timeline/update/admin), observation, context-summary, cass-memory (used by hooks, not directly registered as agent tools)
11
90
  - **11 Runtime Hooks/Modules**: todo enforcer, empty output sanitizer, git guard, security check, subagent blocker, truncator, memory digest, todo→beads sync, beads-context, cass-memory, and tilth-reading
@@ -15,45 +94,33 @@ Curated agents, commands, skills, and memory system for OpenCode.
15
94
 
16
95
  ## Installation
17
96
 
18
- ### Step 1 — Install Beads (required)
19
-
20
- CliKit uses [Beads](https://github.com/steveyegge/beads) (`bd`) for persistent task tracking. Install it system-wide first.
97
+ ### Step 1 — Install Beads Rust (`br`)
21
98
 
22
- **Windows (PowerShell):**
23
- ```pwsh
24
- irm https://raw.githubusercontent.com/steveyegge/beads/main/install.ps1 | iex
25
- ```
26
-
27
- **macOS / Linux — Homebrew (recommended):**
28
- ```bash
29
- brew install beads
30
- ```
99
+ CliKit now prefers [beads_rust](https://github.com/Dicklesworthstone/beads_rust) (`br`) for persistent task tracking in `.beads/`. Classic `bd` + Dolt are no longer required for the default workflow.
31
100
 
32
- **npm / bun:**
33
- ```bash
34
- npm install -g @beads/bd
35
- # or
36
- bun install -g --trust @beads/bd
37
- ```
101
+ **Windows (native binary):**
102
+ 1. Download the latest `br-v*-windows_amd64.zip` asset from the GitHub Releases page.
103
+ 2. Extract `br.exe`.
104
+ 3. Place it on your `PATH` (for example under `%APPDATA%\npm`).
38
105
 
39
- **go install (Go 1.24+ required):**
106
+ **macOS / Linux / Windows via WSL:**
40
107
  ```bash
41
- go install github.com/steveyegge/beads/cmd/bd@latest
108
+ curl -fsSL "https://raw.githubusercontent.com/Dicklesworthstone/beads_rust/main/install.sh" | bash
42
109
  ```
43
110
 
44
111
  Verify:
45
112
  ```bash
46
- bd version
113
+ br --version
47
114
  ```
48
115
 
49
- ### Step 2 — Initialize Beads in your project
116
+ ### Step 2 — Initialize `.beads/` in your project
50
117
 
51
118
  ```bash
52
119
  cd your-project
53
- bd init --quiet
120
+ br init
54
121
  ```
55
122
 
56
- This creates the `.beads/` database directory. Do this once per project.
123
+ This creates the `.beads/` task-tracking directory. Do this once per project. If `.beads/` already exists, keep it and use `br sync --import-only` after pulling or rebasing older state.
57
124
 
58
125
  ### Step 3 — Install CliKit
59
126
 
@@ -68,11 +135,12 @@ The plugin is registered in `~/.config/opencode/opencode.json`.
68
135
 
69
136
  CliKit injects default MCP server entries at runtime when missing:
70
137
 
71
- - `beads-village` (`npx beads-village`) — requires `bd init` to have been run in the project
72
138
  - `context7` (`https://mcp.context7.com/mcp`)
73
139
  - `grep` (`https://mcp.grep.app`)
74
140
  - `human-mcp` (`npx @goonnguyen/human-mcp`)
75
141
 
142
+ `beads-village` is no longer injected by default. If you still rely on the legacy MCP workflow for reservations or inbox-style coordination, add it manually.
143
+
76
144
  Recommended environment variables:
77
145
 
78
146
  - `CONTEXT7_API_KEY` for Context7
@@ -93,15 +161,16 @@ After installation, use these commands:
93
161
  ```
94
162
 
95
163
  Workflow notes:
96
- - All 14 commands work **standalone** the pipeline is recommended, not required
164
+ - All 15 commands work **standalone** - the pipeline is recommended, not required
97
165
  - `/discuss` runs a pre-create discussion phase — clarify intent, confirm assumptions, and save a planning-ready discussion artifact
98
166
  - `/create` explores codebase first, consumes discussion context, runs a mandatory pre-plan research pass, then produces a single XML-structured plan
99
167
  - `/start` executes the plan, one Task Packet at a time — creates a minimal inline plan if none exists
100
168
  - `/verify` runs all 4 gates (typecheck, tests, lint, build) + deep review — use anytime, not just pre-ship
101
169
  - `/ship` finalizes work in the shared checkout — commit, sync, and land on the repo default branch; `/pr` is optional and only for explicit PR-based exceptions
170
+ - `/augment <draft>` rewrites a prompt into a stronger, intent-aware version, attempts an OpenCode-native LLM refinement pass, and auto-inserts the rewritten prompt into the editor when TUI controls are available; it falls back to the deterministic rewrite and manual copy/send workflow when refinement or prompt injection is unavailable
102
171
  - `/research` is an optional standalone research command — it reads discussion context first, closes decision gaps with external evidence, and saves a planning-ready report
103
172
  - `/design` implements UI/UX with variant exploration and a11y — uses Vision agent
104
- - Beads is the live execution source of truth
173
+ - `br` + `.beads/` is the preferred persistent task source of truth; `beads-village` is optional legacy compatibility only
105
174
  - Plans decompose work into **Task Packets** (1 concern, 1–3 files, one verify bundle)
106
175
 
107
176
  ## Configuration
@@ -192,8 +261,8 @@ Project config overrides user config.
192
261
  | `subagent_question_blocker` | on | Prevents subagents from asking clarifying questions |
193
262
  | `truncator` | on | Truncates large outputs to prevent context overflow |
194
263
  | `memory_digest` | on | Generates `memory/_digest.md` index + topic files (`decision.md`, `learning.md`, etc.) from SQLite observations |
195
- | `todo_beads_sync` | off | Legacy todo→Beads mirror; disabled in compressed workflow |
196
- | `beads_context` | on | Injects active Beads task state into prompts |
264
+ | `todo_beads_sync` | off | Legacy compatibility mirror for syncing todos into `.beads/` exports |
265
+ | `beads_context` | on | Injects active `.beads/` task state into prompts when local Beads data exists |
197
266
  | `cass_memory` | on | Loads embedded memory context on session start and runs idle reflection (`cassMemoryContext`, `cassMemoryReflect`) |
198
267
  | `tilth_reading` | on | Enhances `read` tool output via tilth when available for smarter file reads |
199
268
 
@@ -213,7 +282,7 @@ Default active roles in compressed workflow: `build`, `plan`, `review`, plus coo
213
282
 
214
283
  ## Commands
215
284
 
216
- Run with `/command-name` in OpenCode. **All 14 commands work standalone** — the pipeline is a recommended flow, not a requirement.
285
+ Run with `/command-name` in OpenCode. **All 15 commands work standalone** — the pipeline is a recommended flow, not a requirement.
217
286
 
218
287
  ### Workflow pipeline
219
288
  | Command | Standalone? | One-liner |
@@ -229,8 +298,9 @@ Run with `/command-name` in OpenCode. **All 14 commands work standalone** — th
229
298
  ### Utilities (all standalone)
230
299
  | Command | One-liner |
231
300
  |---------|-----------|
301
+ | `/augment` | Rewrite a draft prompt into a stronger, intent-aware prompt with LLM refinement when available; supported runtimes auto-insert it into the draft editor, with manual review/copy/send as fallback |
232
302
  | `/debug` | Reproduce → 5-Whys root cause → fix → regression test |
233
- | `/status` | Workspace snapshot — Beads tasks, git state, active artifacts |
303
+ | `/status` | Workspace snapshot — task tracker state, git state, active artifacts |
234
304
  | `/init` | Bootstrap CliKit — scaffold dirs + write tailored AGENTS.md |
235
305
  | `/handoff` | Auto-capture session state for graceful pause |
236
306
  | `/resume` | Pick up cold from latest handoff, no warm-up questions |
@@ -278,7 +348,7 @@ Run with `/command-name` in OpenCode. **All 14 commands work standalone** — th
278
348
  ### Integration & Collaboration (6)
279
349
  | Skill | Use When |
280
350
  |-------|----------|
281
- | `beads` | Multi-agent task coordination via beads-village |
351
+ | `beads` | Multi-agent task coordination with `br` and optional legacy beads-village helpers |
282
352
  | `playwright` | Browser automation and E2E testing |
283
353
  | `chrome-devtools` | Web debugging and performance analysis |
284
354
  | `requesting-code-review` | After completing a task |
@@ -297,9 +367,6 @@ bun run build
297
367
  # Type check
298
368
  bun run typecheck
299
369
 
300
- # Unit tests
301
- bun run test
302
-
303
370
  # Full local verification
304
371
  bun run verify
305
372
 
@@ -328,7 +395,7 @@ bun run dev
328
395
  │ ├── research/ # Research artifacts
329
396
  │ ├── reviews/ # Code reviews
330
397
  │ ├── handoffs/ # Session handoffs
331
- │ ├── beads/ # Beads task artifacts
398
+ │ ├── beads/ # Optional compatibility bead metadata
332
399
  │ └── prds/ # Product requirements
333
400
  └── clikit.jsonc
334
401
  ```
@@ -0,0 +1,34 @@
1
+ ---
2
+ description: Rewrite a draft prompt into a stronger, intent-aware prompt and auto-insert it when TUI controls are available.
3
+ agent: build
4
+ ---
5
+
6
+ You are rewriting the user's draft prompt into a stronger, intent-aware version.
7
+
8
+ ## Your Task
9
+
10
+ Use the `augment_prompt` tool with:
11
+ - `draft`: `$ARGUMENTS`
12
+ - `mode`: `auto`
13
+
14
+ If `$ARGUMENTS` is empty, do not guess. Return exactly:
15
+
16
+ ```text
17
+ Usage: /augment <draft prompt>
18
+ ```
19
+
20
+ ## Output Format
21
+
22
+ 1. `Intent: <intent> | Mode: <mode> | Intensity: <intensity>`
23
+ 2. A fenced code block containing only the rewritten prompt from `enhanced`
24
+ 3. If `enhancementSource` is `llm`, add: `Enhancement source: llm`
25
+ 4. If `fallbackReason` is present, add: `Fallback: <fallbackReason>`
26
+ 5. If the editor draft was not updated automatically, add exactly: `Review, copy, and send it manually.`
27
+
28
+ ## Rules
29
+
30
+ - Do not answer the draft prompt itself
31
+ - Do not execute the requested work
32
+ - Do not add commentary beyond the required output format
33
+ - Prefer the tool result as the source of truth for whether fallback happened
34
+ - Assume supported runtimes may auto-insert the rewritten prompt into the editor draft
package/command/create.md CHANGED
@@ -175,11 +175,14 @@ Before presenting the plan, verify:
175
175
  - [ ] All acceptance criteria are agent-executable
176
176
  - [ ] Top 2+ risks assessed
177
177
 
178
- ### 8. Approval, Create Beads, & Guide
178
+ ### 8. Approval, Sync Tracking, & Guide
179
179
 
180
180
  1. Present plan to user
181
181
  2. Wait for explicit approval
182
- 3. Only after approval, call `beads-village_add()` with title, description, and priority
182
+ 3. Only after approval, sync task tracking in the active workflow:
183
+ - Prefer `br` issue creation in DAG order when `.beads/` tracking is active and the runtime can execute `br`
184
+ - If a legacy `beads-village` MCP setup still exists, it may be used as a compatibility fallback
185
+ - Do **not** block plan handoff on missing legacy MCP support
183
186
  4. Then say: "Plan ready. Use `/start` to begin execution."
184
187
 
185
188
  ## Rules
@@ -195,7 +198,7 @@ Before presenting the plan, verify:
195
198
  - ✅ Include Conventions & Past Decisions section in plan
196
199
  - ✅ Every task must include a Task Packet
197
200
  - ✅ File Impact is the build contract
198
- - ✅ Create Beads issues only after explicit approval
201
+ - ✅ Create tracker issues only after explicit approval
199
202
  - ❌ NEVER ask generic questions without codebase context
200
203
  - ❌ NEVER skip acceptance criteria
201
204
  - ❌ NEVER end passively — always question or action
@@ -1,9 +1,9 @@
1
1
  ---
2
- description: Pre-create discussion phase — clarify intent, lock preferences, confirm assumptions, and write a planning-ready discussion artifact.
2
+ description: Pre-create discussion phase — run an interview-style clarification pass, lock preferences, confirm assumptions, and write a planning-ready discussion artifact.
3
3
  agent: plan
4
4
  ---
5
5
 
6
- You are the **Plan Agent** operating in discussion mode. Execute the `/discuss` command and write only the discussion artifact.
6
+ You are the **Plan Agent** operating in discussion mode. Execute the `/discuss` command as an **interview-style pre-plan phase** and write only the discussion artifact.
7
7
 
8
8
  ## Template
9
9
 
@@ -13,6 +13,13 @@ Use template at: `@.opencode/memory/_templates/discussion.md`
13
13
 
14
14
  Run a **pre-create discussion phase adapted for CliKit**.
15
15
 
16
+ The command name stays `/discuss`, but the interaction style should feel like a focused **interview**:
17
+ - surface the highest-impact gray areas first
18
+ - ask only the questions that change planning direction
19
+ - prefer structured choices over open-ended brainstorming when possible
20
+ - skip topics that are already settled by prior artifacts or strong codebase evidence
21
+ - end with a concise artifact that captures what the interview resolved
22
+
16
23
  This command exists to capture the decisions that `/create`, `/research`, and `/start` should not have to guess.
17
24
 
18
25
  Use it to:
@@ -59,13 +66,15 @@ If context is incomplete, capture the uncertainty in the artifact instead of blo
59
66
  - constraints or non-goals
60
67
  - sequencing between discuss/create/research/build
61
68
 
62
- 4. **Run an adaptive discussion**
63
- - Ask focused, high-signal questions
64
- - Prefer decisions over open-ended brainstorming once enough context exists
69
+ 4. **Run an adaptive interview**
70
+ - Start with the few gray areas most likely to change `/create`, `/research`, or `/start`
71
+ - Ask focused, high-signal questions one at a time when possible
72
+ - Prefer decisions or structured options over open-ended brainstorming once enough context exists
65
73
  - Avoid re-asking anything already confirmed by prior artifacts
66
- - If the repository strongly suggests a sensible default, present it as an assumption for confirmation
74
+ - If the repository strongly suggests a sensible default, present it as an assumption for confirmation instead of asking a vague question
75
+ - If multiple gray areas remain, prioritize the ones with the biggest scope or workflow impact first
67
76
 
68
- 5. **Lock what is known and defer the rest**
77
+ 5. **Lock what the interview resolved and defer the rest**
69
78
  - Record confirmed decisions explicitly
70
79
  - Separate confirmed assumptions from unresolved questions
71
80
  - Push non-critical ideas into a deferred section rather than expanding scope
@@ -85,7 +94,7 @@ Use this request schema:
85
94
 
86
95
  ```yaml
87
96
  type: "discussion"
88
- mode: "pre-create-phase"
97
+ mode: "interview-style-pre-create-phase"
89
98
  topic: "[Feature or topic being clarified]"
90
99
  goal: "[What outcome the user wants]"
91
100
  ambiguities:
@@ -97,12 +106,15 @@ constraints:
97
106
  workflow: "[Any sequencing or approval constraints]"
98
107
  format: "discussion-brief"
99
108
  depth: "standard" # quick | standard | deep
109
+ question_style: "adaptive-interview"
100
110
  ```
101
111
 
102
112
  ## Rules
103
113
 
104
114
  - Start from user intent, not technical implementation detail
105
115
  - Clarify only what changes planning, sequencing, or execution direction
116
+ - Treat `/discuss` as an interview, not an unbounded brainstorm
117
+ - Ask the minimum number of questions needed to remove planning-critical ambiguity
106
118
  - Prefer concrete decisions over vague summaries
107
119
  - Preserve unresolved items instead of guessing them away
108
120
  - Write only the final discussion artifact under `.opencode/memory/discussions/`
package/command/init.md CHANGED
@@ -39,9 +39,10 @@ Ensure these exist:
39
39
  - `.opencode/memory/reviews`
40
40
  - `.opencode/memory/handoffs`
41
41
  - `.opencode/memory/prds`
42
- - `.opencode/memory/beads`
43
42
  - `.opencode/memory/_templates`
44
43
 
44
+ Task tracking now lives in the project-root `.beads/` directory created by `br init`, not under `.opencode/memory/beads`.
45
+
45
46
  ### 4) Handle existing AGENTS.md safely
46
47
 
47
48
  If root `AGENTS.md` exists:
package/command/start.md CHANGED
@@ -28,20 +28,22 @@ If no plan exists:
28
28
  - Read `plan.md` — get objectives, context, task list, file impact, dependencies, and acceptance criteria
29
29
  - Read `discussion.md` (if referenced or latest relevant) — preserve locked intent and constraints
30
30
  - Read latest handoff in `.opencode/memory/handoffs/` (if exists) — resume from previous session
31
- - Check bead status via `beads-village_ls()`
31
+ - Check tracker state:
32
+ - prefer `br ready --json` / `br list --json` when `.beads/` is active
33
+ - if a legacy `beads-village` MCP is installed, you may also inspect reservations or inbox state
32
34
 
33
35
  ### 3. Determine Next Packet
34
36
 
35
37
  Find the first task / packet that is executable:
36
38
  - dependencies satisfied
37
- - within Beads ready state
39
+ - within the active tracker ready state when tracking exists
38
40
  - not blocked
39
41
 
40
42
  If resuming from handoff, pick up `in_progress` tasks first.
41
43
 
42
44
  ### 4. Execute Packet
43
45
 
44
- - Reserve packet files via `beads-village_reserve()`
46
+ - Reserve packet files when optional legacy reservations are available; otherwise use explicit file scope plus `git status` as the coordination primitive
45
47
  - Follow `files_in_scope` strictly
46
48
  - Implement only the active packet
47
49
 
@@ -58,7 +60,7 @@ If verification fails twice, stop and escalate.
58
60
 
59
61
  ### 6. Close Packet
60
62
 
61
- - Mark Beads task done
63
+ - Close or update tracker state when a tracked issue exists
62
64
  - Report evidence
63
65
  - Continue only if another ready packet exists and the user asked to keep going
64
66
 
package/command/status.md CHANGED
@@ -1,23 +1,26 @@
1
1
  ---
2
- description: Instant workspace snapshot — active Beads tasks, ready work, git state, and all memory artifacts in one view.
2
+ description: Instant workspace snapshot — tracker state, ready work, git state, and memory artifacts in one view.
3
3
  agent: build
4
4
  ---
5
5
 
6
- You are providing a **status overview** of the current workspace and beads.
6
+ You are providing a **status overview** of the current workspace and task tracker.
7
7
 
8
8
  ## Your Task
9
9
 
10
- Show the current state of work: beads, tasks, files, and git status.
10
+ Show the current state of work: tracker state, tasks, files, and git status.
11
11
 
12
12
  ## Process
13
13
 
14
- ### 1. Check Beads Village
14
+ ### 1. Check Task Tracking
15
15
 
16
- ```
17
- beads-village_status()
16
+ Preferred path:
17
+
18
+ ```bash
19
+ br ready --json
20
+ br list --json
18
21
  ```
19
22
 
20
- Also inspect ready work, reservations, and inbox state using the matching `beads-village_*` tools.
23
+ If a legacy `beads-village` MCP is installed, you may also inspect reservations, inbox state, or agent presence using the matching MCP tools.
21
24
 
22
25
  ### 2. Check Git State
23
26
 
@@ -48,7 +51,7 @@ Look for:
48
51
 
49
52
  ---
50
53
 
51
- ### 🎯 Beads Village
54
+ ### 🎯 Tracker State
52
55
 
53
56
  | Status | Count |
54
57
  |--------|-------|
@@ -62,6 +65,8 @@ Look for:
62
65
  1. [ID] [Title] (P[priority])
63
66
  2. [ID] [Title] (P[priority])
64
67
 
68
+ **Tracker Source:** `br` / `beads-village` / `none`
69
+
65
70
  ---
66
71
 
67
72
  ### 📁 Active Artifacts
@@ -113,11 +118,9 @@ Look for:
113
118
 
114
119
  | Area | Tool |
115
120
  |------|------|
116
- | Beads | `beads-village_status()` |
117
- | Tasks | `beads-village_ls()` |
118
- | Ready tasks | `beads-village_ls(status="ready")` |
119
- | Reservations | `beads-village_reservations()` |
120
- | Messages | `beads-village_inbox()` |
121
+ | Tracker | `br ready --json`, `br list --json` |
122
+ | Legacy reservations | `beads-village_reservations()` when available |
123
+ | Legacy inbox | `beads-village_inbox()` when available |
121
124
  | Git | `git status`, `git log` |
122
125
  | Artifacts | `glob`, `Read` |
123
126