opencodekit 0.22.0 → 0.23.1

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

@@ -1,34 +1,20 @@
 ---
-description: Create a bead with specification, claim it, and prepare workspace
-argument-hint: "<description> [--type epic|feature|task|bug] [--spec-only]"
+description: Create a specification with PRD, tasks, and workspace setup
+argument-hint: "<description>"
 agent: build
 ---
 
 # Create: $ARGUMENTS
 
-Create a bead, write its specification (PRD), claim it, set up the workspace, and convert to executable tasks — ready for `/ship`.
+Create a specification (PRD), set up workspace, and define executable tasks — ready for `/ship`.
 
-> **Workflow:** **`/create`** → `/ship <id>`
->
-> Use `--spec-only` to create the specification without claiming or setting up workspace.
-
-## Load Skills
-
-```typescript
-skill({ name: "beads" });
-skill({ name: "memory-grounding" });
-skill({ name: "workspace-setup" });
-skill({ name: "prd" }); // PRD template guidance
-skill({ name: "prd-task" }); // PRD → executable tasks (Phase 8)
-```
+> **Workflow:** **`/create`** → `/ship`
 
 ## Parse Arguments
 
 | Argument        | Default       | Description                               |
 | --------------- | ------------- | ----------------------------------------- |
 | `<description>` | required      | What to build/fix (quoted string)         |
-| `--type`        | auto-detected | Override: epic, feature, task, bug        |
-| `--spec-only`   | false         | Create spec without claiming or workspace |
 
 ## Determine Input Type
 
@@ -36,13 +22,12 @@ skill({ name: "prd-task" }); // PRD → executable tasks (Phase 8)
 | ----------- | -------------------- | ----------------------------- |
 | Quoted text | `"description here"` | Create PRD from description   |
 | Short form  | Simple string        | Ask for more detail if needed |
-| `--type`    | Flag provided        | Use provided type             |
 
 ## Before You Create
 
-- **Be certain**: Only create beads you're confident have clear scope
+- **Be certain**: Only create specs you're confident have clear scope
 - **Don't over-spec**: If the description is vague, ask clarifying questions first
-- **Check duplicates**: Always run Phase 1 duplicate check
+- **Check duplicates**: Always check for existing work
 - **No implementation**: This command creates specs and workspace — don't write implementation code
 - **Verify PRD**: Before saving, verify all sections are filled (no placeholders)
 - **Flag uncertainty**: Use `[NEEDS CLARIFICATION]` markers for unknowns — never guess silently
@@ -53,30 +38,16 @@ skill({ name: "prd-task" }); // PRD → executable tasks (Phase 8)
 | --------- | -------------------------------------------- |
 | `explore` | Finding patterns in codebase, affected files |
 | `scout`   | External research, best practices            |
-| `br`      | Creating and managing beads                  |
 
 ## Phase 1: Duplicate Check
 
 ### Memory Search
 
-Follow the [memory-grounding](../skill/memory-grounding/SKILL.md) skill protocol. Focus on: duplicate bead detection, prior decisions.
-
-### Bead List Check
-
-```bash
-br list --status=open --status=in_progress
-```
-
-If a matching bead exists, stop and tell the user to use `/ship <id>` instead.
-
-## Phase 2: Classify Type
+Search memory for: prior decisions, similar work.
 
-If `--type` was provided, use it directly. Otherwise, suggest a type based on the description and ask the user to confirm:
+### Existing Work Check
 
-- **epic**: Multi-session, cross-domain (redesign, migrate, overhaul)
-- **feature**: New capability, scoped (add, implement, build, integrate)
-- **bug**: Something broken (fix, error, crash, not working)
-- **task**: Tactical change, clear scope (everything else)
+Check `.opencode/artifacts/.active` for existing work in progress. If active slug exists with a `spec.md`, ask user if they want to continue with `/ship` instead.
 
 ## Phase 3: Choose Research Depth
 
@@ -136,16 +107,19 @@ Based on research depth choice, spawn agents:
 
 **While agents run**, ask clarifying questions if the description lacks scope or expected outcome. For bugs, also ask for reproduction steps and expected vs actual behavior.
 
-## Phase 5: Create Bead
+## Phase 5: Initialize Plan
 
-Extract bead title and description from `$ARGUMENTS` before creating the bead.
+Extract title and description from `$ARGUMENTS`:
 
 - If user provided a single line, use it for both title and description.
 - If user provided multiple lines, use first line as title and full text as description.
 
