cokit-cli 1.2.7 → 1.4.0

package/skills/ck-docs-seeker/workflows/library-search.md

@@ -0,0 +1,87 @@
+# General Library Documentation Search
+
+**Use when:** User asks about entire library/framework
+
+**Speed:** ⚡⚡ Moderate (30-60s)
+**Token usage:** 🟡 Medium
+**Accuracy:** 📚 Comprehensive
+
+## Trigger Patterns
+
+- "Documentation for [LIBRARY]"
+- "[LIBRARY] getting started"
+- "How to use [LIBRARY]"
+- "[LIBRARY] API reference"
+
+## Workflow (Script-First)
+
+```bash
+# STEP 1: Execute detect-topic.js script
+node scripts/detect-topic.js "<user query>"
+# Returns: {"isTopicSpecific": false} for general queries
+
+# STEP 2: Execute fetch-docs.js script (handles URL construction)
+node scripts/fetch-docs.js "<user query>"
+# Script constructs context7.com URL automatically
+# Script handles GitHub/website URL patterns
+# Returns: llms.txt content with 5-20+ URLs
+
+# STEP 3: Execute analyze-llms-txt.js script
+cat llms.txt | node scripts/analyze-llms-txt.js -
+# Groups URLs: critical, important, supplementary
+# Recommends: agent distribution strategy
+# Returns: {totalUrls, grouped, distribution}
+
+# STEP 4: Deploy agents based on script recommendation
+# - 1-3 URLs: Single agent or direct WebFetch
+# - 4-10 URLs: Deploy 3-5 Explorer agents
+# - 11+ URLs: Deploy 7 agents or phased approach
+
+# STEP 5: Aggregate and present
+# Synthesize findings: installation, concepts, API, examples
+```
+
+## Examples
+
+**Astro framework:**
+```bash
+# Execute scripts (no manual URL construction)
+node scripts/detect-topic.js "Documentation for Astro"
+# {"isTopicSpecific": false}
+
+node scripts/fetch-docs.js "Documentation for Astro"
+# Script fetches: context7.com/withastro/astro/llms.txt
+# Returns: llms.txt with 8 URLs
+
+node scripts/analyze-llms-txt.js < llms.txt
+# {totalUrls: 8, distribution: "3-agents", grouped: {...}}
+
+# Deploy 3 Explorer agents as recommended:
+# Agent 1: Getting started, installation, setup
+# Agent 2: Core concepts, components, layouts
+# Agent 3: Configuration, API reference
+
+# Aggregate and present comprehensive report
+```
+
+## Agent Distribution
+
+**1-3 URLs:** Single agent
+**4-10 URLs:** 3-5 agents (2-3 URLs each)
+**11-20 URLs:** 7 agents (balanced)
+**21+ URLs:** Two-phase (critical first, then important)
+
+## Known Libraries
+
+- Next.js: `vercel/next.js`
+- Astro: `withastro/astro`
+- Remix: `remix-run/remix`
+- shadcn/ui: `shadcn-ui/ui`
+- Better Auth: `better-auth/better-auth`
+
+## Fallback
+
+Scripts handle fallback automatically:
+1. `fetch-docs.js` tries context7.com
+2. If 404, script suggests WebSearch for llms.txt
+3. If still unavailable: [Repository Analysis](./repo-analysis.md)

package/skills/ck-fix/SKILL.md

