opencodekit 0.6.7 → 0.8.0

package/dist/template/.opencode/skill/using-git-worktrees/SKILL.md

@@ -27,23 +27,23 @@ ls -d worktrees 2>/dev/null      # Alternative
 
 **If found:** Use that directory. If both exist, `.worktrees` wins.
 
-### 2. Check CLAUDE.md
+### 2. Check AGENTS.md
 
 ```bash
-grep -i "worktree.*director" CLAUDE.md 2>/dev/null
+grep -i "worktree.*director" AGENTS.md 2>/dev/null
 ```
 
 **If preference specified:** Use it without asking.
 
 ### 3. Ask User
 
-If no directory exists and no CLAUDE.md preference:
+If no directory exists and no AGENTS.md preference:
 
 ```
 No worktree directory found. Where should I create worktrees?
 
 1. .worktrees/ (project-local, hidden)
-2. ~/.config/superpowers/worktrees/<project-name>/ (global location)
+2. ~/.opencode/worktrees/<project-name>/ (global location)
 
 Which would you prefer?
 ```
@@ -62,13 +62,14 @@ grep -q "^\.worktrees/$" .gitignore || grep -q "^worktrees/$" .gitignore
 **If NOT in .gitignore:**
 
 Per Jesse's rule "Fix broken things immediately":
+
 1. Add appropriate line to .gitignore
 2. Commit the change
 3. Proceed with worktree creation
 
 **Why critical:** Prevents accidentally committing worktree contents to repository.
 
-### For Global Directory (~/.config/superpowers/worktrees)
+### For Global Directory (~/.opencode/worktrees)
 
 No .gitignore verification needed - outside project entirely.
 
@@ -88,8 +89,8 @@ case $LOCATION in
   .worktrees|worktrees)
     path="$LOCATION/$BRANCH_NAME"
     ;;