+Derive a kebab-case slug from the title. This slug becomes the feature's namespace:
+
 ```bash
-BEAD_ID=$(br create --title "$TITLE" --description "$DESCRIPTION" --type $BEAD_TYPE --json | jq -r '.id')
-mkdir -p ".beads/artifacts/$BEAD_ID"
+SLUG=$(echo "$TITLE" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9 ]//g' | tr ' ' '-' | sed 's/--*/-/g; s/^-//; s/-$//')
+mkdir -p ".opencode/artifacts/$SLUG"
+echo "$SLUG" > ".opencode/artifacts/.active"
 ```
 
 ## Phase 6: Determine PRD Rigor
@@ -154,13 +128,12 @@ Not every change needs a full spec. Assess complexity to choose the right PRD le
 
 | Signal | Lite PRD | Full PRD |
 | --- | --- | --- |
-| Type | `bug`, `task` | `feature`, `epic` |
+| Scope | Simple, single-concern | Cross-cutting, multi-system |
 | Files affected | 1-3 | 4+ |
-| Scope | Clear, single-concern | Cross-cutting, multi-system |
 | Research depth | Skip or Minimal | Standard or Deep |
 | Description | "Fix X in Y" | "Implement X with Y and Z" |
 
-**Auto-detect:** If type is `bug` or `task` AND research was Skip/Minimal AND description is a single sentence → default to Lite.
+**Auto-detect:** If research was Skip/Minimal AND description is a single sentence → default to Lite.
 
 ### Lite PRD Format
 
@@ -190,7 +163,7 @@ For simple, well-scoped work (bugs, small tasks):
 
 For features and complex work, use the full template:
 
-Read the PRD template from `.opencode/memory/_templates/prd.md` and write it to `.beads/artifacts/$BEAD_ID/prd.md`.
+Read the PRD template and write it to the active feature's spec (`.opencode/artifacts/$(cat .opencode/artifacts/.active)/spec.md`).
 
 ## Phase 7: Write PRD
 
@@ -214,7 +187,7 @@ Copy and fill the PRD template (lite or full) using context from Phase 4.
 
 ### Task Format
 
-Tasks must follow the `prd-task` skill format:
+Tasks must follow this format:
 
 - Title with `[category]` tag
 - One-sentence **end state** description (not step-by-step)
@@ -236,32 +209,22 @@ Before saving, verify:
 
 If any check fails, fix it — don't ask the user.
 
-## Phase 9: Claim and Prepare Workspace
-
-**If `--spec-only` was passed, skip to Phase 12 (Report).**
+## Phase 9: Prepare Workspace
 
 ### Workspace Check
 
 ```bash
 git status --porcelain
 git branch --show-current
-br list --status=in_progress
 ```
 
 - If uncommitted changes: ask user to stash, commit, or continue
-- If other tasks in progress: warn before claiming another
-
-### Claim Bead
-
-```bash
-br update $BEAD_ID --status in_progress
-```
 
 ### Create Branch
 
 ### Workspace Setup
 
-Follow the [workspace-setup](../skill/workspace-setup/SKILL.md) skill protocol.
+Set up the workspace: create branch, install deps if needed.
 
 Additionally offer a "Create worktree" option:
 
@@ -271,21 +234,16 @@ skill({ name: "using-git-worktrees" });
 
 ## Phase 10: Convert PRD to Tasks
 
-Use `prd-task` skill to convert PRD markdown → executable JSON (`prd.json`).
+Convert PRD markdown → executable JSON (`prd.json`).
 
 ## Phase 11: Report
 
 Output:
 
-1. Bead ID and type
-2. PRD location (`.beads/artifacts/$BEAD_ID/prd.md`)
-3. Summary: task count, success criteria count, affected files count
-4. Branch name and workspace (if claimed)
-5. Next step: `/ship $BEAD_ID` (or `/plan $BEAD_ID` for complex work)
-
-```bash
-br comments add $BEAD_ID "Created prd.md with [N] tasks, [M] success criteria"
-```
+1. Summary: task count, success criteria count, affected files count
+2. Branch name and workspace (if claimed)
+3. Active feature: `.opencode/artifacts/$(cat .opencode/artifacts/.active)/`
+4. Next step: `/ship` (or `/plan` for complex work)
 
 ---
 
@@ -294,5 +252,5 @@ br comments add $BEAD_ID "Created prd.md with [N] tasks, [M] success criteria"
 | Need               | Command      |
 | ------------------ | ------------ |
 | Research first     | `/research`  |
