opencodekit 0.12.2 → 0.12.4

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

@@ -1,513 +1,140 @@
 ---
-description: Create bead(s) with automatic complexity analysis and decomposition
-argument-hint: "[optional title]"
+description: Create a tracked task with spec
+argument-hint: "[title or description]"
 agent: build
 ---
 
-# Create Task
+# Create: $ARGUMENTS
 
-## Load Beads Skill
+You're creating a new tracked task. Keep it simple unless complexity demands otherwise.
 
-```typescript
-skill({ name: "beads" });
-```
-
-This skill provides the full beads workflow including Epic → Task → Subtask hierarchy.
-
-## Phase 1: Check for Similar Work
-
-Before creating, search for existing or past work:
-
-```typescript
-memory_search({ query: "[keywords from title/problem]", type: "observations" });
-bd_ls({ status: "all", limit: 20, offset: 0 });
-```
-
-If similar task exists:
-
-- Link as dependency, or
-- Extend existing task, or
-- Confirm this is intentionally separate
-
-## Phase 2: Interview
-
-**If title provided:** Use `$ARGUMENTS` as starting point.
-
-**If no title:** Ask in one message:
-
-1. "What problem are we solving?"
-2. "Bug, feature, or task?"
-3. "What's the acceptance criteria?"
-4. "Any constraints or 'never do X' rules?"
-5. "Related existing code or past work?"
-
-Keep it brief. Get: clear goal, success criteria, scope, constraints.
-
-## Phase 3: Complexity Analysis
-
-Analyze the request to determine if it should be a single bead or decomposed:
-
-### Complexity Signals
-
-```
-SIMPLE (Single Bead)                    COMPLEX (Needs Decomposition)
-━━━━━━━━━━━━━━━━━━━━                    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-• Single file change                    • Multiple unrelated files
-• One clear action                      • Multiple distinct actions
-• ~30 min or less                       • Hours/days of work
-• No phases needed                      • Has natural phases
-• One skill domain                      • Crosses domains (FE + BE)
-• Bug fix or small feature              • New system or major feature
-```
-
-### Automatic Classification
-
-```typescript
-const analyzeComplexity = (request: string) => {
-  const signals = {
-    // COMPLEX signals
-    multiDomain: /frontend.*backend|api.*ui|database.*interface/i,
-    multiPhase: /first.*then|phase|step \d|after.*before/i,
-    largeScope: /system|architecture|refactor.*entire|redesign/i,
-    multiComponent: /and.*and|multiple|several|all.*components/i,
-    integration: /integrate|connect|sync.*between/i,
-
-    // SIMPLE signals
-    singleAction: /fix|update|add|remove|change.*one/i,
-    bugFix: /bug|error|broken|not working|crash/i,
-    smallScope: /typo|config|env|readme|comment/i,
-  };
-
-  let complexScore = 0;
-  if (signals.multiDomain.test(request)) complexScore += 3;
-  if (signals.multiPhase.test(request)) complexScore += 2;
-  if (signals.largeScope.test(request)) complexScore += 3;
-  if (signals.multiComponent.test(request)) complexScore += 2;
-  if (signals.integration.test(request)) complexScore += 2;
-
-  let simpleScore = 0;
-  if (signals.singleAction.test(request)) simpleScore += 2;
-  if (signals.bugFix.test(request)) simpleScore += 1;
-  if (signals.smallScope.test(request)) simpleScore += 3;
-
-  return complexScore > simpleScore + 2 ? "COMPLEX" : "SIMPLE";
-};
-```
-
-### Decision Point
-
-```
-COMPLEXITY ANALYSIS
-━━━━━━━━━━━━━━━━━━━
-
-Request: "[user's request]"
-
-Signals detected:
-✓ Multiple domains (frontend + backend)
-✓ Multi-phase work (setup → implement → test)
-✓ Integration required
+## Check For Duplicates First
 
-Classification: COMPLEX
-
-Recommendation: Create Epic with 3-4 subtasks
-
-Options:
-1. [Recommended] Create Epic + decompose into subtasks
-2. Create single bead (override complexity detection)
-3. Let me clarify scope first
-
-Choose (1/2/3): _
+```bash
+bd list --status=all | grep -i "[keywords]"
 ```
 
-**STOP and wait for user confirmation.**
-
-## Phase 4A: Simple Path (Single Bead)
-
-If SIMPLE or user overrides:
-
-### Type & Priority
-
-- **Type**: bug | feature | task | chore
-- **Priority**: 0 (critical) to 4 (low), default 2
-
-### Create Single Bead
-
-```typescript
-bd_add({
-  title: "[title]",
-  type: "[type]",
-  pri: [priority],
-  desc: "[description]",
-  tags: ["[role]", "[estimate]"],
-});
-```
-
-### Create Spec
-
-Write `.beads/artifacts/<bead-id>/spec.md` (see Standard Spec template below).
-
-**Continue to Phase 6.**
-
-## Phase 4B: Complex Path (Epic + Subtasks)
+If similar work exists, link to it or extend it instead of creating duplicate.
 
-If COMPLEX and user confirms decomposition:
+## Gather Requirements
 
-### Step 1: Identify Natural Breakdown
+If `$ARGUMENTS` is clear, use it directly. If vague, ask:
 
-```
-DECOMPOSITION ANALYSIS
-━━━━━━━━━━━━━━━━━━━━━━
-
-Request: "Add user authentication with OAuth"
+1. What problem are we solving?
+2. Bug, feature, or task?
+3. What's the acceptance criteria?
+4. Any constraints?
 