-  ~/.config/superpowers/worktrees/*)
-    path="~/.config/superpowers/worktrees/$project/$BRANCH_NAME"
+  ~/.opencode/worktrees/*)
+    path="~/.opencode/worktrees/$project/$BRANCH_NAME"
     ;;
 esac
 
@@ -143,31 +144,35 @@ Ready to implement <feature-name>
 
 ## Quick Reference
 
-| Situation | Action |
-|-----------|--------|
-| `.worktrees/` exists | Use it (verify .gitignore) |
-| `worktrees/` exists | Use it (verify .gitignore) |
-| Both exist | Use `.worktrees/` |
-| Neither exists | Check CLAUDE.md → Ask user |
+| Situation                   | Action                      |
+| --------------------------- | --------------------------- |
+| `.worktrees/` exists        | Use it (verify .gitignore)  |
+| `worktrees/` exists         | Use it (verify .gitignore)  |
+| Both exist                  | Use `.worktrees/`           |
+| Neither exists              | Check AGENTS.md → Ask user  |
 | Directory not in .gitignore | Add it immediately + commit |
-| Tests fail during baseline | Report failures + ask |
-| No package.json/Cargo.toml | Skip dependency install |
+| Tests fail during baseline  | Report failures + ask       |
+| No package.json/Cargo.toml  | Skip dependency install     |
 
 ## Common Mistakes
 
 **Skipping .gitignore verification**
+
 - **Problem:** Worktree contents get tracked, pollute git status
 - **Fix:** Always grep .gitignore before creating project-local worktree
 
 **Assuming directory location**
+
 - **Problem:** Creates inconsistency, violates project conventions
-- **Fix:** Follow priority: existing > CLAUDE.md > ask
+- **Fix:** Follow priority: existing > AGENTS.md > ask
 
 **Proceeding with failing tests**
+
 - **Problem:** Can't distinguish new bugs from pre-existing issues
 - **Fix:** Report failures, get explicit permission to proceed
 
 **Hardcoding setup commands**
+
 - **Problem:** Breaks on projects using different tools
 - **Fix:** Auto-detect from project files (package.json, etc.)
 
@@ -190,14 +195,16 @@ Ready to implement auth feature
 ## Red Flags
 
 **Never:**
+
 - Create worktree without .gitignore verification (project-local)
 - Skip baseline test verification
 - Proceed with failing tests without asking
 - Assume directory location when ambiguous
-- Skip CLAUDE.md check
+- Skip AGENTS.md check
 
 **Always:**
-- Follow directory priority: existing > CLAUDE.md > ask
+
+- Follow directory priority: existing > AGENTS.md > ask
 - Verify .gitignore for project-local
 - Auto-detect and run project setup
 - Verify clean test baseline
@@ -205,9 +212,11 @@ Ready to implement auth feature
 ## Integration
 
 **Called by:**
+
 - **brainstorming** (Phase 4) - REQUIRED when design is approved and implementation follows
 - Any skill needing isolated workspace
 
 **Pairs with:**
+
 - **finishing-a-development-branch** - REQUIRED for cleanup after work complete
 - **executing-plans** or **subagent-driven-development** - Work happens in this worktree

package/dist/template/.opencode/skill/{using-superpowers → using-skills}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: using-superpowers
+name: using-skills
 description: Use when starting any conversation - establishes mandatory workflows for finding and using skills, including using Skill tool before announcing usage, following brainstorming before coding, and creating TodoWrite todos for checklists
 ---
 
@@ -53,6 +53,7 @@ If a skill for your task exists, you must use it or you will fail at your task.
 If a skill has a checklist, YOU MUST create TodoWrite todos for EACH item.
 
 **Don't:**
+
 - Work through checklist mentally
 - Skip creating todos "to save time"
 - Batch multiple items into one todo
@@ -66,6 +67,7 @@ Before using a skill, announce that you are using it.
 "I'm using [Skill Name] to [what you're doing]."
 
 **Examples:**
+
 - "I'm using the brainstorming skill to refine your idea into a design."
 - "I'm using the test-driven-development skill to implement this feature."
 
@@ -92,9 +94,10 @@ Your human partner's specific instructions describe WHAT to do, not HOW.
 ## Summary
 
 **Starting any task:**
+
 1. If relevant skill exists → Use the skill
-3. Announce you're using it
-4. Follow what it says
+2. Announce you're using it
+3. Follow what it says
 
 **Skill has checklist?** TodoWrite for every item.
 

package/dist/template/.opencode/skill/writing-plans/SKILL.md

@@ -34,7 +34,7 @@ Assume they are a skilled developer, but know almost nothing about our toolset o
 ```markdown
 # [Feature Name] Implementation Plan
 
-> **For Claude:** REQUIRED SUB-SKILL: Use use_skill("executing-plans") to implement this plan task-by-task.
+> **For Claude:** REQUIRED SUB-SKILL: Use skill({ name: "executing-plans" }) to implement this plan task-by-task.
 
 **Goal:** [One sentence describing what this builds]
 
@@ -111,11 +111,11 @@ After saving the plan, offer execution choice:
 **Which approach?"**
 
 **If Subagent-Driven chosen:**
-- **REQUIRED SUB-SKILL:** Use use_skill("subagent-driven-development")
+- **REQUIRED SUB-SKILL:** Use skill({ name: "subagent-driven-development" })
 - Stay in this session
 - Fresh subagent per task + code review
 
 **If Parallel Session chosen:**
 - Guide them to open new session in worktree
-- **REQUIRED SUB-SKILL:** New session uses use_skill("executing-plans")
+- **REQUIRED SUB-SKILL:** New session uses skill({ name: "executing-plans" })
 ```

package/dist/template/.opencode/skill/writing-skills/SKILL.md

@@ -282,7 +282,7 @@ wc -w skills/path/SKILL.md
 
 Use skill name only, with explicit requirement markers:
 
-- ✅ Good: `**REQUIRED SUB-SKILL:** Use use_skill("test-driven-development")`
+- ✅ Good: `**REQUIRED SUB-SKILL:** Use skill({ name: "test-driven-development" })`
 - ✅ Good: `**REQUIRED BACKGROUND:** You MUST understand systematic-debugging`
 - ❌ Bad: `See skills/testing/test-driven-development` (unclear if required)
 - ❌ Bad: `@skills/testing/test-driven-development/SKILL.md` (force-loads, burns context)
@@ -568,7 +568,7 @@ Run same scenarios WITH skill. Agent should now comply.
 
 Agent found new rationalization? Add explicit counter. Re-test until bulletproof.
 
-**REQUIRED SUB-SKILL:** Use use_skill("testing-skills-with-subagents") for the complete testing methodology:
+**REQUIRED SUB-SKILL:** Use skill({ name: "testing-skills-with-subagents" }) for the complete testing methodology:
 
 - How to write pressure scenarios
 - Pressure types (time, sunk cost, authority, exhaustion)

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "opencodekit",
-	"version": "0.6.7",
+	"version": "0.8.0",
 	"description": "CLI tool for bootstrapping and managing OpenCodeKit projects",
 	"type": "module",
 	"repository": {
@@ -35,6 +35,7 @@
 	"dependencies": {
 		"@clack/prompts": "^0.7.0",
 		"@opencode-ai/plugin": "^1.0.141",
+		"beads-village": "^1.3.3",
 		"cac": "^6.7.14",
 		"cli-table3": "^0.6.5",
 		"ora": "^9.0.0",

package/dist/template/.opencode/memory/handoffs/2025-12-27T103000Z.md

@@ -1,76 +0,0 @@
-# Handoff: test-handoff-plugin
-
-**Created:** 2025-12-27T10:30:00Z
-**Agent:** build
-
-## Provenance
-
-| Key    | Value                                               |
-| ------ | --------------------------------------------------- |
-| Repo   | git@github.com:opencodekit/opencodekit-template.git |
-| Branch | main                                                |
-| Commit | ae38a95f899300419e9b17030268cedc60ebb44f            |
-| Clean  | no                                                  |
-
-## Session Context
-
-**Current Session:** testing handoff plugin
-**Token Usage:** ~50k estimated
-
-Next session can load context with:
-
-```
-read_session("last", project="current")
-```
-
-## Progress
-
-### Completed
-
-- [x] Released v0.6.4 (version bump, changelog, tag, GitHub release)
-- [x] Reviewed Agent-Skills-for-Context-Engineering repo (verdict: mostly theory, not worth stealing)
-- [x] Reviewed Karpathy's hn-time-capsule (verdict: useful patterns)
-- [x] Created handoff plugin (`plugin/handoff.ts`)
-- [x] Updated `/handoff` command to instruct Ctrl+K
-
-### In Progress
-
-- [ ] Testing handoff plugin - verifying it injects context on compaction
-
-### Remaining
-
-- [ ] Commit new handoff plugin and updated command
-- [ ] Test full flow: handoff → Ctrl+K → new session with context
-
-## Context
-
-### Key Files
-
-- `.opencode/plugin/handoff.ts` - New plugin that injects handoff on compaction
-- `.opencode/command/handoff.md` - Updated to tell user to press Ctrl+K
-- `.opencode/plugin/compactor.ts` - Reference for plugin structure
-
-### Decisions Made
-
-- Use `experimental.session.compacting` hook to inject handoff context
-- Only inject handoffs < 1 hour old to prevent stale context
-- Search both `.opencode/memory/handoffs/` and `.beads/artifacts/` for handoffs
-
-### Blockers/Issues
-
-- OpenCode lacks `session.start` hook (Issue #5409) - can't auto-navigate to new session
-- Workaround: User must manually press Ctrl+K after /handoff
-
-## Resume Instructions
-
-1. Commit the new handoff plugin and updated command
-2. Test the full flow: run /handoff, press Ctrl+K, verify context injected
-3. If working, consider adding to v0.6.5 release
-
-**Recommended:** Start next session with `/resume test-handoff-plugin` to auto-load this handoff + previous session context.
-
-## Artifacts
-
-- spec.md: missing
-- research.md: missing
-- plan.md: missing

package/dist/template/.opencode/plugin/skill.ts

@@ -1,275 +0,0 @@
-/**
- * Skills plugin for OpenCode.ai
- *
- * Provides custom tools for loading and discovering skills.
- * Skills are loaded on-demand via use_skill tool, not auto-injected.
- *
- * OpenCode Official Skill Locations:
- * - Project skills: .opencode/skill/
- * - Personal skills: ~/.opencode/skill/
- */
-
-import fs from "fs";
-import os from "os";
-import path from "path";
-import { type Plugin, tool } from "@opencode-ai/plugin";
-
-interface SkillResolution {
-  skillFile: string;
-  sourceType: "project" | "personal";
-  skillPath: string;
-}
-
-interface SkillInfo {
-  path: string;
-  skillFile: string;
-  name: string;
-  description: string;
-  sourceType: "project" | "personal";
-}
-
-interface Frontmatter {
-  name: string;
-  description: string;
-}
-
-// ============================================
-// Skills Core Functions
-// ============================================
-
-function extractFrontmatter(filePath: string): Frontmatter {
-  try {
-    const content = fs.readFileSync(filePath, "utf8");
-    const lines = content.split("\n");
-
-    let inFrontmatter = false;
-    let name = "";
-    let description = "";
-
-    for (const line of lines) {
-      if (line.trim() === "---") {
-        if (inFrontmatter) break;
-        inFrontmatter = true;
-        continue;
-      }
-
-      if (inFrontmatter) {
-        const match = line.match(/^(\w+):\s*(.*)$/);
-        if (match) {
-          const [, key, value] = match;
-          if (key === "name") name = value.trim();
-          if (key === "description") description = value.trim();
-        }
-      }
-    }
-
-    return { name, description };
-  } catch {
-    return { name: "", description: "" };
-  }
-}
-
-function findSkillsInDir(
-  dir: string,
-  sourceType: "project" | "personal",
-  maxDepth = 3,
-): SkillInfo[] {
-  const skills: SkillInfo[] = [];
-
-  if (!fs.existsSync(dir)) return skills;
-
-  function recurse(currentDir: string, depth: number) {
-    if (depth > maxDepth) return;
-
-    const entries = fs.readdirSync(currentDir, { withFileTypes: true });
-
-    for (const entry of entries) {
-      const fullPath = path.join(currentDir, entry.name);
-
-      if (entry.isDirectory()) {
-        const skillFile = path.join(fullPath, "SKILL.md");
-        if (fs.existsSync(skillFile)) {
-          const { name, description } = extractFrontmatter(skillFile);
-          skills.push({
-            path: fullPath,
-            skillFile,
-            name: name || entry.name,
-            description: description || "",
-            sourceType,
-          });
-        }
-        recurse(fullPath, depth + 1);
-      }
-    }
-  }
-
-  recurse(dir, 0);
-  return skills;
-}
-
-function stripFrontmatter(content: string): string {
-  const lines = content.split("\n");
-  let inFrontmatter = false;
-  let frontmatterEnded = false;
-  const contentLines: string[] = [];
-
-  for (const line of lines) {
-    if (line.trim() === "---") {
-      if (inFrontmatter) {
-        frontmatterEnded = true;
-        continue;
-      }
-      inFrontmatter = true;
-      continue;
-    }
-
-    if (frontmatterEnded || !inFrontmatter) {
-      contentLines.push(line);
-    }
-  }
-
-  return contentLines.join("\n").trim();
-}
-
-// ============================================
-// Plugin Export
-// ============================================
-
-export const SkillsPlugin: Plugin = async ({ client, directory }) => {
-  const homeDir = os.homedir();
-  const projectSkillsDir = path.join(directory, ".opencode/skill");
-  const personalSkillsDir = path.join(homeDir, ".opencode/skill");
-
-  return {
-    tool: {
-      use_skill: tool({
-        description:
-          "Load and read a specific skill to guide your work. Skills contain proven workflows, mandatory processes, and expert techniques.",
-        args: {
-          skill_name: tool.schema
-            .string()
-            .describe(
-              'Name of skill to load (e.g., "brainstorming", "my-custom-skill", or "project:my-skill")',
-            ),
-        },
-        execute: async (
-          args: { skill_name: string },
-          context: { sessionID: string },
-        ) => {
-          const { skill_name } = args;
-
-          // Resolve with priority: project > personal
-          const forceProject = skill_name.startsWith("project:");
-          const actualSkillName = forceProject
-            ? skill_name.replace(/^project:/, "")
-            : skill_name;
-
-          let resolved: SkillResolution | null = null;
-
-          // Try project skills first
-          if (forceProject) {
-            const projectSkillFile = path.join(
-              projectSkillsDir,
-              actualSkillName,
-              "SKILL.md",
-            );
-            if (fs.existsSync(projectSkillFile)) {
-              resolved = {
-                skillFile: projectSkillFile,
-                sourceType: "project",
-                skillPath: actualSkillName,
-              };
-            }
-          }
-
-          // Fall back to personal resolution
-          if (!resolved && !forceProject) {
-            const personalSkillFile = path.join(
-              personalSkillsDir,
-              skill_name,
-              "SKILL.md",
-            );
-            if (fs.existsSync(personalSkillFile)) {
-              resolved = {
-                skillFile: personalSkillFile,
-                sourceType: "personal",
-                skillPath: skill_name,
-              };
-            }
-          }
-
-          if (!resolved) {
-            return `Error: Skill "${skill_name}" not found.\n\nRun find_skills to see available skills.`;
-          }
-
-          const fullContent = fs.readFileSync(resolved.skillFile, "utf8");
-          const { name, description } = extractFrontmatter(resolved.skillFile);
-          const content = stripFrontmatter(fullContent);
-          const skillDirectory = path.dirname(resolved.skillFile);
-
-          const skillHeader = `# ${name || skill_name}
-# ${description || ""}
-# Supporting tools and docs are in ${skillDirectory}
-# ============================================`;
-
-          // Insert as user message with noReply for persistence across compaction
-          try {
-            await client.session.prompt({
-              path: { id: context.sessionID },
-              body: {
-                noReply: true,
-                parts: [
-                  {
-                    type: "text",
-                    text: `Loading skill: ${name || skill_name}`,
-                  },
-                  { type: "text", text: `${skillHeader}\n\n${content}` },
-                ],
-              },
-            });
-          } catch {
-            // Fallback: return content directly if message insertion fails
-            return `${skillHeader}\n\n${content}`;
-          }
-
-          return `Launching skill: ${name || skill_name}`;
-        },
-      }),
-
-      find_skills: tool({
-        description:
-          "List all available skills in project and personal skill libraries.",
-        args: {},
-        execute: async () => {
-          const projectSkills = findSkillsInDir(projectSkillsDir, "project", 3);
-          const personalSkills = findSkillsInDir(
-            personalSkillsDir,
-            "personal",
-            3,
-          );
-
-          const allSkills = [...projectSkills, ...personalSkills];
-
-          if (allSkills.length === 0) {
-            return `No skills found. Add project skills to .opencode/skill/ or personal skills to ~/.opencode/skill/`;
-          }
-
-          let output = "Available skills:\n\n";
-
-          for (const skill of allSkills) {
-            const namespace = skill.sourceType === "project" ? "project:" : "";
-            const skillName = skill.name || path.basename(skill.path);
-
-            output += `${namespace}${skillName}\n`;
-            if (skill.description) {
-              output += `  ${skill.description}\n`;
-            }
-            output += `  Directory: ${skill.path}\n\n`;
-          }
-
-          return output;
-        },
-      }),
-    },
-  };
-};