-| Plan after spec    | `/plan <id>` |
-| Implement and ship | `/ship <id>` |
+| Plan after spec    | `/plan`      |
+| Implement and ship | `/ship`      |

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

@@ -25,7 +25,6 @@ Design a component, page, or design system with a clear aesthetic point of view.
 
 ```typescript
 skill({ name: "frontend-design" }); // Design system guidance, anti-patterns, references
-skill({ name: "ux-quality-gates" }); // IA, forms, recovery, loading, usability gates
 ```
 
 ---
@@ -66,7 +65,7 @@ State these decisions explicitly:
 5. **State model** — empty, loading, error, success, disabled, and optimistic states required
 6. **Pattern selection** — form, table/list/grid, notification, modal, or navigation pattern if applicable
 
-Use the `ux-quality-gates` skill to keep these decisions concrete.
+Keep these decisions concrete and explicit.
 
 ---
 

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

@@ -6,7 +6,7 @@ agent: plan
 
 # Explore: $ARGUMENTS
 
-Think through an idea, problem, or approach with structured alternatives and tradeoffs — before committing to a bead or plan.
+Think through an idea, problem, or approach with structured alternatives and tradeoffs — before committing to a plan.
 
 > **Workflow:** **`/explore`** → `/create` (if worth pursuing) or discard
 >
@@ -18,7 +18,6 @@ Think through an idea, problem, or approach with structured alternatives and tra
 
 ```typescript
 skill({ name: "brainstorming" }); // Collaborative refinement
-skill({ name: "memory-grounding" }); // Load past decisions
 ```
 
 ## Phase 1: Ground
@@ -134,8 +133,8 @@ Write the proposal as a structured document:
 `/create "[description based on chosen approach]"`
 ```
 
-**If a bead exists:** Save to `.beads/artifacts/$BEAD_ID/exploration.md`
-**If no bead:** Display inline, don't create files.
+**If a plan exists:** Save to `.opencode/artifacts/$(cat .opencode/artifacts/.active)/research.md`
+**If no plan:** Display inline, don't create files.
 
 ## Phase 6: Ask User
 

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

@@ -11,7 +11,6 @@ Systematically debug and fix the reported issue.
 ## Load Skills
 
 ```typescript
-skill({ name: "systematic-debugging" });
 skill({ name: "root-cause-tracing" });
 skill({ name: "verification-before-completion" });
 ```

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

@@ -14,11 +14,8 @@ Initialize project setup. Run once per project. Supports three modes via argumen
 ## Load Skills
 
 ```typescript
-skill({ name: "index-knowledge" });
-skill({ name: "context-initialization" });
 skill({ name: "brainstorming" });
 skill({ name: "verification-before-completion" });
