@hegemonart/get-design-done 1.41.5 → 1.43.0

package/skills/verify/SKILL.md

@@ -6,7 +6,7 @@ user-invocable: true
 tools: mcp__gdd_state__get, mcp__gdd_state__transition_stage, mcp__gdd_state__add_must_have, mcp__gdd_state__add_blocker, mcp__gdd_state__resolve_blocker, mcp__gdd_state__update_progress, mcp__gdd_state__set_status, mcp__gdd_state__checkpoint, mcp__gdd_state__probe_connections
 ---
 
-# Get Design Done — Verify
+# Get Design Done - Verify
 
 **Stage 5 of 5** in the get-design-done pipeline. Thin orchestrator. Verification intelligence lives in three agents: design-auditor, design-verifier, and design-integration-checker.
 
@@ -17,14 +17,14 @@ Full procedure detail: `./verify-procedure.md`.
 ## State Integration
 
 1. `mcp__gdd_state__transition_stage` with `to: "verify"`; on gate failure surface `error.context.blockers` to the user without advancing.
-2. `mcp__gdd_state__get` -> snapshot `state`. Read `state.must_haves` (verification checklist — each M-XX flips to `pass` or `fail`).
-3. **Quality-gate gate (D-08, D-09)** — inspect `state.quality_gate?.run?.status`:
+2. `mcp__gdd_state__get` -> snapshot `state`. Read `state.must_haves` (verification checklist - each M-XX flips to `pass` or `fail`).
+3. **Quality-gate gate (D-08, D-09)** - inspect `state.quality_gate?.run?.status`:
    - `"fail"` -> refuse to advance; call `mcp__gdd_state__add_blocker` with the iteration count + `commands_run`; exit. Do NOT open the stage.
    - `"timeout"` / `"skipped"` -> print one-line warning naming the status + `commands_run`, continue normally (signals, not walls).
    - `"pass"` / `null` -> continue silently.
    Full decision tree: `./verify-procedure.md` §Quality-gate gate.
-4. Resume detection — if `state.position.status==in_progress` and `.design/DESIGN-VERIFICATION.md` exists: RESUME to Step 2 (gap-response loop). Otherwise call `mcp__gdd_state__update_progress` with `task_progress: "0/3"`, `status: "in_progress"` and proceed.
-5. Missing STATE.md is a hard block — verify is never the entry point; upstream stages own bootstrap.
+4. Resume detection - if `state.position.status==in_progress` and `.design/DESIGN-VERIFICATION.md` exists: RESUME to Step 2 (gap-response loop). Otherwise call `mcp__gdd_state__update_progress` with `task_progress: "0/3"`, `status: "in_progress"` and proceed.
+5. Missing STATE.md is a hard block - verify is never the entry point; upstream stages own bootstrap.
 
 **Flipping a must-have status:** `mcp__gdd_state__add_must_have` with the SAME `id` updates in-place (no separate update tool). Detail: `./verify-procedure.md` §Flipping a must-have status.
 
@@ -45,7 +45,7 @@ Run preview / storybook / chromatic probes at stage entry, then issue ONE batche
 
 ---
 
-## Step 1 — Spawn Auditor + Verifier + Integration Checker
+## Step 1 - Spawn Auditor + Verifier + Integration Checker
 
 Initialize the fix-loop iteration counter to 0. Each full checker is preceded by a cheap Haiku gate that may return `{spawn: false}` to short-circuit (lazy-gate pattern from Plan 10.1-04 / D-21); skipped agents append `lazy_skipped: true` to `.design/telemetry/costs.jsonl`.
 
@@ -59,7 +59,7 @@ Full agent prompts, lazy-gate decision logic, and telemetry-row shapes: `./verif
 
 ---
 
-## Step 2 — Interpret Result
+## Step 2 - Interpret Result
 
 Consolidate gaps from both sources: verifier `## GAPS FOUND` (G-NN entries) and integration-checker (Orphaned -> MAJOR, Missing -> BLOCKER).
 
@@ -71,7 +71,7 @@ Detail: `./verify-procedure.md` §Step 2.
 
 ---
 
-## Step 3 — Gap Response Loop
+## Step 3 - Gap Response Loop
 
 Present the gap summary + 3-option menu (`[1] Fix now`, `[2] Save and exit`, `[3] Accept as-is`).
 