-Natural breakdown:
+Keep it brief. Don't over-engineer the interview.
 
-1. Database & Schema [Backend]
-   - User table, sessions table
-   - Can start immediately
+## Assess Complexity
 
-2. OAuth Provider Integration [Backend]
-   - Google, GitHub providers
-   - Depends on: #1
+**Simple** (single bead): One file, one clear action, ~30 min or less
+**Complex** (needs decomposition): Multiple domains, natural phases, hours of work
 
-3. Auth API Endpoints [Backend]
-   - Login, logout, refresh
-   - Depends on: #1, #2
+If complex, ask: "This looks like it needs decomposition. Create an epic with subtasks?"
 
-4. Frontend Auth Flow [Frontend]
-   - Login page, protected routes
-   - Depends on: #3
+## Create The Bead
 
-5. Testing & Documentation [QA]
-   - E2E tests, API docs
-   - Depends on: #3, #4
+Simple task:
 
-Parallel execution possible:
-- Track A: #1 → #2 → #3
-- Track B: #4 (can start after #3 ready)
-- Track C: #5 (final)
-
-Create this structure? (yes/modify)
+```bash
+bd create "[title]" -t task -p 2
 ```
 
-**STOP and wait for user confirmation.**
-
-### Step 2: Create Epic
+Bug:
 
-```typescript
-const epic = bd_add({
-  title: "[Feature Name]",
-  type: "epic",
-  pri: [priority],
-  desc: "[Overview of the feature]",
-  tags: ["epic", "[domain]"],
-});
-// Returns: { id: "bd-a3f8" }
+```bash
+bd create "[title]" -t bug -p 1
 ```
 
-### Step 3: Create Child Tasks with Dependencies
+Feature:
 
-```typescript
-// Task 1: No dependencies (can start immediately)
-const task1 = bd_add({
-  title: "Database schema for auth",
-  type: "task",
-  pri: 2,
-  parent: "bd-a3f8", // Links to epic
-  desc: "Create user and session tables",
-  tags: ["backend", "database", "S"],
-});
-// Returns: { id: "bd-a3f8.1" }
-
-// Task 2: Depends on Task 1
-const task2 = bd_add({
-  title: "OAuth provider integration",
-  type: "task",
-  pri: 2,
-  parent: "bd-a3f8",
-  deps: ["bd-a3f8.1"], // Blocked by task 1
-  desc: "Integrate Google and GitHub OAuth",
-  tags: ["backend", "M"],
-});
-// Returns: { id: "bd-a3f8.2" }
-
-// Task 3: Depends on Tasks 1 and 2
-const task3 = bd_add({
-  title: "Auth API endpoints",
-  type: "task",
-  pri: 2,
-  parent: "bd-a3f8",
-  deps: ["bd-a3f8.1", "bd-a3f8.2"],
-  desc: "Login, logout, refresh endpoints",
-  tags: ["backend", "api", "M"],
-});
-// Returns: { id: "bd-a3f8.3" }
-
-// Task 4: Depends on Task 3 (different domain - can be parallel agent)
-const task4 = bd_add({
-  title: "Frontend auth flow",
-  type: "task",
-  pri: 2,
-  parent: "bd-a3f8",
-  deps: ["bd-a3f8.3"],
-  desc: "Login page, protected routes, auth context",
-  tags: ["frontend", "M"],
-});
-// Returns: { id: "bd-a3f8.4" }
-
-// Task 5: Final task
-const task5 = bd_add({
-  title: "Auth testing and docs",
-  type: "task",
-  pri: 3,
-  parent: "bd-a3f8",
-  deps: ["bd-a3f8.3", "bd-a3f8.4"],
-  desc: "E2E tests and API documentation",
-  tags: ["qa", "docs", "S"],
-});
-// Returns: { id: "bd-a3f8.5" }
+```bash
+bd create "[title]" -t feature -p 2
 ```
 