-skill({ name: "swarm-coordination" }); // For --brownfield analysis
 ```
 
 ## Parse Arguments
@@ -58,7 +55,7 @@ Show detected summary and ask for confirmation before writing.
 
 ### Phase 3: Create AGENTS.md
 
-Create `./AGENTS.md` — target <60 lines (max 150). Follow `index-knowledge` format:
+Create `./AGENTS.md` — target <60 lines (max 150). Include:
 - Tech stack with versions, file structure, validated commands
 - Code example from actual codebase
 - Testing conventions, boundaries, gotchas

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

@@ -1,41 +1,27 @@
 ---
-description: Create detailed implementation plan with TDD steps for a bead
-argument-hint: "<bead-id> [--create-beads]"
+description: Create detailed implementation plan with TDD steps
 agent: plan
 ---
 
-# Plan: $ARGUMENTS
+# Plan
 
 Create a detailed implementation plan with TDD steps. Optional deep-planning between `/create` and `/ship`.
 
-> **Workflow:** `/create` → **`/plan <id>`** (optional) → `/ship <id>`
+> **Workflow:** `/create` → **`/plan`** (optional) → `/ship`
 >
-> Bead MUST be `in_progress` with `prd.md`. Use `/create` first.
->
-> **When to use:** Complex tasks where PRD verification steps aren't enough guidance. Skip for simple tasks.
-
-## Load Skills
-
-```typescript
-skill({ name: "beads" });
-skill({ name: "memory-grounding" });
-skill({ name: "writing-plans" }); // TDD plan format
-// For user-facing UI work: skill({ name: "ux-quality-gates" });
-```
+> **When to use:** Complex tasks where spec verification steps aren't enough guidance. Skip for simple tasks.
 
 ## Parse Arguments
 
-| Argument         | Default  | Description                       |
-| ---------------- | -------- | --------------------------------- |
-| `<bead-id>`      | required | The bead to plan                  |
-| `--create-beads` | false    | Create child beads for each phase |
+| Argument | Default  | Description                       |
+| -------- | -------- | --------------------------------- |
+| none     | —        | Plan based on current spec        |
 
 ## Before You Plan
 
 - **Be certain**: Only create tasks you're confident about
-- **Don't over-plan**: If the PRD is clear, trust it
+- **Don't over-plan**: If the spec is clear, trust it
 - **Budget context**: Target ~50% context per execution
-- **Split signals**: Create child beads for complex work
 - **Vertical slices**: Each task should cover one feature end-to-end
 
 ## Phase 0: Institutional Research (Mandatory)
@@ -46,7 +32,7 @@ Before touching the PRD or planning anything, load what the codebase already kno
 
 ### Step 1: Search institutional memory
 
-Follow the [memory-grounding](../skill/memory-grounding/SKILL.md) skill protocol. Focus on: bugfixes, existing plans (ask user before overwriting).
+Search memory for: bugfixes, existing plans (ask user before overwriting).
 
 If relevant observations found: incorporate them directly into the plan. Don't re-solve solved problems.
 
@@ -92,17 +78,10 @@ task({
 
 ## Phase 1: Guards
 
-```bash
-br show $ARGUMENTS
-```
-
-Read `.beads/artifacts/$ARGUMENTS/` to check what artifacts exist.
-
 Verify:
 
-- Bead is `in_progress`
-- `prd.md` exists
-- If `plan.md` already exists, ask user: overwrite or skip?
+- `.opencode/artifacts/$(cat .opencode/artifacts/.active)/spec.md` exists (if not, tell user to run `/create` first)
+- If `.opencode/artifacts/$(cat .opencode/artifacts/.active)/plan.md` already exists, ask user: overwrite or skip?
 
 ## Phase 2: Discovery Assessment
 
@@ -243,7 +222,7 @@ Assess size to determine plan structure:
 | ------------- | --------- | ---------------------------------------- |
 | S (1-3 files) | 2-4 tasks | Single plan, no phases                   |
 | M (3-8 files) | 5-8 tasks | 2-3 phases                               |
-| L (8+ files)  | 9+ tasks  | Create child beads with `--create-beads` |
+| L (8+ files)  | 9+ tasks  | Split into separate plans for each subsystem |
 
 ## Phase 6: Dependency Graph & Wave Assignment
 
@@ -272,14 +251,14 @@ Wave 3: C (depends on B)
 
 ## Phase 7: Write Plan
 
-Write `.beads/artifacts/$ARGUMENTS/plan.md` following the `writing-plans` skill format:
+Write `.opencode/artifacts/$(cat .opencode/artifacts/.active)/plan.md`:
 
 ### Required Plan Header
 
 ```markdown
 # [Feature] Implementation Plan
 
-> **For Claude:** REQUIRED SUB-SKILL: Use skill({ name: "executing-plans" }) to implement this plan task-by-task.
+> **For Claude:** Implement this plan task-by-task.
 
 **Goal:** [Outcome-shaped goal from PRD]
 
@@ -361,15 +340,18 @@ Scan `plan.md` content for these patterns:
 ### Check Process
 
 ```bash
+ACTIVE_SLUG=$(cat .opencode/artifacts/.active 2>/dev/null)
+if [ -z "$ACTIVE_SLUG" ]; then echo "No active feature."; exit 1; fi
+ARTIFACT_DIR=".opencode/artifacts/$ACTIVE_SLUG"
 # Scan plan for violation patterns (fixed-string mode to avoid regex false positives)
-grep -inF "git add ." .beads/artifacts/$ARGUMENTS/plan.md
-grep -inF "git add -A" .beads/artifacts/$ARGUMENTS/plan.md
-grep -inF -- "--no-verify" .beads/artifacts/$ARGUMENTS/plan.md
-grep -inF "force push" .beads/artifacts/$ARGUMENTS/plan.md
-grep -inF -- "--force" .beads/artifacts/$ARGUMENTS/plan.md
-grep -inF "reset --hard" .beads/artifacts/$ARGUMENTS/plan.md
-grep -inF "checkout ." .beads/artifacts/$ARGUMENTS/plan.md
-grep -inF "clean -fd" .beads/artifacts/$ARGUMENTS/plan.md
+grep -inF "git add ." "$ARTIFACT_DIR/plan.md"
+grep -inF "git add -A" "$ARTIFACT_DIR/plan.md"
+grep -inF -- "--no-verify" "$ARTIFACT_DIR/plan.md"
+grep -inF "force push" "$ARTIFACT_DIR/plan.md"
+grep -inF -- "--force" "$ARTIFACT_DIR/plan.md"
+grep -inF "reset --hard" "$ARTIFACT_DIR/plan.md"
+grep -inF "checkout ." "$ARTIFACT_DIR/plan.md"
+grep -inF "clean -fd" "$ARTIFACT_DIR/plan.md"
 ```
 
 Also check:
