fix: claude agents install

Author: davidlee

.agents/skills/dispatch

@@ -0,0 +1 @@
+../../.spec-driver/skills/dispatch

.agents/skills/sub-driver

@@ -0,0 +1 @@
+../../.spec-driver/skills/sub-driver

.pi/extensions/spec-driver-artifact-events.ts

@@ -16,9 +16,7 @@
  *       supekku/claude.hooks/artifact_event.py (_ARTIFACT_PATTERNS)
  *       see mem.artifact-pattern-sync
  */
-import type {
-  ExtensionFactory,
-} from "@mariozechner/pi-coding-agent";
+import type { ExtensionFactory } from "@mariozechner/pi-coding-agent";
 import { spawnSync } from "node:child_process";
 import { appendFileSync, mkdirSync } from "node:fs";
 import { join, relative } from "node:path";

.spec-driver/AGENTS.md

@@ -6,17 +6,15 @@
 When users ask you to perform tasks, check if any of the available skills below can help complete the task more effectively. Skills provide specialized capabilities and domain knowledge.
 
 How to use skills:
-
 - Check available skills in <available_skills> below
 - Skills are loaded via slash commands or agent tooling
 - Each skill contains detailed instructions for completing specific tasks
 
 Usage notes:
-
 - Only use skills listed in <available_skills> below
 - Do not invoke a skill that is already loaded in your context
 - Each skill invocation is stateless
-  </usage>
+</usage>
 
 <available_skills>
 
@@ -56,6 +54,12 @@ Usage notes:
 <location>project</location>
 </skill>
 
+<skill>
+<name>dispatch</name>
+<description>Orchestrate parallel implementation via sub-agents. Reads an IP's phase/task structure, analyses parallelism, batches tasks by token budget, routes to appropriate models (sonnet/opus), and dispatches workers in isolated worktrees. Use instead of /execute-phase when a phase has parallelizable work.</description>
+<location>project</location>
+</skill>
+
 <skill>
 <name>doctrine</name>
 <description>Understand project governance to avoid spreading heresy. you</description>
@@ -140,6 +144,12 @@ Usage notes:
 <location>project</location>
 </skill>
 
+<skill>
+<name>sub-driver</name>
+<description>Lightweight spec-driver fluency for dispatch workers. Provides the minimum vocabulary, commands, and boundaries needed to navigate a spec-driver project without full boot ceremony. Loaded via skills: frontmatter in dispatch-worker agent definition.</description>
+<location>project</location>
+</skill>
+
 <skill>
 <name>update-delta-docs</name>
 <description>Reconcile DE/IP/phase/DR execution artefacts during delta work. Use this when implementation changes structured execution state, not just notes.</description>

.spec-driver/deltas/DE-133-installer_support_for_claude_agents_agent_sync_pipeline/workflow/state.yaml

@@ -0,0 +1,21 @@
+schema: supekku.workflow.state
+version: 1
+artifact:
+  id: DE-133
+  kind: delta
+  path: .spec-driver/deltas/DE-133-installer_support_for_claude_agents_agent_sync_pipeline
+  notes_path: .spec-driver/deltas/DE-133-installer_support_for_claude_agents_agent_sync_pipeline/notes.md
+phase:
+  id: IP-133.PHASE-01
+  status: in_progress
+  path: .spec-driver/deltas/DE-133-installer_support_for_claude_agents_agent_sync_pipeline/phases/phase-01.md
+workflow:
+  status: implementing
+  active_role: implementer
+  handoff_boundary: phase
+timestamps:
+  created: '2026-04-17T02:00:51+00:00'
+  updated: '2026-04-17T02:00:51+00:00'
+plan:
+  id: IP-133
+  path: .spec-driver/deltas/DE-133-installer_support_for_claude_agents_agent_sync_pipeline/IP-133.md

.spec-driver/skills/boot/SKILL.md

@@ -11,7 +11,7 @@ checking for the "Spec-Driver Boot Context" heading. If you cannot find
 it, warn the user:
 
 > ⚠ Preboot context not found. Run `uv run spec-driver admin preboot`
-> and ensure `.claude/rules/spec-driver-boot.md` symlink exists.
+> and ensure `.agents/spec-driver-boot.md` symlink exists.
 
 When boot context has been observed — print:
 Δ ∴ ⊤

.spec-driver/skills/capturing-memory/SKILL.md

@@ -1,12 +1,13 @@
 ---
 name: capturing-memory
 description: |
-  Invoke this skill whenever any of the following occurs during work: (1) you discover or confirm a durable fact, constraint, invariant, or “how we do X here” pattern; (2) you create a new workflow/checklist that will be reused; (3) you resolve a recurring confusion (“where is the source of truth?”); (4) you make a decision that is not an ADR/SPEC but would prevent rework; (5) you detect a sharp edge, footgun, or non-obvious dependency that future agents will hit; (6) you complete an implementation phase or are closing a delta
+  Invoke this skill whenever any of the following occurs during work: (1) you discover or confirm a durable fact, constraint, invariant, or “how we do X here” pattern; (2) you create a new workflow/checklist that will be reused; (3) you resolve a recurring confusion (“where is the source of truth?”); (4) you make a decision that is not an ADR/SPEC but would prevent rework; (5) you detect a sharp edge, footgun, or non-obvious dependency that future agents will hit.
   Do NOT rely on conversational context to persist. When the information would save ≥10 minutes for a future agent, write a memory record immediately.
 ---
 
-Before treating a phase, task, or delta as closed, scan the current notes,
-artefacts, and your recent experience for durable guidance worth preserving.
+Phase and delta wrap-up are mandatory prompts for this skill. Before treating a
+phase, task, or delta as wrapped, scan the current notes, phase sheet, audit
+findings, and any fresh gotchas for durable guidance worth preserving.
 
 Procedure:
 

.spec-driver/skills/capturing-memory/tile.json

@@ -15,7 +15,7 @@ Inputs:
 Process:
 
 1. Pre-check:
-   - Phase/IP criteria complete; phase frontmatter statuses are `completed`
+   - Phase/IP criteria complete
    - Specs patched to match contracts + audit findings
    - Relevant verification coverage statuses updated (typically `verified` where required)
    - Inspect the delta for originating backlog entries; if any exist, decide what closure update each needs before the delta is completed

.spec-driver/skills/close-change/SKILL.md

@@ -40,9 +40,8 @@ uv run spec-driver create handoff <DELTA-ID> --to <role>
 Where `<role>` is the appropriate next role (e.g. `reviewer`, `implementer`,
 `architect`).
 
-If you are completing a phase, use `phase complete` instead — it updates the
-phase sheet frontmatter to `completed`, marks state.yaml, and emits a handoff
-automatically:
+If you are completing a phase, use `phase complete` instead — it marks the
+phase done and emits a handoff automatically:
 
 ```
 uv run spec-driver phase complete <DELTA-ID>