-### Step 4: Visualize Dependency Graph
+Epic (if decomposing):
 
-```
-DEPENDENCY GRAPH: bd-a3f8 "User Authentication"
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-bd-a3f8.1 [Database] ────┬────► bd-a3f8.2 [OAuth] ────┐
-     (ready)             │           │                │
-                         │           ▼                │
-                         └────► bd-a3f8.3 [API] ◄─────┘
-                                     │
-                    ┌────────────────┼────────────────┐
-                    ▼                                 ▼
-             bd-a3f8.4 [Frontend]              bd-a3f8.5 [Testing]
-                    │                                 ▲
-                    └─────────────────────────────────┘
-
-READY NOW: bd-a3f8.1 (no blockers)
-BLOCKED:   bd-a3f8.2, bd-a3f8.3, bd-a3f8.4, bd-a3f8.5
+```bash
+bd create "[title]" -t epic -p 1
 ```
 
-## Phase 5: Create Spec for Epic
+## Create Spec
 
-Write `.beads/artifacts/<epic-id>/spec.md`:
+Write `.beads/artifacts/<bead-id>/spec.md`:
 
 ```markdown
-# [Feature Name]
+# [Title]
 
-**Epic:** <epic-id>
+**Bead:** <bead-id>
 **Created:** [date]
-**Status:** In Progress
-**Complexity:** XL (decomposed into [N] subtasks)
 
 ## Goal
 
-[1-2 sentences: What exactly are we building and why?]
-
-## Subtasks
-
-| ID       | Title             | Status  | Depends On | Assignee |
-| -------- | ----------------- | ------- | ---------- | -------- |
-| <epic>.1 | Database schema   | Ready   | -          | backend  |
-| <epic>.2 | OAuth integration | Blocked | .1         | backend  |
-| <epic>.3 | API endpoints     | Blocked | .1, .2     | backend  |
-| <epic>.4 | Frontend flow     | Blocked | .3         | frontend |
-| <epic>.5 | Testing & docs    | Blocked | .3, .4     | qa       |
-
-## Parallel Execution
-
-Agents can work in parallel on:
-
-- **After .1 completes:** .2 can start
-- **After .3 completes:** .4 and .5 can start in parallel
+[1-2 sentences: What and why]
 
 ## Success Criteria
 
-- [ ] All subtasks completed
-- [ ] Integration tests passing
-- [ ] [Specific acceptance criterion]
+- [ ] [Criterion 1]
+  - Verify: `[command]`
+- [ ] [Criterion 2]
   - Verify: `[command]`
 
 ## Constraints
 
-**Must:**
-
-- [Required constraint]
-
-**Never:**
-
-- [Anti-pattern or forbidden action]
+**Must:** [required]
+**Never:** [forbidden]
 
 ## Notes
 
-[Additional context]
+[context if needed]
 ```
 
-## Phase 6: Spec Quality Check
-
-Before presenting, verify:
-
-- [ ] **Testable criteria?** Each success criterion has a verification command
-- [ ] **Constraints explicit?** "Must" and "Never" rules documented
-- [ ] **Dependencies correct?** Graph makes sense, no cycles
-- [ ] **Scope clear?** In/Out boundaries defined
-- [ ] **Parallel paths identified?** Agents can work concurrently
-
-## Phase 7: Review and Confirm
+## If Epic: Create Subtasks
 
-Present the structure for approval:
+```bash
+# First task (no blockers)
+bd create "[subtask 1]" -t task -p 2
 
+# Second task (blocked by first)
+bd create "[subtask 2]" -t task -p 2
+bd dep add bd-[second] bd-[first] --type blocks
 ```
-CREATED: [Feature Name]
-━━━━━━━━━━━━━━━━━━━━━━━
 
-Epic: bd-a3f8 "[Feature Name]"
+Visualize:
 
-Subtasks:
-├── bd-a3f8.1: Database schema [S] ← READY
-├── bd-a3f8.2: OAuth integration [M] ← blocked by .1
-├── bd-a3f8.3: API endpoints [M] ← blocked by .1, .2
-├── bd-a3f8.4: Frontend flow [M] ← blocked by .3
-└── bd-a3f8.5: Testing & docs [S] ← blocked by .3, .4
-
-Parallel Tracks:
-• Backend agent: .1 → .2 → .3
-• Frontend agent: .4 (after .3)
-• QA agent: .5 (after .3, .4)
-
-Spec: .beads/artifacts/bd-a3f8/spec.md
-
-Quality check:
-✓ Testable criteria
-✓ Dependencies valid
-✓ Parallel paths identified
-
-Approve? (yes/modify)
+```bash
+bd dep tree bd-[epic]
 ```
 
-**STOP and wait for human response.**
-
-## Phase 8: Sync & Report
+## Sync
 
 ```typescript