@@ -87,7 +87,7 @@ Full prompts + branching: `./verify-procedure.md` §Step 3.
 
 1. `mcp__gdd_state__update_progress` -> `task_progress: "<verified>/<total>"`, `status: "verify_complete"`.
 2. `mcp__gdd_state__set_status` -> `"pipeline_complete"` (all pass, no gaps) or `"verify_failed_requires_loop"` (gaps remain).
-3. `mcp__gdd_state__checkpoint` — stamps `last_checkpoint` and appends `verify_completed_at`. No direct STATE.md writes.
+3. `mcp__gdd_state__checkpoint` - stamps `last_checkpoint` and appends `verify_completed_at`. No direct STATE.md writes.
 
 ## After Completion
 
@@ -97,17 +97,17 @@ Print the `=== Verify complete ===` summary (status, gap counts, agent paths, ne
 Do NOT mark the cycle complete until the user has reviewed `.design/DESIGN-VERIFICATION.md`. If this project uses a custom `.design` location, read the artifact path from `.design/STATE.md` rather than assuming the default.
 </HARD-GATE>
 
-## Rationalizations — Thought to Reality
+## Rationalizations - Thought to Reality
 
 The reasons an agent gives to skip or weaken verification, and what each one lets through:
 
 | Thought | Reality |
 |---------|---------|
 | "The implementation looks right, I can skip the verifier spawn." | Skipping verification ships unchecked must-haves; the 5-phase verifier exists to catch what "looks right" misses. |
-| "The integration-checker is redundant with the auditor." | The auditor scores quality; the integration-checker proves each D-XX is actually wired — an orphaned decision passes the audit but fails the product. |
+| "The integration-checker is redundant with the auditor." | The auditor scores quality; the integration-checker proves each D-XX is actually wired - an orphaned decision passes the audit but fails the product. |
 | "These gaps are minor, I'll accept-as-is without a blocker." | Accept-as-is without recording the unresolved gaps erases the trail; the next cycle re-discovers them from scratch. |
-| "The quality gate timed out, I'll treat that as a pass." | Timeout is a signal, not a pass — masking it lets a genuinely failing gate slip through to ship. |
-| "I'll loop the fixer a fourth time to clear the last gap." | The 3-iteration cap exists because a gap surviving three fixes is a design problem, not a code problem — save and escalate. |
+| "The quality gate timed out, I'll treat that as a pass." | Timeout is a signal, not a pass - masking it lets a genuinely failing gate slip through to ship. |
+| "I'll loop the fixer a fourth time to clear the last gap." | The 3-iteration cap exists because a gap surviving three fixes is a design problem, not a code problem - save and escalate. |
 | "Post-handoff bundles don't need the faithfulness check." | Skipping the handoff-faithfulness section means a divergence from the source design ships unflagged. |
 
 ## VERIFY COMPLETE

package/skills/verify/verify-procedure.md

@@ -7,8 +7,8 @@ tags: [verify, procedure, extracted, pipeline-stage, gap-loop, must-have, qualit
 last_updated: 2026-05-18
 ---
 
-Source: extracted from `skills/verify/SKILL.md` (Phase 28.5 rework — D-10 extract-then-link).
-The skill's load-bearing workflow stays in `../skills/verify/SKILL.md`; this file holds the
+Source: extracted from `skills/verify/SKILL.md` (Phase 28.5 rework - D-10 extract-then-link).
+The skill's essential workflow stays in `../skills/verify/SKILL.md`; this file holds the
 detail the agent reaches for when executing a specific step (state integration, quality-gate
 decision tree, agent spawn protocols, gap-response loop, must-have flipping).
 
@@ -16,7 +16,7 @@ decision tree, agent spawn protocols, gap-response loop, must-have flipping).
 
 Detailed procedure for the get-design-done `verify` Stage 5 orchestrator. Companion to
 `../skills/verify/SKILL.md`. Read this file when executing a specific verify step; the
-SKILL.md keeps the load-bearing workflow + decision tree, this file holds the deep
+SKILL.md keeps the essential workflow + decision tree, this file holds the deep
 methodology, agent prompts, and gap-loop semantics.
 
 ---
@@ -26,9 +26,9 @@ methodology, agent prompts, and gap-loop semantics.
 ### Stage entry
 
 1. `mcp__gdd_state__transition_stage` with `to: "verify"`.
-2. `mcp__gdd_state__get` → snapshot `state`. Read `state.must_haves` — this is the verification checklist; each M-XX starts at `status: pending` and will be flipped to `pass` or `fail` as verification concludes.
+2. `mcp__gdd_state__get` → snapshot `state`. Read `state.must_haves` - this is the verification checklist; each M-XX starts at `status: pending` and will be flipped to `pass` or `fail` as verification concludes.
 
-#### Step 2.5 — Quality-gate gate (D-08, D-09)
+#### Step 2.5 - Quality-gate gate (D-08, D-09)
 
 Before resume detection, inspect `state.quality_gate` from the same snapshot. The Stage 4.5 quality-gate skill (see `skills/quality-gate/SKILL.md`) writes a single `<run/>` element capturing the most recent run; this step is the verify-side consumer of that result. Three branches, evaluated in order:
 
@@ -45,14 +45,14 @@ Before resume detection, inspect `state.quality_gate` from the same snapshot. Th
 
 - **`state.quality_gate?.run?.status === "timeout"` OR `=== "skipped"`** → Print a one-line warning naming the status and the `commands_run` value, then continue normally. Per D-07 these are signals, not walls: a slow test suite must not hostage the pipeline, and a project with no detectable quality commands must not block verify entry. The warning surfaces the degraded state without halting.
 
-- **`state.quality_gate?.run?.status === "pass"` OR `state.quality_gate === null`** → Continue silently. `pass` is the happy path; `null` means the gate has never been run for this cycle (the user skipped Stage 4.5 entirely, which is permitted — verify only *checks* the gate result, never *runs* the gate itself, per the 25-07 out-of-scope clause).
+- **`state.quality_gate?.run?.status === "pass"` OR `state.quality_gate === null`** → Continue silently. `pass` is the happy path; `null` means the gate has never been run for this cycle (the user skipped Stage 4.5 entirely, which is permitted - verify only *checks* the gate result, never *runs* the gate itself, per the 25-07 out-of-scope clause).
 
-This step is a pure read against the snapshot already loaded in Step 2 — no extra MCP call is required.
+This step is a pure read against the snapshot already loaded in Step 2 - no extra MCP call is required.
 
 3. Resume detection (read `state.position.status` from the snapshot):
-   - If `status==in_progress` and `.design/DESIGN-VERIFICATION.md` exists: RESUME — skip re-spawning agents, go to Step 2 (gap-response loop).
+   - If `status==in_progress` and `.design/DESIGN-VERIFICATION.md` exists: RESUME - skip re-spawning agents, go to Step 2 (gap-response loop).
    - Otherwise: call `mcp__gdd_state__update_progress` with `task_progress: "0/3"`, `status: "in_progress"` to open the stage, then proceed to Step 1.
-4. If STATE.md is missing entirely (edge case — verify is never the entry point): block with "No STATE.md found — run /get-design-done:discover first." Do NOT attempt to create a skeleton from verify; upstream stages own bootstrap.
+4. If STATE.md is missing entirely (edge case - verify is never the entry point): block with "No STATE.md found - run /get-design-done:discover first." Do NOT attempt to create a skeleton from verify; upstream stages own bootstrap.
 
 ---
 
@@ -66,7 +66,7 @@ When verification concludes that M-XX is satisfied (or failed), record the resul
 { "id": "M-03", "text": "Dark mode toggle persists to localStorage", "status": "pass" }
 ```
 
-The gdd-state mutator treats an `add_must_have` with an existing id as an **update-in-place**, not a duplicate append. The entry's position in the `<must_haves>` block is preserved. This is intentional design — verify doesn't need a dedicated `update_must_have_status` tool because `add_must_have` handles both cases correctly.
+The gdd-state mutator treats an `add_must_have` with an existing id as an **update-in-place**, not a duplicate append. The entry's position in the `<must_haves>` block is preserved. This is intentional design - verify doesn't need a dedicated `update_must_have_status` tool because `add_must_have` handles both cases correctly.
 
 Pass the original `text` verbatim when you're only flipping the status; supplying a changed `text` overwrites the prose in-place as well (useful when the M-XX description was imprecise and the verifier can restate it). Omit `text` by passing the value from the earlier `mcp__gdd_state__get` snapshot.
 
@@ -93,18 +93,18 @@ Step P2 — Live tool call:
 Record the preview probe result via `mcp__gdd_state__probe_connections` (batched with the storybook and chromatic probes below — one call per stage, see "Batched connections write" at the end of this section).
 ```
 
-When `preview: available`, the design-verifier agent runs Phase 4B — Screenshot Evidence to resolve `? VISUAL` heuristic flags with real screenshot evidence. See `agents/design-verifier.md` Phase 4B for the screenshot evidence loop.
+When `preview: available`, the design-verifier agent runs Phase 4B - Screenshot Evidence to resolve `? VISUAL` heuristic flags with real screenshot evidence. See `agents/design-verifier.md` Phase 4B for the screenshot evidence loop.
 
 ### Probe Storybook connection
 
 Run at stage entry, after reading STATE.md:
 
-Step B1 — Project detection:
+Step B1 - Project detection:
   Bash: ls .storybook/ 2>/dev/null || grep -l '"storybook"' package.json 2>/dev/null
   -> Found -> storybook_project: true -> proceed to Step B2
   -> Not found -> storybook: not_configured (skip all Storybook steps)
 
-Step B2 — Dev server detection:
+Step B2 - Dev server detection:
   Bash: curl -sf http://localhost:6006/index.json 2>/dev/null | head -1
   -> Returns JSON -> storybook: available
   -> Fails -> Bash: curl -sf http://localhost:6006/stories.json 2>/dev/null | head -1
@@ -116,23 +116,23 @@ Record the storybook probe result for the batched `mcp__gdd_state__probe_connect
 ### Storybook A11y Loop (when storybook: available)
 
 If `state.connections.storybook === "available"` (from the earlier `mcp__gdd_state__get` snapshot):
-1. Run: Bash: npx storybook test --ci 2>&1 | tee .design/storybook-a11y-report.txt
-2. Read .design/storybook-a11y-report.txt — pass to design-verifier as additional a11y evidence
+1. Run: Bash: npx storybook test `--ci` 2>&1 | tee .design/storybook-a11y-report.txt
+2. Read .design/storybook-a11y-report.txt - pass to design-verifier as additional a11y evidence
 3. design-verifier reads this file in its a11y gap analysis section and annotates DESIGN-VERIFICATION.md with per-story violations
 
-If storybook: unavailable — skip this section; run standard WCAG grep-based a11y checks only.
-If storybook: not_configured — skip; emit no note (opt-in feature).
+If storybook: unavailable - skip this section; run standard WCAG grep-based a11y checks only.
+If storybook: not_configured - skip; emit no note (opt-in feature).
 
 ### Probe Chromatic connection
 
 Run at stage entry, after reading STATE.md:
 
-Step C1 — CLI presence:
-  Bash: command -v chromatic 2>/dev/null || npx chromatic --version 2>/dev/null
+Step C1 - CLI presence:
+  Bash: command -v chromatic 2>/dev/null || npx chromatic `--version` 2>/dev/null
   -> found -> proceed to Step C2
   -> not found -> chromatic: not_configured (skip all Chromatic steps)
 
-Step C2 — Token check:
+Step C2 - Token check:
   Bash: test -n "${CHROMATIC_PROJECT_TOKEN}"
   -> true -> chromatic: available
   -> false -> chromatic: unavailable
@@ -142,7 +142,7 @@ Record the chromatic probe result for the batched `mcp__gdd_state__probe_connect
 
 ### Batched connections write
 
-After all three probes (preview, storybook, chromatic) have a verdict, call `mcp__gdd_state__probe_connections` ONCE with `probe_results` = an array of `{ name, status }` entries — one per probed connection. Example:
+After all three probes (preview, storybook, chromatic) have a verdict, call `mcp__gdd_state__probe_connections` ONCE with `probe_results` = an array of `{ name, status }` entries - one per probed connection. Example:
 
 ```json
 [
@@ -152,12 +152,12 @@ After all three probes (preview, storybook, chromatic) have a verdict, call `mcp
 ]
 ```
 
-Unspecified connections keep their existing value. Do NOT issue multiple `probe_connections` calls — the tool is designed for a single batch write per stage.
+Unspecified connections keep their existing value. Do NOT issue multiple `probe_connections` calls - the tool is designed for a single batch write per stage.
 
 ### Chromatic Visual Delta (when chromatic: available)
 
 After design executor has run (when verifying post-design):
-1. Run: Bash: npx chromatic --project-token $CHROMATIC_PROJECT_TOKEN --output json 2>&1 | tee .design/chromatic-results.json
+1. Run: Bash: npx chromatic `--project-token` $CHROMATIC_PROJECT_TOKEN `--output` json 2>&1 | tee .design/chromatic-results.json
 2. Pass .design/chromatic-results.json to design-verifier for narration (see design-verifier.md Chromatic Delta Narration section)
 If chromatic: unavailable or not_configured: skip; note in DESIGN-VERIFICATION.md "visual regression check skipped".
 
@@ -167,7 +167,7 @@ If chromatic: unavailable or not_configured: skip; note in DESIGN-VERIFICATION.m
 
 **DESIGN-PLAN.md prerequisite check:**
 - **Normal mode:** Check that `.design/DESIGN-PLAN.md` exists. If missing, block with: "Verify requires DESIGN-PLAN.md. Run `/gdd:plan` first, or use `--post-handoff` if starting from a Claude Design handoff bundle."
-- **Post-handoff mode** (`post_handoff=true` OR STATE.md `status: handoff-sourced`): Skip the DESIGN-PLAN.md check entirely — handoff workflows have no DESIGN-PLAN.md.
+- **Post-handoff mode** (`post_handoff=true` OR STATE.md `status: handoff-sourced`): Skip the DESIGN-PLAN.md check entirely - handoff workflows have no DESIGN-PLAN.md.
 
 Abort only if no `.design/` directory exists (user has not run prior stages). Output: "No .design/ directory found. Run /get-design-done:discover first."
 
@@ -196,7 +196,7 @@ Also pass post-handoff context to design-auditor: auditor skips DESIGN-PLAN.md r
 
 ---
 
-## Step 1 — Spawn Auditor + Verifier + Integration Checker
+## Step 1 - Spawn Auditor + Verifier + Integration Checker
 
 Initialize iteration counter to 0 (used for fix loop limit in Step 3).
 
@@ -230,7 +230,7 @@ Emit `## AUDIT COMPLETE` when done.
 
 Wait for `## AUDIT COMPLETE` in the agent response. Once detected, call `mcp__gdd_state__update_progress` with `task_progress: "1/3"` and a short `status` summary (e.g., `status: "audit_done"`).
 