@@ -0,0 +1,209 @@
+---
+name: ck-fix
+description: "ALWAYS activate this skill before fixing ANY bug, error, test failure, CI/CD issue, type error, lint, log error, UI issue, code problem."
+argument-hint: "[issue] --auto|--review|--quick|--parallel"
+---
+
+# Fixing
+
+Unified skill for fixing issues of any complexity with intelligent routing.
+
+## Arguments
+
+- `--auto` - Activate autonomous mode (**default**)
+- `--review` - Activate human-in-the-loop review mode
+- `--quick` - Activate quick mode
+- `--parallel` - Activate parallel mode: route to parallel `ck-fullstack-developer` agents per issue
+
+<HARD-GATE>
+Do NOT propose or implement fixes before completing Steps 1-2 (Scout + Diagnose).
+Symptom fixes are failure. Find the cause first through structured analysis, NEVER guessing.
+If 3+ fix attempts fail, STOP and question the architecture — discuss with user before attempting more.
+User override: `--quick` mode allows fast scout→diagnose→fix cycle for trivial issues (lint, type errors).
+</HARD-GATE>
+
+## Anti-Rationalization
+
+| Thought | Reality |
+|---------|---------|
+| "I can see the problem, let me fix it" | Seeing symptoms ≠ understanding root cause. Scout first. |
+| "Quick fix for now, investigate later" | "Later" never comes. Fix properly now. |
+| "Just try changing X" | Random fixes waste time and create new bugs. Diagnose first. |
+| "It's probably X" | "Probably" = guessing. Use structured diagnosis. Verify first. |
+| "One more fix attempt" (after 2+) | 3+ failures = wrong approach. Question architecture. |
+| "Emergency, no time for process" | Systematic diagnosis is FASTER than guess-and-check. |
+| "I already know the codebase" | Knowledge decays. Scout to verify assumptions before acting. |
+| "The fix is done, tests pass" | Without prevention, same bug class will recur. Add guards. |
+
+## Process Flow (Authoritative)
+
+```mermaid
+flowchart TD
+    A[Issue Input] --> B[Step 0: Mode Selection]
+    B --> C[Step 1: Scout - Understand Context]
+    C --> D[Step 2: Diagnose - Structured Root Cause Analysis]
+    D --> E[Step 3: Complexity Assessment + Task Orchestration]
+    E -->|Simple| F[Quick Workflow]
+    E -->|Moderate| G[Standard Workflow]
+    E -->|Complex| H[Deep Workflow]
+    E -->|Parallel| I[Multi-Agent Fix]
+    F --> J[Step 4: Fix Implementation]
+    G --> J
+    H --> J
+    I --> J
+    J --> K[Step 5: Verify + Prevent]
+    K -->|Pass + Prevention in place| L[Step 6: Finalize]
+    K -->|Fail, <3 attempts| D
+    K -->|Fail, 3+ attempts| M[Question Architecture]
+    M --> N[Discuss with User]
+    L --> O[Report + Docs + Journal]
+```
+
+**This diagram is the authoritative workflow.** If prose conflicts with this flow, follow the diagram.
+
+## Workflow
+
+### Step 0: Mode Selection
+
+**First action:** If there is no "auto" keyword in the request, ask the user to determine workflow mode:
+
+| Option | Recommend When | Behavior |
+|--------|----------------|----------|
+| **Autonomous** (default) | Simple/moderate issues | Auto-approve if score >= 9.5 & 0 critical |
+| **Human-in-the-loop Review** | Critical/production code | Pause for approval at each step |
+| **Quick** | Type errors, lint, trivial bugs | Fast scout → diagnose → fix → review cycle |
+
+See `references/mode-selection.md` for asking the user format.
+
+### Step 1: Scout (MANDATORY — never skip)
+
+**Purpose:** Understand the affected codebase BEFORE forming any hypotheses.
+
+**Mandatory skill chain:**
+1. Activate `ck-scout` skill OR launch 2-3 parallel `Explore` subagents
+2. Discover: affected files, dependencies, related tests, recent changes (`git log`)
+3. Read `./docs` for project context if unfamiliar
+
+**Quick mode:** Minimal scout — locate affected file(s) and their direct dependencies only.
+**Standard/Deep mode:** Full scout — map module boundaries, test coverage, call chains.
+
+**Output:** `✓ Step 1: Scouted - [N] files mapped, [M] dependencies, [K] tests found`
+
+### Step 2: Diagnose (MANDATORY — never skip)
+
+**Purpose:** Structured root cause analysis. NO guessing. Evidence-based only.
+
+**Mandatory skill chain:**
+1. **Capture pre-fix state:** Record exact error messages, failing test output, stack traces, log snippets. This becomes the baseline for Step 5 verification.
+2. Activate `ck-debug` skill (systematic-debugging + root-cause-tracing techniques).
+3. Activate `ck-sequential-thinking` skill — form hypotheses through structured reasoning, NOT guessing.
+4. Spawn parallel `Explore` subagents to test each hypothesis against codebase evidence.
+5. If 2+ hypotheses fail → auto-activate `ck-problem-solving` skill for alternative approaches.
+6. Create diagnosis report: confirmed root cause, evidence chain, affected scope.
+
+See `references/diagnosis-protocol.md` for full methodology.
+
+**Output:** `✓ Step 2: Diagnosed - Root cause: [summary], Evidence: [brief], Scope: [N files]`
+
+### Step 3: Complexity Assessment & Task Orchestration
+
+Classify before routing. See `references/complexity-assessment.md`.
+
+| Level | Indicators | Workflow |
+|-------|------------|----------|
+| **Simple** | Single file, clear error, type/lint | `references/workflow-quick.md` |
+| **Moderate** | Multi-file, root cause unclear | `references/workflow-standard.md` |
+| **Complex** | System-wide, architecture impact | `references/workflow-deep.md` |
+| **Parallel** | 2+ independent issues OR `--parallel` flag | Parallel `ck-fullstack-developer` agents |
+
+**Task Orchestration (Moderate+ only):** After classifying, create native Tasks for all phases upfront with dependencies. See `references/task-orchestration.md`.
+- Skip for Quick workflow (< 3 steps, overhead exceeds benefit)
+- Use `TaskCreate` with `addBlockedBy` for dependency chains
+- Update via `TaskUpdate` as each phase completes
+- For Parallel: create separate task trees per independent issue
+- **Fallback:** Task tools (`TaskCreate`/`TaskUpdate`/`TaskGet`/`TaskList`) are CLI-only — unavailable in VSCode extension. If they error, use `TodoWrite` for progress tracking. Fix workflow remains fully functional without them.
+
+### Step 4: Fix Implementation
+
+- Implement fix per selected workflow, updating Tasks as phases complete.
+- Follow diagnosis findings — fix the ROOT CAUSE, not symptoms.
+- Minimal changes only. Follow existing patterns.
+
+### Step 5: Verify + Prevent (MANDATORY — never skip)
+
+**Purpose:** Prove the fix works AND prevent the same bug class from recurring.
+
+**Mandatory skill chain:**
+1. **Verify (iron-law):** Run the EXACT commands from pre-fix state capture. Compare output. NO claims without fresh evidence.
+2. **Regression test:** Add or update test(s) that specifically cover the fixed issue. The test MUST fail without the fix and pass with it.
+3. **Prevention gate:** Apply defense-in-depth validation where applicable. See `references/prevention-gate.md`.
+4. **Parallel verification:** Launch `Bash` agents for typecheck + lint + build + test.
+
+**If verification fails:** Loop back to Step 2 (re-diagnose). After 3 failures → question architecture, discuss with user.
+
+See `references/prevention-gate.md` for prevention requirements.
+
+**Output:** `✓ Step 5: Verified + Prevented - [before/after comparison], [N] tests added, [M] guards added`
+
+### Step 6: Finalize (MANDATORY — never skip)
+
+1. Report summary: confidence score, root cause, changes, files, prevention measures
+2. `ck-docs-manager` subagent → update `./docs` if changes warrant (NON-OPTIONAL)
+3. `TaskUpdate` → mark ALL Tasks `completed` (skip if Task tools unavailable)
+4. Ask user if they want to commit via `ck-git-manager` subagent
+5. Run `/ck-journal` to write a concise technical journal entry upon completion
+
+---
+
+## IMPORTANT: Skill/Subagent Activation Matrix
+
+See `references/skill-activation-matrix.md` for complete matrix.
+
+**Always activate (ALL workflows):**
+- `ck-scout` (Step 1) — understand before diagnosing
+- `ck-debug` (Step 2) — systematic root cause investigation
+- `ck-sequential-thinking` (Step 2) — structured hypothesis formation
+
+**Conditional:**
+- `ck-problem-solving` — auto-triggers when 2+ hypotheses fail in Step 2
+- `brainstorm` — multiple valid approaches, architecture decision (Deep only)
+- `ck-context-engineering` — fixing AI/LLM/agent code
+- `project-management` — moderate+ for task hydration/sync-back
+
+**Subagents:** `ck-debugger`, `ck-researcher`, `ck-planner`, `ck-code-reviewer`, `ck-tester`, `Bash`
+**Parallel:** Multiple `Explore` agents for scouting, `Bash` agents for verification
+
+## Output Format
+
+Unified step markers:
+```
+✓ Step 0: [Mode] selected
+✓ Step 1: Scouted - [N] files, [M] deps
+✓ Step 2: Diagnosed - Root cause: [summary]
+✓ Step 3: [Complexity] detected - [workflow] selected
+✓ Step 4: Fixed - [N] files changed
+✓ Step 5: Verified + Prevented - [tests added], [guards added]
+✓ Step 6: Complete - [action taken]
+```
+
+## References
+
+Load as needed:
+- `references/mode-selection.md` - asking the user format for mode
+- `references/diagnosis-protocol.md` - Structured diagnosis methodology (NEW)
+- `references/prevention-gate.md` - Prevention requirements after fix (NEW)
+- `references/complexity-assessment.md` - Classification criteria
+- `references/task-orchestration.md` - Native Task patterns for moderate+ workflows
+- `references/workflow-quick.md` - Quick: scout → diagnose → fix → verify+prevent → review
+- `references/workflow-standard.md` - Standard: full pipeline with Tasks
+- `references/workflow-deep.md` - Deep: research + brainstorm + plan with Tasks
+- `references/review-cycle.md` - Review logic (autonomous vs HITL)
+- `references/skill-activation-matrix.md` - When to activate each skill
+- `references/parallel-exploration.md` - Parallel Explore/Bash/Task coordination patterns
+
+**Specialized Workflows:**
+- `references/workflow-ci.md` - GitHub Actions/CI failures
+- `references/workflow-logs.md` - Application log analysis
+- `references/workflow-test.md` - Test suite failures
+- `references/workflow-types.md` - TypeScript type errors
+- `references/workflow-ui.md` - Visual/UI issues (requires design skills)