@@ -400,16 +382,7 @@ If violations found:
 Violations resolved. Plan is compliant.
 ```
 
-## Phase 9: Create Child Beads (if --create-beads or L size)
-
-For large work, create child beads for each plan phase:
-
-```bash
-CHILD=$(br create "[Phase title]" --type task --json | jq -r '.id')
-br dep add $CHILD $ARGUMENTS
-```
-
-## Phase 10: Report
+## Phase 9: Report
 
 Output:
 
@@ -419,18 +392,15 @@ Output:
 4. **Dependency Waves:** [N] waves for parallel execution
 5. **Task count:** [N] tasks, [M] TDD steps
 6. **Files affected:** [List]
-7. **Plan location:** `.beads/artifacts/$ARGUMENTS/plan.md`
-8. **Child bead hierarchy:** (if created)
-9. **Next step:** `/ship $ARGUMENTS`
+7. **Plan location:** `.opencode/artifacts/$(cat .opencode/artifacts/.active)/plan.md`
+8. **Next step:** `/ship`
 
-```bash
-br comments add $ARGUMENTS "Created plan.md: Level [N] discovery, [X] waves, [Y] tasks, [Z] TDD steps"
-```
+---
 
 ## Related Commands
 
 | Need           | Command      |
 | -------------- | ------------ |
 | Create spec    | `/create`    |
-| Execute plan   | `/ship <id>` |
+| Execute plan   | `/ship`      |
 | Research first | `/research`  |

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

@@ -1,6 +1,6 @@
 ---
-description: Create and submit pull request with bead traceability
-argument-hint: "[bead-id] [--draft]"
+description: Create and submit a pull request
+argument-hint: "[--draft]"
 agent: build
 ---
 
@@ -9,18 +9,14 @@ agent: build
 ## Load Skills
 
 ```typescript
-skill({ name: "beads" });
-skill({ name: "memory-grounding" });
-skill({ name: "verification-gates" });
 skill({ name: "verification-before-completion" });
 ```
 
 ## Parse Arguments
 
-| Argument    | Default  | Description        |
-| ----------- | -------- | ------------------ |
-| `<bead-id>` | optional | Link PR to bead    |
-| `--draft`   | false    | Create as draft PR |
+| Argument  | Default | Description        |
+| --------- | ------- | ------------------ |
+| `--draft` | false   | Create as draft PR |
 
 ## Phase 1: Pre-PR Verification
 
@@ -30,7 +26,7 @@ git status --porcelain
 
 If uncommitted changes exist, ask whether to commit first.
 
-Follow the [verification-gates](../skill/verification-gates/SKILL.md) skill protocol. All gates must pass before creating the PR.
+All gates must pass before creating the PR.
 
 Check `package.json` scripts, `Makefile`, or `justfile` for project-specific commands first — prefer those over generic defaults.
 
@@ -40,7 +36,7 @@ If any gate fails, stop. Fix errors first, then run `/pr` again.
 
 ### Memory Grounding
 
-Follow the [memory-grounding](../skill/memory-grounding/SKILL.md) skill protocol. Include relevant findings in the PR description.
+Search memory for relevant findings to include in the PR description.
 
 ### Git Context
 
@@ -50,27 +46,13 @@ git log main...HEAD --oneline
 git diff main...HEAD --stat
 ```
 
-If bead ID provided:
-
-```bash
-br show $ARGUMENTS
-```
-
-Read `.beads/artifacts/$ARGUMENTS/` to check what artifacts exist.
-
-Read the PRD to extract goal and success criteria for the PR description.
+Read `.opencode/artifacts/$(cat .opencode/artifacts/.active)/spec.md` to extract goal and success criteria for the PR description.
 
 ## Phase 2B: Pre-PR Review
 
 This is the last gate before code hits GitHub. Run it every time.
 