package/dist/template/.opencode/skill/systematic-debugging/CREATION-LOG.md

@@ -1,119 +0,0 @@
-# Creation Log: Systematic Debugging Skill
-
-Reference example of extracting, structuring, and bulletproofing a critical skill.
-
-## Source Material
-
-Extracted debugging framework from `/Users/jesse/.claude/CLAUDE.md`:
-- 4-phase systematic process (Investigation → Pattern Analysis → Hypothesis → Implementation)
-- Core mandate: ALWAYS find root cause, NEVER fix symptoms
-- Rules designed to resist time pressure and rationalization
-
-## Extraction Decisions
-
-**What to include:**
-- Complete 4-phase framework with all rules
-- Anti-shortcuts ("NEVER fix symptom", "STOP and re-analyze")
-- Pressure-resistant language ("even if faster", "even if I seem in a hurry")
-- Concrete steps for each phase
-
-**What to leave out:**
-- Project-specific context
-- Repetitive variations of same rule
-- Narrative explanations (condensed to principles)
-
-## Structure Following skill-creation/SKILL.md
-
-1. **Rich when_to_use** - Included symptoms and anti-patterns
-2. **Type: technique** - Concrete process with steps
-3. **Keywords** - "root cause", "symptom", "workaround", "debugging", "investigation"
-4. **Flowchart** - Decision point for "fix failed" → re-analyze vs add more fixes
-5. **Phase-by-phase breakdown** - Scannable checklist format
-6. **Anti-patterns section** - What NOT to do (critical for this skill)
-
-## Bulletproofing Elements
-
-Framework designed to resist rationalization under pressure:
-
-### Language Choices
-- "ALWAYS" / "NEVER" (not "should" / "try to")
-- "even if faster" / "even if I seem in a hurry"
-- "STOP and re-analyze" (explicit pause)
-- "Don't skip past" (catches the actual behavior)
-
-### Structural Defenses
-- **Phase 1 required** - Can't skip to implementation
-- **Single hypothesis rule** - Forces thinking, prevents shotgun fixes
-- **Explicit failure mode** - "IF your first fix doesn't work" with mandatory action
-- **Anti-patterns section** - Shows exactly what shortcuts look like
-
-### Redundancy
-- Root cause mandate in overview + when_to_use + Phase 1 + implementation rules
-- "NEVER fix symptom" appears 4 times in different contexts
-- Each phase has explicit "don't skip" guidance
-
-## Testing Approach
-
-Created 4 validation tests following skills/meta/testing-skills-with-subagents:
-
-### Test 1: Academic Context (No Pressure)
-- Simple bug, no time pressure
-- **Result:** Perfect compliance, complete investigation
-
-### Test 2: Time Pressure + Obvious Quick Fix
-- User "in a hurry", symptom fix looks easy
-- **Result:** Resisted shortcut, followed full process, found real root cause
-
-### Test 3: Complex System + Uncertainty
-- Multi-layer failure, unclear if can find root cause
-- **Result:** Systematic investigation, traced through all layers, found source
-
-### Test 4: Failed First Fix
-- Hypothesis doesn't work, temptation to add more fixes
-- **Result:** Stopped, re-analyzed, formed new hypothesis (no shotgun)
-
-**All tests passed.** No rationalizations found.
-
-## Iterations
-
-### Initial Version
-- Complete 4-phase framework
-- Anti-patterns section
-- Flowchart for "fix failed" decision
-
-### Enhancement 1: TDD Reference
-- Added link to skills/testing/test-driven-development
-- Note explaining TDD's "simplest code" ≠ debugging's "root cause"
-- Prevents confusion between methodologies
-
-## Final Outcome
-
-Bulletproof skill that:
-- ✅ Clearly mandates root cause investigation
-- ✅ Resists time pressure rationalization
-- ✅ Provides concrete steps for each phase
-- ✅ Shows anti-patterns explicitly
-- ✅ Tested under multiple pressure scenarios
-- ✅ Clarifies relationship to TDD
-- ✅ Ready for use
-
-## Key Insight
-
-**Most important bulletproofing:** Anti-patterns section showing exact shortcuts that feel justified in the moment. When Claude thinks "I'll just add this one quick fix", seeing that exact pattern listed as wrong creates cognitive friction.
-
-## Usage Example
-
-When encountering a bug:
-1. Load skill: skills/debugging/systematic-debugging
-2. Read overview (10 sec) - reminded of mandate
-3. Follow Phase 1 checklist - forced investigation
-4. If tempted to skip - see anti-pattern, stop
-5. Complete all phases - root cause found
-
-**Time investment:** 5-10 minutes
-**Time saved:** Hours of symptom-whack-a-mole
-
----
-
-*Created: 2025-10-03*
-*Purpose: Reference example for skill extraction and bulletproofing*