package/skills/ck-fix/references/complexity-assessment.md

@@ -0,0 +1,73 @@
+# Complexity Assessment
+
+Classify issue complexity before routing to workflow. Assessment happens AFTER Step 1 (Scout) and Step 2 (Diagnose).
+
+## Classification Criteria
+
+### Simple (→ workflow-quick.md) — No Tasks
+
+**Indicators:**
+- Single file affected
+- Clear error message (type error, syntax, lint)
+- Keywords: `type`, `typescript`, `tsc`, `lint`, `eslint`, `syntax`
+- Obvious fix location
+- Root cause confirmed by diagnosis (not assumed)
+
+**Task usage:** Skip. < 3 steps, overhead exceeds benefit.
+
+**Examples:**
+- "Fix type error in auth.ts"
+- "ESLint errors after upgrade"
+- "Syntax error in config file"
+
+### Moderate (→ workflow-standard.md) — Use Tasks (6 phases)
+
+**Indicators:**
+- 2-5 files affected
+- Root cause identified but fix spans multiple files
+- Needs investigation to confirm diagnosis
+- Keywords: `bug`, `broken`, `not working`, `fails sometimes`
+- Test failures with root cause traced
+
+**Task usage:** Create 6 phase tasks with dependencies. See `references/task-orchestration.md`.
+
+**Examples:**
+- "Login sometimes fails"
+- "API returns wrong data"
+- "Component not rendering correctly"
+
+### Complex (→ workflow-deep.md) — Use Tasks with Dependency Chains (9 phases)
+
+**Indicators:**
+- System-wide impact (5+ files)
+- Architecture decision needed
+- Research required for solution
+- Keywords: `architecture`, `refactor`, `system-wide`, `design issue`
+- Performance/security vulnerabilities
+- Multiple interacting components
+- Root cause spans multiple layers/modules
+
+**Task usage:** Create 9 phase tasks. Steps 1+2+3 run parallel (scout+diagnose+research). Full dependency chains. See `references/task-orchestration.md`.
+
+**Examples:**
+- "Memory leak in production"
+- "Database deadlocks under load"
+- "Security vulnerability in auth flow"
+
+### Parallel (→ multiple fullstack-developer agents) — Use Task Trees
+
+**Triggers:**
+- `--parallel` flag explicitly passed (activate parallel routing regardless of auto-classification)
+
+**Indicators:**
+- 2+ independent issues mentioned
+- Issues in different areas (frontend + backend, auth + payments)
+- No dependencies between issues
+- Keywords: list of issues, "and", "also", multiple error types
+
+**Task usage:** Create separate task trees per independent issue (each with scout+diagnose+fix+verify). Spawn `ck-fullstack-developer` agent per tree. See `references/task-orchestration.md`.
+
+**Examples:**
+- "Fix type errors AND update UI styling"
+- "Auth bug + payment integration issue"
+- "3 different test failures in unrelated modules"

