opencodekit 0.7.0 → 0.9.0

package/dist/index.js

@@ -750,7 +750,7 @@ var cac = (name = "") => new CAC(name);
 // package.json
 var package_default = {
   name: "opencodekit",
-  version: "0.7.0",
+  version: "0.9.0",
   description: "CLI tool for bootstrapping and managing OpenCodeKit projects",
   type: "module",
   repository: {

package/dist/template/.opencode/AGENTS.md

@@ -79,13 +79,12 @@ Specify depth when delegating to control tool call budget:
 
 ## Tool Priority
 
-**GKG tools → LSP tools → AST tools → Built-in tools**
+**LSP tools → AST tools → Built-in tools**
 
-1. `gkg_search_codebase_definitions`, `gkg_get_references`, `gkg_repo_map` - Find symbols, usages, API overview
-2. `lsp_rename`, `lsp_code_actions`, `lsp_organize_imports` - Semantic refactoring (LSP-based)
-3. `ast-grep` - Semantic code search/replace (AST-based)
-4. `grep`, `glob` - Pattern matching, file discovery
-5. `read`, `edit`, `write` - File operations
+1. `lsp_rename`, `lsp_code_actions`, `lsp_organize_imports` - Semantic refactoring (LSP-based)
+2. `ast-grep` - Semantic code search/replace (AST-based)
+3. `grep`, `glob` - Pattern matching, file discovery
+4. `read`, `edit`, `write` - File operations
 
 **Rule**: Always `read` before `edit` to verify content.
 
@@ -296,15 +295,15 @@ Use all three:
 
 ## Beads Usage
 
-**Session start**: `bd doctor --fix` then `bd ready`
+**Session start**: `bd_doctor()` then `bd_claim()`
 **Session end**: Complete one bead fully before starting next
-**Weekly**: `bd cleanup --older-than 7d` then `bd sync`
+**Weekly**: `bd_cleanup(days=7)` then `bd_sync()`
 
 **Philosophy**: Beads is execution, not planning. Plan elsewhere, track in Beads.
 
-## Beads Village (Multi-Agent Coordination)
+## Beads Tools (Multi-Agent Coordination)
 
-MCP server for task coordination and file locking between agents.
+Native plugin tools for task coordination and file locking between agents.
 
 ### When to Use
 
@@ -315,41 +314,80 @@ MCP server for task coordination and file locking between agents.
 ### Core Workflow
 
 ```
-init() → claim() → reserve(paths) → [work] → done(id, msg) → RESTART
+bd_init() → bd_claim() → bd_reserve(paths) → [work] → bd_done(id, msg) → RESTART
 ```
 
-### Key Tools
+### Tool Reference
 
-**Session Management**
+**Lifecycle Tools**
 
-Start every session by calling `init` with your team name and role. This registers you in the workspace and enables role-based task filtering. For example, `init(team="project", role="fe")` joins as a frontend agent.
+Start every session by calling `bd_init` with your team name and role. This registers you in the workspace and enables role-based task filtering. For example, `bd_init({ team: "project", role: "fe" })` joins as a frontend agent.
 
-Check workspace state with `status(include_agents=true)` to see active agents, file locks, and pending messages.
+Call `bd_claim` to get the next ready task assigned to your role. It auto-filters based on task tags matching your role and marks the task as in_progress.
 
-**Task Operations**
+When work is complete, call `bd_done` with the task ID and completion message. This closes the task, releases all file reservations, and syncs with git. After `bd_done`, restart your session for fresh context.
 
-Call `claim` to get the next ready task assigned to your role. It auto-filters based on task tags matching your role.
+**Task Management Tools**
 
-When work is complete, call `done(id="bd-42", msg="Implemented feature X")` to close the task and notify other agents. After `done`, restart your session for a fresh context.
+Use `bd_add` to create new tasks for discovered work. Specify title, optional description, and priority (0=critical through 4=backlog). Use `bd_assign` to assign tasks to specific roles like fe, be, mobile, devops, or qa.
 
-**File Reservations**
+Call `bd_ls` to list tasks filtered by status: open, closed, in_progress, ready, or all. Use `bd_show` with a task ID to get full details including description, notes, and history.
 
-Before editing files, call `reserve(paths=["src/auth.ts"])` to lock them. This prevents other agents from modifying the same files. Call `release` when finished to unlock.
+**File Reservation Tools**
 
-**Messaging**
+Before editing any file, call `bd_reserve` with the file paths you need. This creates locks that prevent other agents from modifying the same files. Locks expire after 600 seconds by default.
 
-Send messages with `msg(subj="API Ready", global=true, to="all")` for cross-workspace announcements. Check incoming messages with `inbox(unread=true)`.
+Call `bd_release` to unlock files early, or let `bd_done` release them automatically. Use `bd_reservations` to see all active locks across the workspace before editing.
 
-### Integration with Commands
+**Messaging Tools**
 
-Use `/create` for the full spec workflow instead of the Village `add` tool. When implementing, `claim` gets your task and `reserve` locks files - Village handles the coordination while your `/implement` command handles the actual work. When finishing, `done` syncs state and notifies other agents.
+Send messages with `bd_msg` using a subject and optional body. Set `to: "all"` for broadcast messages visible to all agents. Check incoming messages with `bd_inbox`, optionally filtering to unread only.
+
+**Status and Maintenance Tools**
+
+Call `bd_status` to get workspace overview including ready task count, in-progress tasks, and active locks. Use `bd_sync` to manually sync with git.
+
+Run `bd_cleanup` periodically to remove old closed issues. Use `bd_doctor` to check and repair database health.
+
+**Analysis Tools**
+
+Call `bd_insights` for graph analysis showing bottlenecks and high-priority keystones. Use `bd_plan` to see a parallel execution plan with tasks grouped by priority tracks.
+
+Get `bd_priority` recommendations for what to work on next based on graph analysis. Use `bd_diff` to compare issue changes between git revisions.
+
+### Quick Start
+
+```typescript
+// 1. Join workspace
+bd_init({ team: "project", role: "fe" });
+
+// 2. Get next task
+const task = bd_claim();
+
+// 3. Lock files before editing
+bd_reserve({ paths: ["src/auth.ts", "src/types.ts"] });
+
+// 4. Do the work...
+
+// 5. Complete and restart
+bd_done({ id: task.id, msg: "Implemented auth" });
+// RESTART SESSION
+```
 
 ### Rules
 
-- **Always `init()` first** in any session using Village tools
+- **Always `bd_init()` first** in any session using beads tools
 - **Reserve before edit** to prevent conflicts
-- **One task per session** - restart after `done()`
-- **Use `msg(global=true)`** for cross-workspace announcements
+- **One task per session** - restart after `bd_done()`
+- **Use `bd_msg(to="all")`** for team-wide announcements
+
+### Skill
+
+Load `beads` skill for detailed workflow guidance:
+
+```
+skill({ name: "beads" })
+```
 
 ## Skills System
 

package/dist/template/.opencode/README.md

@@ -144,11 +144,9 @@ Memory (Permanent)     → Beads (Multi-session)    → Git (Audit Trail)
 
 Plugins run automatically in every session:
 
-| Plugin        | What it does                                                |
-| ------------- | ----------------------------------------------------------- |
-| **enforcer**  | OS notification when session idles with incomplete TODOs    |
-| **compactor** | Warns at 70%, 85%, 95% context usage - prevents rushed work |
-| **truncator** | Dynamic output truncation based on context remaining        |
+- **enforcer** - OS notification when session idles with incomplete TODOs
+- **compactor** - Warns at 70%, 85%, 95% context usage - prevents rushed work
+- **truncator** - Dynamic output truncation based on context remaining
 
 **Compactor thresholds**:
 
@@ -160,13 +158,11 @@ Plugins run automatically in every session:
 
 ## Custom Tools
 
-| Tool              | Purpose                                  |
-| ----------------- | ---------------------------------------- |
-| **memory-read**   | Load previous context, templates         |
-| **memory-update** | Save learnings, handoffs                 |
-| **memory-search** | Search across all memory files           |
-| **observation**   | Create structured observations           |
-| **ast-grep**      | Semantic code search/replace (AST-based) |
+- **memory-read** - Load previous context, templates
+- **memory-update** - Save learnings, handoffs
+- **memory-search** - Search across all memory files
+- **observation** - Create structured observations
+- **ast-grep** - Semantic code search/replace (AST-based)
 
 ### AST-Grep Usage
 
@@ -190,7 +186,7 @@ ast-grep pattern="oldFunc($$$)" rewrite="newFunc($$$)" dryRun=true
 
 ## MCP Services
 
-**Enabled by default (5 total):**
+**Enabled by default (4 total):**
 
 1. **context7** - Up-to-date library documentation (37.6k+ libraries)
    - Requires: CONTEXT7_API_KEY
@@ -204,18 +200,17 @@ ast-grep pattern="oldFunc($$$)" rewrite="newFunc($$$)" dryRun=true
    - No API key needed (public service)
    - GitHub: https://github.com/Shachlan/grep.app-mcp
 
-4. **gkg** - GitLab Knowledge Graph (local codebase semantic search)
-   - No API key needed (runs locally on port 27495)
-   - Docs: https://gitlab-org.gitlab.io/rust/knowledge-graph/
-   - Install: Follow https://gitlab-org.gitlab.io/rust/knowledge-graph/getting-started/install/
-
 **Optional (disabled by default):**
 
-5. **Framelink MCP for Figma** - Extract Figma layouts and design tokens
+4. **Framelink MCP for Figma** - Extract Figma layouts and design tokens
    - Requires: FIGMA_API_KEY
    - GitHub: https://github.com/GLips/Figma-Context-MCP (11.9k+ stars)
    - Enable: Set `"Framelink MCP for Figma": { "enabled": true }` in opencode.json
 
+5. **playwright** - Browser automation for testing
+   - No API key needed
+   - Use via skill: `skill({ name: "playwright" })` then `skill_mcp()`
+
 ---
 
 ## Getting Started Examples

package/dist/template/.opencode/agent/build.md

@@ -14,7 +14,6 @@ tools:
   webfetch: true
   websearch: true
   codesearch: true
-  gkg*: true
   ast-grep*: true
   lsp*: true
   context7*: true
@@ -47,11 +46,10 @@ Primary orchestrator. Execute-first. Autonomous task completion until resolved.
 
 ## Tool Priority
 
-1. **GKG tools** for code search (definitions, references, repo map)
-2. **LSP tools** for semantic refactoring (rename, code actions, organize imports)
-3. **AST-Grep** for semantic code search/replace
-4. **Built-in tools** for pattern matching (grep, glob, read)
-5. **Bash** for running tests, builds, commands
+1. **LSP tools** for semantic refactoring (rename, code actions, organize imports)
+2. **AST-Grep** for semantic code search/replace
+3. **Built-in tools** for pattern matching (grep, glob, read)
+4. **Bash** for running tests, builds, commands
 
 ### LSP Tools
 

package/dist/template/.opencode/agent/explore.md

@@ -13,7 +13,7 @@ tools:
   list: true
   todoread: false
   todowrite: false
-  gkg*: true
+  ast-grep*: true
 ---
 
 # Explore Agent
@@ -25,7 +25,7 @@ File search specialist. Navigate and explore codebases efficiently.
 - Finding files using glob patterns
 - Searching code with regex patterns
 - Reading and analyzing file contents
-- Semantic code search with GKG tools
+- Semantic code search with AST-Grep
 
 ## Guidelines
 
@@ -37,30 +37,30 @@ File search specialist. Navigate and explore codebases efficiently.
 
 ## Tool Priority
 
-**Use GKG tools FIRST, then fall back to built-in tools.**
+**Use AST-Grep for semantic search, then fall back to built-in tools.**
 
-### GKG Tools (Semantic Search)
+### AST-Grep (Semantic Search)
 
-| Tool                              | Use For                                    |
-| --------------------------------- | ------------------------------------------ |
-| `gkg_search_codebase_definitions` | Find functions, classes, constants by name |
-| `gkg_get_references`              | Find all callers/usages of a symbol        |
-| `gkg_read_definitions`            | Read function/class body only              |
-| `gkg_get_definition`              | Jump to definition from usage              |
-| `gkg_repo_map`                    | API-level overview of directories          |
+`ast-grep` finds functions, classes, and patterns semantically.
+
+**Pattern syntax:** `$NAME` = single node, `$$$` = zero or more nodes
+
+**Examples:**
+
+- `ast-grep pattern="function $NAME($$$) { $$$ }"` - Find all functions
+- `ast-grep pattern="console.log($$$)"` - Find all console.log calls
+- `ast-grep pattern="const [$S, $SET] = useState($$$)"` - Find React hooks
 
 ### Built-in Tools (Pattern Matching)
 
-| Tool   | Use For                           |
-| ------ | --------------------------------- |
-| `glob` | Find files by pattern (`**/*.ts`) |
-| `grep` | Search file contents with regex   |
-| `read` | Read specific file contents       |
+- `glob` - Find files by pattern (`**/*.ts`)
+- `grep` - Search file contents with regex
+- `read` - Read specific file contents
 
 ## Thoroughness Levels
 
-**Quick**: Single GKG search or glob. Read 1-3 files. Return immediately.
+**Quick**: Single ast-grep or glob. Read 1-3 files. Return immediately.
 
-**Medium**: GKG + grep verification. Check 2-3 naming conventions. Read 3-5 files.
+**Medium**: AST-grep + grep verification. Check 2-3 naming conventions. Read 3-5 files.
 
 **Very Thorough**: Comprehensive search across multiple terms and locations. Build dependency map. Report with file:line references.

package/dist/template/.opencode/agent/planner.md

@@ -16,7 +16,6 @@ tools:
   task: true
   todowrite: true
   todoread: true
-  gkg*: true
   context7*: true
   codesearch: true
   gh_grep*: true
@@ -60,12 +59,10 @@ Use **Facts/Guesses/Plans** in bead notes:
 
 ## Agent Assignments
 
-| Task Type              | Agent    |
-| ---------------------- | -------- |
-| Codebase search        | @explore |
-| Library docs, patterns | @scout   |
-| Code review, debugging | @review  |
-| Implementation         | @build   |
+- Codebase search → @explore
+- Library docs, patterns → @scout
+- Code review, debugging → @review
+- Implementation → @build
 
 **Typical chain**: research → plan → build → review
 

package/dist/template/.opencode/agent/review.md

@@ -11,7 +11,6 @@ tools:
   grep: true
   read: true
   list: true
-  gkg*: true
   webfetch: true
   websearch: true
   context7*: true
@@ -70,7 +69,7 @@ bd create "[type]: [description]" -t bug -p [0-4] -d "[details, file:line]"
 
 ## Tool Priority
 
-**Codebase**: gkg_search → gkg_get_references → read → grep
+**Codebase**: grep → ast-grep → read
 **Verification**: bash (tests, lint, type-check)
 **History**: `git log -p`, `git blame`
 

package/dist/template/.opencode/agent/rush.md

@@ -13,7 +13,6 @@ tools:
   list: true
   webfetch: true
   websearch: true
-  gkg*: true
   ast-grep*: true
   lsp*: true
   context7*: true
@@ -46,12 +45,11 @@ Fast execute-first agent. Speed over depth. Delegate anything complex.
 
 ## Tool Priority
 
-**GKG tools FIRST, then LSP, then AST-Grep, then built-in tools.**
+**LSP tools FIRST, then AST-Grep, then built-in tools.**
 
-1. `gkg_search_codebase_definitions`, `gkg_get_references` - Find symbols, usages
-2. `lsp_rename`, `lsp_organize_imports` - Semantic refactoring
-3. `ast-grep` - Semantic code search/replace
-4. `grep`, `glob` - Text search, file patterns
+1. `lsp_rename`, `lsp_organize_imports` - Semantic refactoring
+2. `ast-grep` - Semantic code search/replace
+3. `grep`, `glob` - Text search, file patterns
 
 ### LSP Tools (Fast Refactoring)
 

package/dist/template/.opencode/agent/scout.md

@@ -11,7 +11,6 @@ tools:
   grep: false
   read: false
   list: false
-  gkg*: false
   webfetch: true
   websearch: true
   context7*: true
@@ -32,62 +31,70 @@ External research: library docs, GitHub patterns, framework analysis.
 - Cross-repository analysis
 - Best practices research
 
-## Guidelines
+## First: Classify the Request
+
+Before searching, identify what you're dealing with.
 
-- Cite sources with links
-- No emojis in responses
-- Explain WHAT, WHY, HOW in deep mode
-- Compare implementations across repositories
+**Conceptual questions** sound like "how do I use X", "what's the best practice for Y", or "docs for Z". These need official documentation plus recent web sources. Run context7 and websearch in parallel.
 
-## Responsibility
+**Implementation questions** sound like "how does X implement Y", "show me the source of Z", or "internal logic of W". These need actual source code with permalinks. Clone the repo, find the code, construct a permalink.
 
-**DO**: Library docs, API references, GitHub code search, framework deep dives.
+**Context questions** sound like "why was this changed", "history of X", or "what issues led to Y". These need git history, issues, and PRs. Search issues and PRs, check git blame, find the discussion.
 
-**DON'T**: Local codebase search, code generation, implementation.
+**Comprehensive questions** are complex or ambiguous. Hit everything in parallel: docs, web search, GitHub code search, and source analysis.
 
 ## Quick Mode
 
-For API lookups, syntax help, configuration guides.
+For API lookups, syntax help, configuration guides. Triggered by: "how to", "syntax for", "API for", "docs for".
 
-```
-1. context7_resolve_library_id("library")
-2. context7_get_library_docs(libraryID, topic)
-3. Return: API signature + example + source link
-```
+Start with context7 to resolve the library ID, then query the specific topic. If context7 lacks coverage, fall back to websearch or codesearch. Return the API signature, a minimal example, and the source link.
 
-**Output**: 2-3 sentences + syntax example + link
-**Performance**: <10 seconds
+Run at least 2-3 tool calls in parallel. Output should be 2-3 sentences plus a code example. Target under 10 seconds.
 
 ## Deep Mode
 
-For cross-repository analysis, pattern comparison.
+For cross-repository analysis and pattern comparison. Triggered by: "how do others", "compare", "best practices", "production patterns".
+
+Search GitHub for real implementations using gh_grep_searchGitHub. Vary your queries to hit different angles of the same concept. Compare 3-5 implementations from different repositories. Synthesize the common patterns and note the tradeoffs.
+
+Run at least 4-6 tool calls in parallel. Output should include a summary, multiple code examples, tradeoffs, and a recommendation.
+
+## Permalink Protocol
 
-```
-1. gh_grep_searchGitHub(pattern, language)
-2. context7 for official docs
-3. Compare 3-5 implementations
-4. Synthesize patterns
-```
+Every code reference must include a GitHub permalink. Never link to a branch or tag that can change.
 
-**Output**: Summary + code examples + tradeoffs + recommendations
-**Performance**: 30-60 seconds
+To construct a permalink: clone the repo with depth 1, get the commit SHA with `git rev-parse HEAD`, then build the URL as `https://github.com/owner/repo/blob/<sha>/path/to/file#L10-L20`.
+
+When citing code, format it as the claim, then the evidence with a permalink, then the code block, then a brief explanation of why this matters.
 
 ## Tool Priority
 
-1. **context7**: Official documentation
-2. **gh_grep_searchGitHub**: Real GitHub code
-3. **codesearch**: Code examples
-4. **websearch**: Best practices, comparisons
-5. **webfetch**: Official docs, RFCs, specific URLs
+Use context7 first for official documentation. It's fastest and most authoritative for library APIs.
+
+Use gh_grep_searchGitHub for real GitHub code patterns. Vary your queries: search for the function name, then the configuration key, then the error message.
+
+Use codesearch for code examples when you need broader coverage than a single repo.
+
+Use websearch for best practices, comparisons, and recent articles. Always append the current year to avoid stale results.
+
+Use webfetch for specific URLs: official docs, RFCs, blog posts the user shared.
+
+## When Things Fail
+
+If context7 doesn't find the library, clone the repo directly and read the source plus README.
+
+If gh_grep returns nothing, broaden your query. Search for concepts instead of exact function names.
+
+If you hit API rate limits, work from already-cloned repos in the temp directory.
+
+If you're uncertain, say so explicitly. Propose a hypothesis but flag it as unverified.
+
+## Guidelines
 
-## Mode Detection
+Cite sources with links. No emojis. Explain what the code does, why it's designed that way, and how to use it.
 
-**Quick**: "how to", "syntax for", "API for", "docs for"
-**Deep**: "how do others", "compare", "best practices", "production patterns"
+Compare implementations across repositories when doing deep research. Note which patterns are common versus unique.
 
 ## Delegation
 
-- Local codebase → @explore
-- Complex reasoning → @review
-- Code generation → @build
-- Architecture planning → @planner
+If the task requires local codebase search, hand off to @explore. If it requires complex reasoning or debugging, hand off to @review. If it requires code generation, hand off to the main agent. If it requires architecture planning, hand off to @planner.

package/dist/template/.opencode/agent/vision.md

@@ -16,7 +16,6 @@ tools:
   task: true
   todowrite: true
   todoread: true
-  gkg*: true
   context7*: true
   codesearch: true
   gh_grep*: true
@@ -57,12 +56,10 @@ Comprehensive analysis with actionable recommendations.
 **Use when:** Design review, accessibility audit, system consistency check
 **Skills:** Combine multiple skills based on task:
 
-| Task            | Primary Skill         | Supporting Skills     |
-| --------------- | --------------------- | --------------------- |
-| UI/UX Review    | `ui-ux-research`      | `frontend-aesthetics` |
-| Accessibility   | `accessibility-audit` | `visual-analysis`     |
-| Design System   | `design-system-audit` | `frontend-aesthetics` |
-| Mockup Analysis | `mockup-to-code`      | `visual-analysis`     |
+- **UI/UX Review**: Primary `ui-ux-research`, supporting `frontend-aesthetics`
+- **Accessibility**: Primary `accessibility-audit`, supporting `visual-analysis`
+- **Design System**: Primary `design-system-audit`, supporting `frontend-aesthetics`
+- **Mockup Analysis**: Primary `mockup-to-code`, supporting `visual-analysis`
 
 ```
 Load skill(s) → Systematic analysis → Structured findings → Recommendations
@@ -89,22 +86,19 @@ Load skill(s) → Systematic analysis → Structured findings → Recommendation
 
 ## Skill Selection Guide
 
-| User Request                  | Load This Skill       |
-| ----------------------------- | --------------------- |
-| "Review this mockup"          | `visual-analysis`     |
-| "Check accessibility"         | `accessibility-audit` |
-| "Audit our design system"     | `design-system-audit` |
-| "Convert this design to code" | `mockup-to-code`      |
-| "Is this too AI-looking?"     | `frontend-aesthetics` |
-| "Deep UI/UX analysis"         | `ui-ux-research`      |
+- "Review this mockup" → `visual-analysis`
+- "Check accessibility" → `accessibility-audit`
+- "Audit our design system" → `design-system-audit`
+- "Convert this design to code" → `mockup-to-code`
+- "Is this too AI-looking?" → `frontend-aesthetics`
+- "Deep UI/UX analysis" → `ui-ux-research`
 
 ## Tool Priority
 
 1. **Skills** (`use_skill`) - Load appropriate skill for the task
 2. **Read/Glob** - Inspect existing components and styles
-3. **GKG tools** - Find design-related code definitions
-4. **Webfetch/Websearch** - Design inspiration and references
-5. **Context7** - UI library documentation
+3. **Webfetch/Websearch** - Design inspiration and references
+4. **Context7** - UI library documentation
 
 ## Output Format
 
@@ -138,12 +132,10 @@ All analyses should follow this structure:
 
 ## Delegation
 
-| Need                  | Delegate To |
-| --------------------- | ----------- |
-| Implement changes     | @build      |
-| Research UI libraries | @scout      |
-| Review implementation | @review     |
-| Plan large redesign   | @planner    |
+- Implement changes → @build
+- Research UI libraries → @scout
+- Review implementation → @review
+- Plan large redesign → @planner
 
 ## Anti-Patterns to Flag
 

package/dist/template/.opencode/command/analyze-project.md

@@ -10,7 +10,7 @@ agent: planner
 ## Quick Status
 
 1. **Git:** `git status` - current branch, changes
-2. **Tasks:** `bd list` - active beads
+2. **Tasks:** `bd_ls({ status: "open" })` - active beads
 3. **CI:** Check build status
 4. **Dependencies:** Check for outdated packages
 
@@ -18,8 +18,8 @@ agent: planner
 
 Find actionable tasks with no blockers:
 
-```bash
-bd ready
+```typescript
+bd_ls({ status: "ready", limit: 10, offset: 0 });
 ```
 
 This shows beads that are unblocked and ready to start. Use `/implement <bead-id>` to begin work on any of these.
@@ -28,9 +28,9 @@ This shows beads that are unblocked and ready to start. Use `/implement <bead-id
 
 ### Task Overview
 
-```bash
-bd list --status open
-bd ready
+```typescript
+bd_ls({ status: "open", limit: 10, offset: 0 });
+bd_ls({ status: "ready", limit: 10, offset: 0 });
 ```
 
 For active beads, read spec from `.beads/artifacts/<bead-id>/spec.md`
@@ -39,8 +39,8 @@ For active beads, read spec from `.beads/artifacts/<bead-id>/spec.md`
 
 Check what's blocking progress:
 
-```bash
-bd list --status blocked
+```typescript
+bd_ls({ status: "blocked", limit: 10, offset: 0 });
 ```
 
 For each blocked bead, identify the blocker and either resolve it or escalate.
@@ -55,7 +55,7 @@ For each blocked bead, identify the blocker and either resolve it or escalate.
 
 ### Recommendations
 
-- **Immediate:** Tasks from `bd ready` to start now
+- **Immediate:** Tasks from `bd_ls({ status: "ready" })` to start now
 - **Blocked:** Dependencies preventing progress
 - **Attention:** Areas needing cleanup or refactoring
 - **Updates:** Dependency updates needed

package/dist/template/.opencode/command/create.md

@@ -47,14 +47,19 @@ Approve? (yes/modify)
 
 On approval:
 
-```bash
-bd create "[title]" -t [type] -p [priority] -d "[description]" --json
+```typescript
+bd_add({
+  title: "[title]",
+  type: "[type]",
+  pri: [priority],
+  desc: "[description]",
+});
 ```
 
 **If using Beads Village for multi-agent coordination:** Add role tags so tasks can be auto-assigned to the right agent:
 
-```
-add(title="[title]", tags=["[role]"], priority=[0-4])
+```typescript
+bd_add({ title: "[title]", type: "[type]", pri: [priority], tags: ["[role]"] });
 ```
 
 This makes the task claimable by agents with matching roles.