From 538d65120be78ad147fc82ea392da2ed0edc4cdc Mon Sep 17 00:00:00 2001 From: Jesse Vincent Date: Tue, 4 Aug 2026 11:17:05 -0700 Subject: [PATCH] =?UTF-8?q?fix(planning):=20the=20spec=20travels=20with=20?= =?UTF-8?q?the=20plan=20=E2=80=94=20Spec:=20header=20pointer=20+=20SDD=20r?= =?UTF-8?q?eads=20it=20at=20setup?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit In controlled evals, an identical seeded-incoherence plan yielded 0-1/5 correct conflict resolutions when executed specless (controllers ruled the conflicts 'internally explained') and 4-5/5 with the spec merely present and named — even with no other skill-text changes. Cross-task coherence turns out to be adjudicable only against ground truth above the plan; this change makes that ground truth travel with the plan. Claude-Session: https://claude.ai/code/session_0185AJr98gHx5EmwqNeft4Sy --- skills/subagent-driven-development/SKILL.md | 5 ++++- skills/writing-plans/SKILL.md | 3 +++ 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/skills/subagent-driven-development/SKILL.md b/skills/subagent-driven-development/SKILL.md index 6c0b8349..be2a44e4 100644 --- a/skills/subagent-driven-development/SKILL.md +++ b/skills/subagent-driven-development/SKILL.md @@ -140,7 +140,10 @@ a ledger file, not only in todos. that happens, recover from `git log`. Read the plan once, note its context and Global Constraints, and create a -todo per task. +todo per task. If the plan names a Spec, read that too: the spec is the +authority the plan argues from, and conflicts inside the plan resolve +against it. A plan with no reachable spec gets a ledger note saying so — +rulings made without one are provisional. Before dispatching Task 1, scan the plan once for conflicts: diff --git a/skills/writing-plans/SKILL.md b/skills/writing-plans/SKILL.md index dd2702b8..f74605bf 100644 --- a/skills/writing-plans/SKILL.md +++ b/skills/writing-plans/SKILL.md @@ -66,6 +66,9 @@ independently testable deliverable. **Tech Stack:** [Key technologies/libraries] +**Spec:** [path to the spec/design doc this plan implements — the plan +argues from the spec, so the spec travels with it; executors read both] + ## Global Constraints [The spec's project-wide requirements — version floors, dependency limits,