package/skills/ck-fix/references/diagnosis-protocol.md

@@ -0,0 +1,133 @@
+# Diagnosis Protocol
+
+Structured root cause analysis methodology. Replaces ad-hoc guessing with evidence-based investigation.
+
+## Core Principle
+
+**NEVER guess root causes.** Form hypotheses through structured reasoning and test them against evidence.
+
+## Pre-Diagnosis: Capture State (MANDATORY)
+
+Before any investigation, capture the current broken state as baseline:
+
+```
+1. Record exact error messages (copy-paste, not paraphrase)
+2. Record failing test output (full command + output)
+3. Record relevant stack traces
+4. Record relevant log snippets with timestamps
+5. Record git status / recent changes: git log --oneline -10
+```
+
+This baseline is required for Step 5 (Verify) — you MUST compare before/after.
+
+## Diagnosis Chain (Follow in Order)
+
+### Phase 1: Observe — What is actually happening?
+
+Read, don't assume. Use `ck-debug` (systematic-debugging Phase 1).
+
+- What is the exact error message?
+- Where does it occur? (file, line, function)
+- When did it start? (check `git log`, `git bisect`)
+- Can it be reproduced consistently?
+- What is the expected vs actual behavior?
+
+### Phase 2: Hypothesize — Why might this happen?
+
+Activate `ck-sequential-thinking` skill. Form hypotheses through structured reasoning.
+
+**Structured hypothesis formation:**
+```
+For each hypothesis:
+  1. State the hypothesis clearly
+  2. What evidence would CONFIRM it?
+  3. What evidence would REFUTE it?
+  4. How to test it quickly?
+```
+
+**Common hypothesis categories:**
+- Recent code change introduced regression (`git log`, `git diff`)
+- Data/state mismatch (wrong input, stale cache, race condition)
+- Environment difference (deps version, config, platform)
+- Missing validation (null check, type guard, boundary)
+- Incorrect assumption (API contract, data shape, ordering)
+
+### Phase 3: Test — Verify hypotheses against evidence
+
+Spawn parallel `Explore` subagents to test each hypothesis simultaneously:
+
+```
+// Launch in SINGLE message — max 3 parallel agents
+Task("Explore", "Test hypothesis A: [specific search/check]", "Verify H-A")
+Task("Explore", "Test hypothesis B: [specific search/check]", "Verify H-B")
+Task("Explore", "Test hypothesis C: [specific search/check]", "Verify H-C")
+```
+
+**For each hypothesis result:**
+- CONFIRMED: Evidence supports this as root cause → proceed to root cause tracing
+- REFUTED: Evidence contradicts → discard, note why
+- INCONCLUSIVE: Need more data → refine hypothesis or gather more evidence
+
+### Phase 4: Trace — Follow the root cause chain
+
+Use `ck-debug` (root-cause-tracing technique). Trace backward:
+
+```
+Symptom (where error appears)
+  ↑ Immediate cause (what triggered the error)
+    ↑ Contributing factor (what set up the bad state)
+      ↑ ROOT CAUSE (the original trigger that must be fixed)
+```
+
+**Rule:** NEVER fix where the error appears. Trace back to the source.
+
+### Phase 5: Escalate — When hypotheses fail
+
+If 2+ hypotheses are REFUTED:
+1. Auto-activate `ck-problem-solving` skill
+2. Apply Inversion Exercise: "What would CAUSE this bug intentionally?"
+3. Apply Scale Game: "Does this fail with 1 item? 100? 10000?"
+4. Consider environmental factors (timing, concurrency, platform)
+
+If 3+ fix attempts fail after diagnosis:
+1. STOP immediately
+2. Question the architecture — is the design fundamentally flawed?
+3. Discuss with user before attempting more
+
+## Diagnosis Report Format
+
+```markdown
+## Diagnosis Report
+
+**Issue:** [one-line description]
+**Pre-fix state captured:** Yes/No
+
+### Root Cause
+[Clear explanation of the root cause, traced back to origin]
+
+### Evidence Chain
+1. [Observation] → led to hypothesis [X]
+2. [Test result] → confirmed/refuted [X]
+3. [Trace] → root cause at [file:line]
+
+### Affected Scope
+- Files: [list]
+- Functions: [list]
+- Dependencies: [list]
+
+### Recommended Fix
+[What to change and why — addressing root cause, not symptoms]
+
+### Prevention Needed
+[What guards/tests to add to prevent recurrence]
+```
+
+## Quick Mode Diagnosis
+
+For trivial issues (type errors, lint, syntax), abbreviated diagnosis:
+
+1. Read error message
+2. Locate affected file(s) via scout results
+3. Identify root cause (usually obvious for simple issues)
+4. Skip parallel hypothesis testing
+5. Still capture pre-fix state for verification