-### 1b-gate. Lazy gate — should design-verifier run?
+### 1b-gate. Lazy gate - should design-verifier run?
 
 Spawn the cheap Haiku gate before the expensive verifier:
 
@@ -292,7 +292,7 @@ by structured gap list, then `## VERIFICATION COMPLETE`. If no gaps, just emit `
 
 Wait for `## VERIFICATION COMPLETE` in the agent response. Once detected, call `mcp__gdd_state__update_progress` with `task_progress: "2/3"` and a short `status` summary (e.g., `status: "verifier_done"`).
 
-### 1c-gate. Lazy gate — should design-integration-checker run?
+### 1c-gate. Lazy gate - should design-integration-checker run?
 
 Same pattern as 1b-gate:
 
@@ -305,7 +305,7 @@ Same pattern as 1b-gate:
     design-integration-checker should spawn.
 
     Context:
-      diff_files: <git diff --name-only output>
+      diff_files: <git diff `--name-only` output>
       diff_body: <git diff output, truncated>
       baseline_sha: <from STATE.md or HEAD~1>
 
@@ -347,7 +347,7 @@ Wait for `## INTEGRATION CHECK COMPLETE` in the agent response. Once detected, c
 
 ---
 
-## Step 2 — Interpret Result
+## Step 2 - Interpret Result
 
 Check agent responses for gaps. Gaps come from two sources:
 - design-verifier: `## GAPS FOUND` marker in the verifier response (G-NN entries)