-Load the review skill:
-
-```typescript
-skill({ name: "requesting-code-review" });
-```
-
-Run **5 parallel agents**: security/correctness, performance/architecture, type-safety/tests, conventions/patterns, simplicity/completeness.
+Run **5 parallel agents** for review: security/correctness, performance/architecture, type-safety/tests, conventions/patterns, simplicity/completeness.
 
 ```bash
 BASE_SHA=$(git rev-parse origin/main 2>/dev/null || git merge-base HEAD origin/main)
@@ -147,7 +129,7 @@ EOF
 
 If `--draft`, add `--draft` flag.
 
-If bead ID provided, add artifacts section linking to `.beads/artifacts/$ARGUMENTS/prd.md`.
+Add a link to `.opencode/artifacts/$(cat .opencode/artifacts/.active)/spec.md` for requirements context.
 
 ## Output
 

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

@@ -11,7 +11,6 @@ Improve code quality without changing external behavior.
 ## Load Skills
 
 ```typescript
-skill({ name: "code-simplification" });
 skill({ name: "verification-before-completion" });
 ```
 

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

@@ -1,6 +1,6 @@
 ---
-description: Research a topic or bead before implementation
-argument-hint: "<topic-or-bead-id> [--quick|--thorough]"
+description: Research a topic before implementation
+argument-hint: "<topic> [--quick|--thorough]"
 agent: scout
 ---
 
@@ -10,39 +10,23 @@ Gather information before implementation. Find answers, document findings, stop
 
 > Research can happen at any phase when you need external information or codebase understanding.
 
-## Load Skills
-
-```typescript
-skill({ name: "beads" });
-skill({ name: "memory-grounding" });
-// For --thorough mode:
-skill({ name: "deep-research" });
-```
-
 ## Parse Arguments
 
 | Argument         | Default  | Description                         |
 | ---------------- | -------- | ----------------------------------- |
-| Topic or bead ID | required | What to research                    |
+| Topic            | required | What to research                    |
 | `--quick`        | false    | ~10 tool calls, single question     |
 | `--thorough`     | false    | ~100+ calls, comprehensive analysis |
 
 Default depth: ~30 tool calls for moderate exploration.
 
-## Determine Input Type
-
-| Input Type | Detection                   | Action                            |
-| ---------- | --------------------------- | --------------------------------- |
-| Bead ID    | Matches `br-xxx` or numeric | Research within that bead context |
-| Topic      | String                      | Standalone research               |
-
 ## Before You Research
 
 - **Be certain**: Only research what you need for implementation
 - **Don't over-research**: Stop when you have enough to proceed
 - **Use source priority**: Codebase → Docs → Source → GitHub → Web
 - **Verify confidence**: Medium+ confidence required before stopping
-- **Document findings**: Write to research.md for beads, report for topics
+- **Document findings**: Write to `.opencode/artifacts/$(cat .opencode/artifacts/.active)/research.md` or report directly
 
 ## Available Tools
 
@@ -57,17 +41,11 @@ Default depth: ~30 tool calls for moderate exploration.
 
 ## Phase 1: Load Context
 
-If argument is a bead ID:
-
-```bash
-br show $ARGUMENTS
-```
-
-Read PRD if it exists and extract questions that need answering.
+Read `.opencode/artifacts/$(cat .opencode/artifacts/.active)/spec.md` if it exists and extract questions that need answering.
 
 ### Memory Search (Required)
 
-Follow the [memory-grounding](../skill/memory-grounding/SKILL.md) skill protocol. Use findings to: skip already-answered questions, narrow scope to gaps only, avoid contradicting prior decisions without justification.
+Search memory for existing findings. Use them to: skip already-answered questions, narrow scope to gaps only, avoid contradicting prior decisions without justification.
 
 ## Phase 2: Research
 
@@ -102,7 +80,7 @@ Follow the [memory-grounding](../skill/memory-grounding/SKILL.md) skill protocol
 
 ## Phase 4: Document
 
-Write findings to `.beads/artifacts/$ARGUMENTS/research.md` (if bead) or report directly (if topic):
+Write findings to `.opencode/artifacts/$(cat .opencode/artifacts/.active)/research.md` (if plan exists) or report directly (if topic):
 
 - Questions asked → answered/partial/unanswered with confidence
 - Key findings with sources (file paths, docs)