package/skills/ck-fix/references/mode-selection.md

@@ -0,0 +1,46 @@
+# Mode Selection
+
+Use asking the user at start of fixing workflow.
+
+## asking the user Format
+
+```json
+{
+  "questions": [{
+    "question": "How should I handle the fix workflow?",
+    "header": "Fix Mode",
+    "options": [
+      {
+        "label": "Autonomous (Recommended)",
+        "description": "Auto-approve if quality high, only ask when stuck"
+      },
+      {
+        "label": "Human-in-the-loop",
+        "description": "Pause for approval at each major step"
+      },
+      {
+        "label": "Quick fix",
+        "description": "Fast debug-fix-review cycle for simple issues"
+      }
+    ],
+    "multiSelect": false
+  }]
+}
+```
+
+## Mode Recommendations
+
+| Issue Type | Recommended Mode |
+|------------|------------------|
+| Type errors, lint errors | Quick |
+| Single file bugs | Quick or Autonomous |
+| Multi-file, unclear root cause | Autonomous |
+| Production/critical code | Human-in-the-loop |
+| System-wide/architecture | Human-in-the-loop |
+| Security vulnerabilities | Human-in-the-loop |
+
+## Skip Mode Selection When
+
+- Issue is clearly trivial (type error keyword detected) → default Quick
+- User explicitly specified mode in prompt
+- Previous context already established mode