@@ -376,7 +376,7 @@ Merge verifier gaps (G-NN entries) and integration-checker gaps (Orphaned/Missin
 
 ---
 
-## Step 3 — Gap Response Loop
+## Step 3 - Gap Response Loop
 
 Present to the user:
 
@@ -432,7 +432,7 @@ Task("design-fixer", """
 @.design/DESIGN-CONTEXT.md
 </required_reading>
 
-Fix all BLOCKER and MAJOR gaps from ## Phase 5 — Gaps in DESIGN-VERIFICATION.md.
+Fix all BLOCKER and MAJOR gaps from ## Phase 5 - Gaps in DESIGN-VERIFICATION.md.
 For each gap: apply the targeted fix to the file/location in the gap's Location field.
 After each fix, make an atomic commit: fix(design-gap-GNN): [gap title].
 
@@ -480,9 +480,9 @@ Write updated .design/DESIGN-VERIFICATION.md. Emit ## GAPS FOUND (if any), then
 
 1. Call `mcp__gdd_state__update_progress` with `task_progress: "<verified>/<total>"` (the total is `state.must_haves.length` from the entry snapshot; verified is the count set to `pass`) and `status: "verify_complete"`.
 2. Call `mcp__gdd_state__set_status` with one of:
-   - `status: "pipeline_complete"` — all must-haves passed and no outstanding gaps.
-   - `status: "verify_failed_requires_loop"` — gaps remain (save-and-exit, accept-as-is with fails, or auto-mode blocker).
-3. Call `mcp__gdd_state__checkpoint` — stamps `frontmatter.last_checkpoint` and appends a `verify_completed_at` timestamp entry. No direct STATE.md writes; the checkpoint tool owns the final persist.
+   - `status: "pipeline_complete"` - all must-haves passed and no outstanding gaps.
+   - `status: "verify_failed_requires_loop"` - gaps remain (save-and-exit, accept-as-is with fails, or auto-mode blocker).
+3. Call `mcp__gdd_state__checkpoint` - stamps `frontmatter.last_checkpoint` and appends a `verify_completed_at` timestamp entry. No direct STATE.md writes; the checkpoint tool owns the final persist.
 
 ---
 

package/skills/warm-cache/SKILL.md

@@ -15,9 +15,9 @@ You are the Layer A cache primer. You enumerate the agent roster by scanning `ag
 
 ## Invocation Contract
 
-- **Command form**: `/gdd:warm-cache` — warms all agents that import the shared preamble.
-- **With filter**: `/gdd:warm-cache --agents design-verifier,design-planner,design-integration-checker` — warms only the named agents (comma-separated, no spaces, matches agent file basename without `.md`).
-- **Output**: a single markdown summary to stdout —
+- **Command form**: `/gdd:warm-cache` - warms all agents that import the shared preamble.
+- **With filter**: `/gdd:warm-cache --agents design-verifier,design-planner,design-integration-checker` - warms only the named agents (comma-separated, no spaces, matches agent file basename without `.md`).
+- **Output**: a single markdown summary to stdout -
   ```
   ## Warm-cache complete
   - Agents warmed: 14
@@ -25,7 +25,7 @@ You are the Layer A cache primer. You enumerate the agent roster by scanning `ag
   - Duration: 4.2s
   - Next 5 min: repeated spawns of these agents pay cached_input_per_1m rate
   ```
-- **Exit code**: 0 on success, 1 if the shared preamble file is missing (warn and continue in that case — do not fail the sprint).
+- **Exit code**: 0 on success, 1 if the shared preamble file is missing (warn and continue in that case - do not fail the sprint).
 
 ## Step-by-step Flow
 
@@ -48,7 +48,7 @@ For each kept agent, spawn the agent at tier `haiku` with an input payload desig
 No-op warm: acknowledge and return "ok". Do not read files. Do not write files. Do not emit anything beyond the two characters "ok".
 ```
 
-Spawns run serially — parallelism buys nothing here because Anthropic's prompt cache keys on prompt prefix, not on concurrent calls. Swallow spawn errors per agent (log and continue) — a single broken agent must not abort the sprint.
+Spawns run serially - parallelism buys nothing here because Anthropic's prompt cache keys on prompt prefix, not on concurrent calls. Swallow spawn errors per agent (log and continue) - a single broken agent must not abort the sprint.
 
 ### Step 4: emit summary
 
@@ -61,8 +61,8 @@ Full + filtered command-output examples live in `./../cache-manager/cache-policy
 ## Integration Points
 
 - **Pre-sprint**: `/gdd:warm-cache` is the recommended first line of a `/gdd:discover`, `/gdd:plan`, or `/gdd:verify` sprint. Users type it before the real command, or an orchestrator-level wrapper runs it automatically if `agent-metrics.json` (Plan 10.1-05) indicates the last sprint was > 5 min ago.
-- **`reference/shared-preamble.md`** (authored in Plan 10.1-04) is the load-bearing file for this command — agents import it first per D-17, which makes the first N tokens of every agent's rendered system prompt identical, which is what Anthropic's prompt cache keys on.
-- **No interaction with `hooks/budget-enforcer.js`** — the hook is a PreToolUse gate; warm-cache runs as an ordinary Agent tool call itself and is subject to the hook (each no-op Haiku ping is budgeted and logged like any other spawn). This is intentional: warm-cache's own telemetry rows in `.design/telemetry/costs.jsonl` are the evidence that cache priming happened.
+- **`reference/shared-preamble.md`** (authored in Plan 10.1-04) is the essential file for this command - agents import it first per D-17, which makes the first N tokens of every agent's rendered system prompt identical, which is what Anthropic's prompt cache keys on.
+- **No interaction with `hooks/budget-enforcer.js`** - the hook is a PreToolUse gate; warm-cache runs as an ordinary Agent tool call itself and is subject to the hook (each no-op Haiku ping is budgeted and logged like any other spawn). This is intentional: warm-cache's own telemetry rows in `.design/telemetry/costs.jsonl` are the evidence that cache priming happened.
 
 ## Cost Model
 
@@ -72,7 +72,7 @@ Full per-ping math, total-cost arithmetic for a 14-agent warm, and payback calcu
 
 - Shared preamble missing → print warning, exit 0. Sprint continues without Layer A priming.
 - Individual agent spawn fails → log, continue to next agent.
-- Budget cap hit during warm-cache (hypothetical — the total cost is trivial) → hook blocks per D-02, warm-cache surfaces the error in the summary and exits 0. User can raise cap or proceed without priming.
+- Budget cap hit during warm-cache (hypothetical - the total cost is trivial) → hook blocks per D-02, warm-cache surfaces the error in the summary and exits 0. User can raise cap or proceed without priming.
 
 ## Non-Goals
 

package/skills/watch-authorities/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: gdd-watch-authorities
-description: "Fetches the design-authority feed whitelist, diffs against .design/authority-snapshot.json, and writes .design/authority-report.md (consumed by /gdd:reflect). Authority monitoring only — no trend-watching."
+description: "Fetches the design-authority feed whitelist, diffs against .design/authority-snapshot.json, and writes .design/authority-report.md (consumed by /gdd:reflect). Authority monitoring only - no trend-watching."
 argument-hint: "[--refresh] [--since <date>] [--feed <name>] [--schedule <weekly|daily|monthly>]"
 tools: Read, Write, Task, Bash
 ---
@@ -13,11 +13,11 @@ Authority-monitoring only. Not trend-watching. See `reference/authority-feeds.md
 
 ## Steps
 
-1. **Parse args.** Extract optional flags: `--refresh`, `--since <date>`, `--feed <name>`, `--schedule <cadence>`. Anything that doesn't match one of these is an error — print `Unknown flag: <arg>. Valid flags: --refresh --since <date> --feed <name> --schedule <weekly|daily|monthly>.` and STOP.
+1. **Parse args.** Extract optional flags: `--refresh`, `--since <date>`, `--feed <name>`, `--schedule <cadence>`. Anything that doesn't match one of these is an error - print `Unknown flag: <arg>. Valid flags: --refresh --since <date> --feed <name> --schedule <weekly|daily|monthly>.` and STOP.
 
    Mutual exclusion rules:
-   - `--schedule` is handled entirely by this skill — it does not combine with the other three. If `--schedule` is present alongside any of `--refresh | --since | --feed`, print `--schedule cannot combine with other flags. Schedule registration runs this skill with no flags at the configured cadence.` and STOP.
-   - `--refresh` and `--since` are mutually exclusive — print `--refresh and --since are mutually exclusive. --refresh re-seeds the snapshot silently; --since surfaces a backlog from a boundary date. Pick one.` and STOP.
+   - `--schedule` is handled entirely by this skill - it does not combine with the other three. If `--schedule` is present alongside any of `--refresh | --since | --feed`, print `--schedule cannot combine with other flags. Schedule registration runs this skill with no flags at the configured cadence.` and STOP.
+   - `--refresh` and `--since` are mutually exclusive - print `--refresh and --since are mutually exclusive. --refresh re-seeds the snapshot silently; --since surfaces a backlog from a boundary date. Pick one.` and STOP.
 
 2. **Handle `--schedule <cadence>` branch** (early-return).
 
@@ -29,7 +29,7 @@ Authority-monitoring only. Not trend-watching. See `reference/authority-feeds.md
      ToolSearch({ query: "scheduled-tasks", max_results: 3 })
      ```
 
-   - If the probe returns an empty result set: print `scheduled-tasks MCP not connected. Install it with: claude mcp add scheduled-tasks ... then retry with --schedule.` — this is a documented fallback (not an error). Terminate with `## WATCH COMPLETE` and exit 0.
+   - If the probe returns an empty result set: print `scheduled-tasks MCP not connected. Install it with: claude mcp add scheduled-tasks ... then retry with --schedule.` - this is a documented fallback (not an error). Terminate with `## WATCH COMPLETE` and exit 0.
    - If the probe returns one or more `scheduled-tasks` tools: register the cron. Discover the MCP's registration tool name at runtime from the ToolSearch result and follow its schema. Target command: `/gdd:watch-authorities` with NO flags (the cron invokes the default diff-and-report behavior). Cadence → cron expression mapping:
      - `weekly`  → `0 9 * * 1` (Mondays 09:00 local)
      - `daily`   → `0 9 * * *` (every day 09:00 local)
@@ -64,12 +64,12 @@ Authority-monitoring only. Not trend-watching. See `reference/authority-feeds.md
    """)
    ```
 
-   `<joined flag list>` is the subset of `--refresh | --since <date> | --feed <name>` actually passed — e.g., `--refresh`, `--since 2026-03-01`, `--feed wai-aria-apg`, `--refresh --feed radix-ui-releases`, or literally `none` when no flags were supplied.
+   `<joined flag list>` is the subset of `--refresh | --since <date> | --feed <name>` actually passed - e.g., `--refresh`, `--since 2026-03-01`, `--feed wai-aria-apg`, `--refresh --feed radix-ui-releases`, or literally `none` when no flags were supplied.
 
 5. **Print summary.**
 
    After the agent returns:
-   - If STATE.md gained a `<blocker type="contract-violation">` on this run (snapshot version mismatch, hash-format violation, or over-200 entries per feed), surface the blocker verbatim and stop — do not print the default "review and reflect" line.
+   - If STATE.md gained a `<blocker type="contract-violation">` on this run (snapshot version mismatch, hash-format violation, or over-200 entries per feed), surface the blocker verbatim and stop - do not print the default "review and reflect" line.
    - Otherwise print the agent's one-line stdout summary (normal mode: `Surfaced N entries across M feeds. K skipped. See .design/authority-report.md.`; first-run / refresh mode: `Seeded snapshot for N feeds — next run will surface new entries.`) followed by: `Review and reflect: /gdd:reflect`.
 
 6. **Terminate with `## WATCH COMPLETE`.**
@@ -77,6 +77,6 @@ Authority-monitoring only. Not trend-watching. See `reference/authority-feeds.md
 ## Do Not
 
 - Do not modify `agents/design-authority-watcher.md`.
-- Do not modify `agents/design-reflector.md` — Phase 13.2 does not touch the reflector agent (CONTEXT.md D-25).
-- Do not write to `.design/authority-snapshot.json` or `.design/authority-report.md` directly — those are the agent's writes.
+- Do not modify `agents/design-reflector.md` - Phase 13.2 does not touch the reflector agent (CONTEXT.md D-25).
+- Do not write to `.design/authority-snapshot.json` or `.design/authority-report.md` directly - those are the agent's writes.
 - Do not fetch URLs outside `reference/authority-feeds.md`. The whitelist is the allow-list.

package/skills/zoom-out/SKILL.md

@@ -5,7 +5,7 @@ disable-model-invocation: true
 argument-hint: "[scope]"
 ---
 
-Source: mattpocock/skills (MIT) — adapted with permission. See `../NOTICE` for the full attribution block.
+Source: mattpocock/skills (MIT) - adapted with permission. See `../NOTICE` for the full attribution block.
 
 # Zoom Out
 
@@ -15,9 +15,9 @@ I don't know this area of code well. Go up a layer of abstraction. Give me a map
 
 When invoked, produce a one-screen map that names:
 
-1. **Modules in scope** — one-line description of each, using terms from `CONTEXT.md` (see `./../reference/context-md-format.md` for the schema). Do not invent terms.
-2. **Callers** — who calls these modules from elsewhere, with file paths.
-3. **Seams** — where data crosses module boundaries, named per `./../reference/architecture-vocabulary.md`.
+1. **Modules in scope** - one-line description of each, using terms from `CONTEXT.md` (see `./../reference/context-md-format.md` for the schema). Do not invent terms.
+2. **Callers** - who calls these modules from elsewhere, with file paths.
+3. **Seams** - where data crosses module boundaries, named per `./../reference/architecture-vocabulary.md`.
 
 Do not propose fixes. Do not write code. The output is a map.