feat: sub-agent skills

Author: davidlee

.spec-driver/backlog/improvements/IMPR-034-spec_driver_update_command/IMPR-034.md

@@ -0,0 +1,17 @@
+---
+id: IMPR-034
+name: spec-driver update command
+created: "2026-04-17"
+updated: "2026-04-17"
+status: idea
+kind: improvement
+---
+
+# spec-driver update command
+
+it'd be nice if it could figure out how to self-update depending on install method, and re-install.
+
+also: it'd be nice to make the npm install less shit / spammy when already installed.
+
+oh and rip out the skills whitelist.
+

.spec-driver/deltas/DE-132-sub_agent_orchestration_skill_for_parallel_implementation/DR-132.md

@@ -170,14 +170,16 @@ Isolation is a per-batch rule, not a judgment call:
 | Batch type | Isolation | Rationale |
 |------------|-----------|-----------|
 | Parallel, file-scope disjoint | `isolation="worktree"` | avoid concurrent-write conflicts |
-| Sequential, depends on prior batch output | omit (main tree) | must see prior work |
+| Sequential, depends on prior batch or phase work | omit (main tree) | must see prior work |
 | Single-batch phase | omit (main tree) | no merge step needed |
 
-Sequential batches *that depend on prior output* MUST NOT use
-`isolation="worktree"` — the worktree forks from a git ref at spawn time
-and cannot see uncommitted prior work (vk field evidence, §9). Independent
-batches may still use worktree isolation even in a serial ordering; the
-"depends on" clause is what forbids it.
+Sequential batches that depend on prior work MUST NOT use
+`isolation="worktree"` — regardless of whether that prior work is
+committed or in-flight. The worktree forks from a git ref at spawn time;
+even committed work can be missing from the fork if the Agent tool's
+branch point lags HEAD (vk field evidence, §9). Independent batches may
+still use worktree isolation even in a serial ordering; the "depends on"
+clause is what forbids it.
 
 **Timing model.** `Agent(isolation="worktree")` forks from the main
 branch's HEAD at the moment the Agent tool executes. Uncommitted main-tree

.spec-driver/deltas/DE-132-sub_agent_orchestration_skill_for_parallel_implementation/IP-132.md

@@ -57,12 +57,16 @@ entries:
   - artefact: VA-002
     kind: VA
     requirement: ""
-    status: planned
+    status: verified
     notes: >-
       Agent review of revised dispatch SKILL.md §6 — answers isolation-selection
       questions (sequential batch? single-batch phase? parallel batch depending
       on prior phase commit?). Guards against recurrence of the reading-level
-      ambiguity that caused the vk DE-105 incident.
+      ambiguity that caused the vk DE-105 incident. PASSED 2026-04-17 (3/3
+      correct, high confidence, clarity rated "unambiguous"); one narrow-reading
+      risk identified and resolved in the same session (row-label tightening
+      from "prior batch output" to "prior batch or phase work"). Evidence in
+      phase-03.md §9.
   - artefact: VH-003
     kind: VH
     requirement: ""

.spec-driver/deltas/DE-132-sub_agent_orchestration_skill_for_parallel_implementation/phases/phase-03.md

@@ -78,7 +78,7 @@ Wire skills into the install pipeline and verify end-to-end dispatch.
 | [ ] | 3.5 | VH-001: Parallel dispatch test | Deferred to first real use |
 | [ ] | 3.6 | VH-002: Worktree isolation test | Re-run post-amendment (§5) |
 | [ ] | 3.7 | VH-003: Model routing test | Deferred to first real use |
-| [ ] | 3.8 | VA-002: Isolation-rule literacy on revised SKILL.md | See §5 |
+| [x] | 3.8 | VA-002: Isolation-rule literacy on revised SKILL.md | Passed 2026-04-17; see §9 |
 
 ## 9. Decisions & Outcomes
 
@@ -91,6 +91,15 @@ Wire skills into the install pipeline and verify end-to-end dispatch.
   mode. DR-132 DEC-132-02 clarified (amendment log §9); SKILL.md §3/§6
   tightened; VA-002 added. VH-002 re-runs against clarified rules with
   concrete acceptance steps in §5.
+- 2026-04-17 — **VA-002 PASSED.** Sonnet agent given revised
+  `.spec-driver/skills/dispatch/SKILL.md` §3+§6 and the three test
+  questions from §5. All three answered correctly with §6.1 citations,
+  confidence=high, overall clarity rated "unambiguous". Agent flagged
+  one narrow-reading risk on the row label "depends on prior batch
+  output" — tightened the same session to "depends on prior batch or
+  phase work" with explicit note that the rule applies whether prior
+  work is committed or in-flight. Mirror in DR-132 §3.5 updated to
+  match. VH-002 still pending — requires live multi-phase dispatch.
 
 ## 11. Wrap-up Checklist
 

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

@@ -215,13 +215,16 @@ Pick isolation by batch type. This is a rule, not a judgment call:
 | Batch type | `isolation` |
 |------------|-------------|
 | Parallel, verified file-scope disjoint | `"worktree"` |
-| Sequential, depends on prior batch output | omit (main tree) |
+| Sequential, depends on prior batch or phase work | omit (main tree) |
 | Single-batch phase | omit (main tree) |
 
-Sequential batches that depend on prior output MUST NOT use
-`isolation="worktree"` — the worktree forks from a git ref and cannot see
-uncommitted prior work. Independent-but-ordered batches may use worktree
-isolation; the "depends on" clause is what forbids it.
+Sequential batches that depend on prior work MUST NOT use
+`isolation="worktree"` — regardless of whether that prior work is
+committed or in-flight. The worktree forks from a git ref at spawn
+time; even committed work can be missing from the fork if the Agent
+tool's branch point lags HEAD (the vk DE-105 failure mode).
+Independent-but-ordered batches may use worktree isolation; the
+"depends on" clause is what forbids it.
 
 **Timing.** A worktree forks from the main branch's HEAD at spawn time.
 Uncommitted main-tree changes are invisible to the worker. Therefore,

flake.lock

@@ -215,13 +215,16 @@ Pick isolation by batch type. This is a rule, not a judgment call:
 | Batch type | `isolation` |
 |------------|-------------|
 | Parallel, verified file-scope disjoint | `"worktree"` |
-| Sequential, depends on prior batch output | omit (main tree) |
+| Sequential, depends on prior batch or phase work | omit (main tree) |
 | Single-batch phase | omit (main tree) |
 
-Sequential batches that depend on prior output MUST NOT use
-`isolation="worktree"` — the worktree forks from a git ref and cannot see
-uncommitted prior work. Independent-but-ordered batches may use worktree
-isolation; the "depends on" clause is what forbids it.
+Sequential batches that depend on prior work MUST NOT use
+`isolation="worktree"` — regardless of whether that prior work is
+committed or in-flight. The worktree forks from a git ref at spawn
+time; even committed work can be missing from the fork if the Agent
+tool's branch point lags HEAD (the vk DE-105 failure mode).
+Independent-but-ordered batches may use worktree isolation; the
+"depends on" clause is what forbids it.
 
 **Timing.** A worktree forks from the main branch's HEAD at spawn time.
 Uncommitted main-tree changes are invisible to the worker. Therefore,