package/skills/ck-fix/references/parallel-exploration.md

@@ -0,0 +1,100 @@
+# Parallel Exploration
+
+Patterns for launching multiple subagents in parallel to scout codebase, verify implementation, and coordinate via native Tasks.
+
+## Parallel Exploration (Scouting)
+
+Launch multiple `Explore` subagents simultaneously when needing to find:
+- Related files across different areas
+- Similar implementations/patterns
+- Dependencies and usage
+
+**Pattern:**
+```
+Task(subagent_type="Explore", prompt="Find [X] in [area1]", description="Scout area1")
+Task(subagent_type="Explore", prompt="Find [Y] in [area2]", description="Scout area2")
+Task(subagent_type="Explore", prompt="Find [Z] in [area3]", description="Scout area3")
+```
+
+**Example - Multi-area scouting:**
+```
+// Launch in SINGLE message with multiple Task calls:
+Task("Explore", "Find auth-related files in src/", "Scout auth")
+Task("Explore", "Find API routes handling users", "Scout API")
+Task("Explore", "Find test files for auth module", "Scout tests")
+```
+
+## Parallel Verification (Bash)
+
+Launch multiple `Bash` subagents to verify implementation from different angles.
+
+**Pattern:**
+```
+Task(subagent_type="Bash", prompt="Run [command1]", description="Verify X")
+Task(subagent_type="Bash", prompt="Run [command2]", description="Verify Y")
+```
+
+**Example - Multi-verification:**
+```
+// Launch in SINGLE message:
+Task("Bash", "Run typecheck: bun run typecheck", "Verify types")
+Task("Bash", "Run lint: bun run lint", "Verify lint")
+Task("Bash", "Run build: bun run build", "Verify build")
+```
+
+## Task-Coordinated Parallel (Moderate+)
+
+For multi-phase fixes, use native Tasks to coordinate parallel agents.
+See `references/task-orchestration.md` for full patterns.
+
+**Pattern - Parallel issue trees:**
+```
+// Create separate task trees per independent issue
+T_A1 = TaskCreate(subject="[Issue A] Debug", activeForm="Debugging A")
+T_A2 = TaskCreate(subject="[Issue A] Fix",   activeForm="Fixing A",   addBlockedBy=[T_A1])
+T_B1 = TaskCreate(subject="[Issue B] Debug", activeForm="Debugging B")
+T_B2 = TaskCreate(subject="[Issue B] Fix",   activeForm="Fixing B",   addBlockedBy=[T_B1])
+T_final = TaskCreate(subject="Integration verify", addBlockedBy=[T_A2, T_B2])
+
+// Spawn agents per issue tree
+Task("fullstack-developer", "Fix Issue A. Claim tasks via TaskUpdate.", "Fix A")
+Task("fullstack-developer", "Fix Issue B. Claim tasks via TaskUpdate.", "Fix B")
+```
+
+Agents claim work via `TaskUpdate(status="in_progress")` and complete via `TaskUpdate(status="completed")`. Blocked tasks auto-unblock when dependencies resolve.
+
+## When to Use Parallel
+
+| Scenario | Parallel Strategy |
+|----------|-------------------|
+| Root cause unclear, multiple suspects | 2-3 Explore agents on different areas |
+| Multi-module fix | Explore each module in parallel |
+| After implementation | Bash agents for typecheck + lint + build |
+| Before commit | Bash agents for test + build + lint |
+| 2+ independent issues | Task trees per issue + fullstack-developer agents |
+
+## Combining Explore + Tasks + Bash
+
+**Step 1:** Parallel Explore to scout
+**Step 2:** Sequential implementation (update Tasks as phases complete)
+**Step 3:** Parallel Bash to verify
+
+```
+// Scout phase - parallel
+Task("Explore", "Find payment handlers", "Scout payments")
+Task("Explore", "Find order processors", "Scout orders")
+
+// Wait for results, implement fix, TaskUpdate each phase
+
+// Verify phase - parallel
+Task("Bash", "Run tests: bun test", "Run tests")
+Task("Bash", "Run typecheck", "Check types")
+Task("Bash", "Run build", "Verify build")
+```
+
+## Resource Limits
+
+- Max 3 parallel agents recommended (system resources)
+- Each subagent has 200K token context limit
+- Keep prompts concise to avoid context bloat
+- Use `TaskList()` to check for available unblocked work