-bd_sync({ reason: "Created epic $ARGUMENTS with subtasks" });
-```
-
-### Next Steps by Structure
-
-**Single Bead (Simple):**
-
-```
-Next: /implement <bead-id>
+bd_sync({ reason: "Sync new bead" });
 ```
 
-**Epic with Subtasks (Complex):**
+## Output
 
 ```
-Ready to start: bd-a3f8.1 (first unblocked task)
+Created: bd-[id]
 
-Next steps:
-├── /implement bd-a3f8.1  (start first task)
-├── bd ready              (see all ready work)
-└── bd_blocked()          (see blocked tasks)
+Type: [task/bug/feature/epic]
+Priority: [0-4]
+Spec: .beads/artifacts/bd-[id]/spec.md
 
-For parallel agents:
-├── Agent 1: /implement bd-a3f8.1
-├── Agent 2: (wait for .1, then .2)
-└── Agent 3: (wait for .3, then .4)
+Next: /implement bd-[id]
 ```
 
-## Templates
-
-### Standard Spec (Simple Tasks)
-
-```markdown
-# [Title]
-
-**Bead:** <bead-id>
-**Created:** [date]
-**Status:** To Do
-**Estimate:** [S/M] (~[N] tool calls)
-
-## Goal
-
-[1-2 sentences: What exactly are we building and why?]
-
-## Scope
+If epic with subtasks:
 
-**In-Scope:**
-
-- [What we ARE doing]
-
-**Out-of-Scope:**
-
-- [What we are NOT doing]
-
-## Success Criteria
-
-- [ ] [Criterion 1]
-  - Verify: `[actual command to test this]`
-- [ ] [Criterion 2]
-  - Verify: `[actual command to test this]`
-
-## Constraints
-
-**Must:**
-
-- [Required constraint]
-
-**Never:**
-
-- [Anti-pattern or forbidden action]
-
-## Notes
-
-[Additional context]
 ```
+Created: bd-[epic] (Epic)
 
-## When to Decompose
-
-| Scenario                   | Action                               |
-| -------------------------- | ------------------------------------ |
-| Bug fix                    | Single bead                          |
-| Config change              | Single bead                          |
-| Small feature (1 file)     | Single bead                          |
-| Feature touching 2-3 files | Single bead with phases in plan      |
-| Feature crossing FE/BE     | Epic + subtasks by domain            |
-| New system/service         | Epic + subtasks by component         |
-| Refactor multiple areas    | Epic + subtasks by area              |
-| Integration work           | Epic + subtasks by integration point |
-
-## Anti-Patterns
-
-❌ **One Giant Bead**
-Creating a single bead for "Implement entire auth system" - agents lose context, can't parallelize.
-
-❌ **Too Many Tiny Beads**  
-Creating 20 beads for a simple feature - overhead exceeds value.
-
-❌ **No Dependencies**
-Creating subtasks without linking dependencies - agents don't know execution order.
-
-❌ **Missing Domain Tags**
-Not tagging with `frontend`/`backend`/`qa` - can't route to specialized agents.
-
-## Integration with Parallel Agents
-
-When epic is created with proper dependencies:
-
-```typescript
-// Agent 1 claims ready work
-bd_init({ team: "project", role: "backend" });
-bd_claim(); // Gets bd-a3f8.1 (first ready task)
-
-// Agent 1 completes, Agent 2 can now start
-bd_done({ id: "bd-a3f8.1", msg: "Schema created" });
-
-// Agent 2 claims next ready work
-bd_claim(); // Gets bd-a3f8.2 (now unblocked)
+Subtasks:
+├── bd-[epic].1: [title] ← READY
+├── bd-[epic].2: [title] ← blocked by .1
+└── bd-[epic].3: [title] ← blocked by .2
 
-// After bd-a3f8.3 completes, both .4 and .5 become ready
-// Multiple agents can work on them in parallel
+Next: /implement bd-[epic].1
 ```