@hegemonart/get-design-done 1.42.0 → 1.43.0

package/dist/claude-code/.claude/skills/health/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: gdd-health
-description: "Reports .design/ artifact health — staleness, missing files, token drift, broken state transitions."
+description: "Reports .design/ artifact health - staleness, missing files, token drift, broken state transitions."
 tools: Read, Bash, Glob, Grep, mcp__gdd_state__get
 disable-model-invocation: true
 ---
@@ -11,19 +11,19 @@ disable-model-invocation: true
 
 ## Checks
 
-1. **Artifact inventory** — `ls -la .design/*.md` with size and mtime. Print a table.
-2. **Missing expected artifacts** — by `stage` field from the `mcp__gdd_state__get` snapshot:
+1. **Artifact inventory** - `ls -la .design/*.md` with size and mtime. Print a table.
+2. **Missing expected artifacts** - by `stage` field from the `mcp__gdd_state__get` snapshot:
    - `brief` expects BRIEF.md
    - `explore` expects DESIGN.md, DESIGN-DEBT.md, DESIGN-CONTEXT.md
    - `plan` expects DESIGN-PLAN.md
    - `design` expects DESIGN-SUMMARY.md
    - `verify` expects DESIGN-VERIFICATION.md
    FAIL per missing.
-3. **Token drift** — `wc -c .design/DESIGN.md .design/DESIGN-CONTEXT.md`; approx tokens = bytes/4. WARN if combined >40000.
-4. **Aged DESIGN-DEBT** — items in `.design/DESIGN-DEBT.md` not touched in >14 days (file mtime). WARN.
-5. **Broken state transitions** — `stage` field from the snapshot inconsistent with artifacts present (e.g. stage=`verify` but DESIGN-SUMMARY.md missing). FAIL.
-6. **Pending sketch/spike wrap-ups** — any `.design/sketches/*` or `.design/spikes/*` directory lacking a SUMMARY.md. WARN.
-7. **Seed germination** — scan `.design/SEEDS.md` (if present) for seeds whose trigger keywords match the snapshot or CYCLES.md content. List as "Seed ready: <text>".
+3. **Token drift** - `wc -c .design/DESIGN.md .design/DESIGN-CONTEXT.md`; approx tokens = bytes/4. WARN if combined >40000.
+4. **Aged DESIGN-DEBT** - items in `.design/DESIGN-DEBT.md` not touched in >14 days (file mtime). WARN.
+5. **Broken state transitions** - `stage` field from the snapshot inconsistent with artifacts present (e.g. stage=`verify` but DESIGN-SUMMARY.md missing). FAIL.
+6. **Pending sketch/spike wrap-ups** - any `.design/sketches/*` or `.design/spikes/*` directory lacking a SUMMARY.md. WARN.
+7. **Seed germination** - scan `.design/SEEDS.md` (if present) for seeds whose trigger keywords match the snapshot or CYCLES.md content. List as "Seed ready: <text>".
 
 ## State snapshot
 
@@ -57,17 +57,17 @@ Health: 5 / 6 checks passing.
 
 After the health table, the `gdd_health` MCP surface (`scripts/lib/health-mirror/index.cjs`) reports a `figma_extract` check so a user knows whether figma-extract is usable. The detail is one of three exact strings:
 
-- `figma extract: ready (token set)` — `FIGMA_TOKEN` (or `FIGMA_PERSONAL_ACCESS_TOKEN`) is present (status `ok`).
-- `figma extract: token missing` — no token env is set (status `warn`).
-- `figma extract: plugin sync needed for variables (Free tier detected)` — token present but a prior pull recorded a 403/skip on the Variables REST path, so run the plugin-sync step (status `warn`).
+- `figma extract: ready (token set)` - `FIGMA_TOKEN` (or `FIGMA_PERSONAL_ACCESS_TOKEN`) is present (status `ok`).
+- `figma extract: token missing` - no token env is set (status `warn`).
+- `figma extract: plugin sync needed for variables (Free tier detected)` - token present but a prior pull recorded a 403/skip on the Variables REST path, so run the plugin-sync step (status `warn`).
 
-Token PRESENCE only is detected (D-10) — the token value is never read, logged, or shown. The Free-tier signal is read from the local raw-pull cache only; no network call is made.
+Token PRESENCE only is detected (D-10) - the token value is never read, logged, or shown. The Free-tier signal is read from the local raw-pull cache only; no network call is made.
 
 ## Skill-discipline bootstrap (skill_discipline)
 
-The `gdd_health` MCP surface also reports a `skill_discipline` check (Phase 32) confirming the using-gdd SessionStart bootstrap is live — detail is one of three exact strings:
-- `skill-discipline: ready` — `skills/using-gdd/SKILL.md` exists AND `hooks/hooks.json` SessionStart wires `inject-using-gdd.sh` (status `ok`).
-- `skill-discipline: missing using-gdd` (skill absent) or `skill-discipline: hook not wired` (skill present, no SessionStart inject) — both `warn`.
+The `gdd_health` MCP surface also reports a `skill_discipline` check (Phase 32) confirming the using-gdd SessionStart bootstrap is live - detail is one of three exact strings:
+- `skill-discipline: ready` - `skills/using-gdd/SKILL.md` exists AND `hooks/hooks.json` SessionStart wires `inject-using-gdd.sh` (status `ok`).
+- `skill-discipline: missing using-gdd` (skill absent) or `skill-discipline: hook not wired` (skill present, no SessionStart inject) - both `warn`.
 
 ## Check MCP registration (gdd-mcp)
 
@@ -94,6 +94,6 @@ Thresholds: warn >=100, block >=250 (D-01). Strict description-format off by def
 
 ## Do Not
 
-- Do not mutate STATE.md — this skill is read-only. Only `mcp__gdd_state__get` is permitted.
+- Do not mutate STATE.md - this skill is read-only. Only `mcp__gdd_state__get` is permitted.
 
 ## HEALTH COMPLETE

package/dist/claude-code/.claude/skills/health/health-mcp-detection.md

@@ -19,11 +19,11 @@ than crashing the skill.
 
 1. Read `.design/config.json` (if present). Parse JSON inside a try/catch.
 2. If `config.mcp_nudge === false`, SKIP this step entirely (render nothing).
-3. On parse failure: default to `mcp_nudge=true` (show the row) — fail-safe per threat T-27.7-04-05.
+3. On parse failure: default to `mcp_nudge=true` (show the row) - fail-safe per threat T-27.7-04-05.
 
 ## Detection
 
-1. Read `.claude/settings.local.json` (or equivalent harness settings file) and inspect its `mcpServers` object — alternatively run `claude mcp list` / `codex mcp list` if a CLI is available (see fallback below).
+1. Read `.claude/settings.local.json` (or equivalent harness settings file) and inspect its `mcpServers` object - alternatively run `claude mcp list` / `codex mcp list` if a CLI is available (see fallback below).
 2. Preferred invocation via the install-lib: call `detectMcpRegistration()` from `scripts/lib/install/mcp-register.cjs`. Returns `{harnesses: [{harness, present, registered}], summary}`.
 
 ## Row rendering
@@ -41,4 +41,4 @@ Based on the detection result, render exactly ONE of these row strings:
 
 ## Fallback (if `mcp-register.cjs` not yet shipped)
 
-Skip this step silently with status `MCP server: unknown`. This step is non-blocking — failures here MUST NOT crash the SKILL.
+Skip this step silently with status `MCP server: unknown`. This step is non-blocking - failures here MUST NOT crash the SKILL.

package/dist/claude-code/.claude/skills/health/health-skill-length-report.md

@@ -1,4 +1,4 @@
-# Health skill — skill-length report subsection
+# Health skill - skill-length report subsection
 
 Phase 28.5-11 / D-11 reference. Read by `skills/health/SKILL.md` to render the
 "Skill-length report" subsection after the standard health checks.
@@ -50,9 +50,9 @@ Skill-length: 70 total | 67 clean | 2 warn (>=100) | 1 block (>=250)
 
 ## Thresholds (D-01)
 
-- `warn >=100` — skill flagged as advisory; CI emits `::warning::` annotation
+- `warn >=100` - skill flagged as advisory; CI emits `::warning::` annotation
   but does not fail the build.
-- `block >=250` — skill flagged as blocker; CI emits `::error::` and fails
+- `block >=250` - skill flagged as blocker; CI emits `::error::` and fails
   the build via exit code 2.
 
 ## Strict description-format (D-02)
@@ -64,6 +64,6 @@ to hard-block based on A/B evidence at
 
 ## Cross-link from health
 
-- `skills/health/SKILL.md` — emits the report after the main checks table.
-- `scripts/validate-skill-length.cjs` — provides the JSON.
-- `tests/phase-28.5-baseline.test.cjs` — locks the post-rework distribution.
+- `skills/health/SKILL.md` - emits the report after the main checks table.
+- `scripts/validate-skill-length.cjs` - provides the JSON.
+- `tests/phase-28.5-baseline.test.cjs` - locks the post-rework distribution.

package/dist/claude-code/.claude/skills/help/SKILL.md

@@ -5,7 +5,7 @@ tools: Read
 disable-model-invocation: true
 ---
 
-# Get Design Done — Help
+# Get Design Done - Help
 
 **Role:** Print a formatted reference of all `/gdd:` commands, grouped by purpose.
 

package/dist/claude-code/.claude/skills/list-assumptions/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: gdd-list-assumptions
-description: "Surfaces hidden design assumptions baked into the codebase before planning — pattern-based detection plus user-surfaced items."
+description: "Surfaces hidden design assumptions baked into the codebase before planning - pattern-based detection plus user-surfaced items."
 argument-hint: "[--area typography|color|layout|motion|a11y]"
 tools: Read, Grep, Glob
 disable-model-invocation: true
@@ -10,11 +10,11 @@ disable-model-invocation: true
 
 **Role:** Surface implicit design assumptions that were never explicitly decided. Output a numbered list tagging each as `[EXPLICIT]` (found in STATE.md/DESIGN-CONTEXT.md decisions) or `[IMPLICIT]` (inferred from code patterns).
 
-## Step 1 — Read explicit decisions
+## Step 1 - Read explicit decisions
 
 Read `.design/STATE.md` `<decisions>` and `.design/DESIGN-CONTEXT.md` (if present). Collect every D-XX as `[EXPLICIT]` entries keyed by category.
 
-## Step 2 — Scan codebase for implicit patterns
+## Step 2 - Scan codebase for implicit patterns
 
 If `--area <name>` is given, restrict to that area. Otherwise scan all.
 
@@ -39,7 +39,7 @@ If `--area <name>` is given, restrict to that area. Otherwise scan all.
 
 For each hit, emit `Detected assumption: [pattern] at [file:line]` and flag as `[IMPLICIT]`.
 
-## Step 3 — Output
+## Step 3 - Output
 
 ```
 ━━━ Design assumptions ━━━

package/dist/claude-code/.claude/skills/map/SKILL.md

@@ -6,7 +6,7 @@ tools: Read, Write, Bash, Task
 user-invocable: true
 ---
 
-# Get Design Done — Map
+# Get Design Done - Map
 
 Parallel orchestrator. Spawns 5 specialist mappers, each writing one file under `.design/map/`. The explore stage consumes these when present. See `./reference/heuristics.md` §"Optimization rules" for parallel-spawn cost considerations.
 
@@ -20,16 +20,16 @@ Parallel orchestrator. Spawns 5 specialist mappers, each writing one file under
 | `a11y-mapper` | `.design/map/a11y.md` |
 | `motion-mapper` | `.design/map/motion.md` |
 
-## Step 1 — Setup
+## Step 1 - Setup
 
 - Ensure `.design/map/` exists (create if missing).
 - Read `.design/config.json` → `parallelism` object. Use `reference/config-schema.md` defaults if absent.
-- Read `.design/STATE.md` — note `<connections>` (Figma availability for token-mapper).
+- Read `.design/STATE.md` - note `<connections>` (Figma availability for token-mapper).
 - Parse `$ARGUMENTS`. If `--only <name>`, restrict the dispatch set to one mapper.
 
-## Step 2 — Parallelism Decision
+## Step 2 - Parallelism Decision
 
-Per `reference/parallelism-rules.md`: all 5 mappers have `parallel-safe: auto` with disjoint `writes:` (each writes a different `.design/map/*.md` file) — no hard-rule conflict. `typical-duration-seconds` sum (~210s) minus slowest (~45s) ≈ 165s savings → clears `min_estimated_savings_seconds`. Verdict: **parallel**.
+Per `reference/parallelism-rules.md`: all 5 mappers have `parallel-safe: auto` with disjoint `writes:` (each writes a different `.design/map/*.md` file) - no hard-rule conflict. `typical-duration-seconds` sum (~210s) minus slowest (~45s) ≈ 165s savings → clears `min_estimated_savings_seconds`. Verdict: **parallel**.
 
 Write the verdict to STATE.md:
 
@@ -46,7 +46,7 @@ Write the verdict to STATE.md:
 
 `--only` → adjust `agents` and set `verdict: serial` with `reason: "single mapper requested"`.
 
-## Step 3 — Dispatch (concurrent)
+## Step 3 - Dispatch (concurrent)
 
 Spawn all selected mappers in a single response with multiple `Task()` calls:
 
@@ -66,17 +66,17 @@ output file under .design/map/. Emit your completion marker when done.
 
 Wait for each completion marker: `## TOKEN MAP COMPLETE`, `## COMPONENT MAP COMPLETE`, `## VISUAL HIERARCHY MAP COMPLETE`, `## A11Y MAP COMPLETE`, `## MOTION MAP COMPLETE`.
 
-## Step 3.5 — Synthesize parallel mapper outputs (Plan 10.1-04, D-13/D-14/D-15)
+## Step 3.5 - Synthesize parallel mapper outputs (Plan 10.1-04, D-13/D-14/D-15)
 
-Each mapper has written its own `.design/map/*.md` (disjoint writes). Main-context doesn't need all 5 verbatim — invoke `synthesize` inline with `outputs:[<each file's text labelled "=== from <mapper> ==="]`, `directive: "Merge into cross-cutting DESIGN-PATTERNS.md preserving section headers; consolidate cross-mapper duplicates with source-agent names; target ~120 lines."`, `output_shape:"markdown"`.
+Each mapper has written its own `.design/map/*.md` (disjoint writes). Main-context doesn't need all 5 verbatim - invoke `synthesize` inline with `outputs:[<each file's text labelled "=== from <mapper> ==="]`, `directive: "Merge into cross-cutting DESIGN-PATTERNS.md preserving section headers; consolidate cross-mapper duplicates with source-agent names; target ~120 lines."`, `output_shape:"markdown"`.
 
-Wait for `## SYNTHESIS COMPLETE`. Write merged markdown to `.design/DESIGN-PATTERNS.md` (overwrite if present) — the primary explore-stage input; per-mapper files remain as drill-down evidence. `--only` (single mapper) → skip this step.
+Wait for `## SYNTHESIS COMPLETE`. Write merged markdown to `.design/DESIGN-PATTERNS.md` (overwrite if present) - the primary explore-stage input; per-mapper files remain as drill-down evidence. `--only` (single mapper) → skip this step.
 
-## Step 4 — Collate
+## Step 4 - Collate
 
-Write `.design/DESIGN-MAP.md` — thin index linking to each `.design/map/*.md` with a one-paragraph summary from each file's header. If Step 3.5 ran, also cross-link to `.design/DESIGN-PATTERNS.md` and note at the top: "See DESIGN-PATTERNS.md for the merged cross-cutting summary — this index preserves per-mapper drill-down."
+Write `.design/DESIGN-MAP.md` - thin index linking to each `.design/map/*.md` with a one-paragraph summary from each file's header. If Step 3.5 ran, also cross-link to `.design/DESIGN-PATTERNS.md` and note at the top: "See DESIGN-PATTERNS.md for the merged cross-cutting summary - this index preserves per-mapper drill-down."
 
-## Step 5 — Report
+## Step 5 - Report
 
 ```
 ━━━ Map complete ━━━

package/dist/claude-code/.claude/skills/migrate/SKILL.md

@@ -10,7 +10,7 @@ tools: Read, Write, Bash, Grep, Glob
 
 Closes the GDD-on-GDD gap: when GDD moves or removes its own paths (e.g. the Phase 31.5
 `scripts/lib/**` → `sdk/**` reorg), a project that referenced the old paths needs updating. This skill
-consults the deprecation registry, finds the stale references **in this project**, and rewrites them —
+consults the deprecation registry, finds the stale references **in this project**, and rewrites them -
 **after showing you the diff**. It never edits silently. Contract: `../../reference/DEPRECATIONS.md`.
 
 ## Invocation
@@ -18,7 +18,7 @@ consults the deprecation registry, finds the stale references **in this project*
 | Command | Behavior |
 |---|---|
 | `/gdd:migrate` | Scan + preview every applicable migration, then confirm each before applying. |
-| `/gdd:migrate --dry-run` | Preview only — print the diff, change nothing. |
+| `/gdd:migrate --dry-run` | Preview only - print the diff, change nothing. |
 | `/gdd:migrate --yes` | Apply every applicable migration without the per-change prompt (still prints what changed). |
 
 ## Steps
@@ -43,19 +43,19 @@ consults the deprecation registry, finds the stale references **in this project*
    - project-local skill/agent references (`grep` the repo, excluding `.git/`, `node_modules/`, and
      GDD's own `reference/DEPRECATIONS.md`),
    - any `require(...)`/import of a removed SDK path.
-   For a code rewrite, scaffold the edit with `scripts/lib/migration/codemod-gen.cjs` (Phase 39.1) —
+   For a code rewrite, scaffold the edit with `scripts/lib/migration/codemod-gen.cjs` (Phase 39.1) -
    you emit the change as a reviewable patch, you do not run a codemod engine.
 4. **Preview.** Print a unified-diff-style preview per file: `Old → New`, the registry status
    (`deprecated` vs `removed`), and the migration hint. If `--dry-run`, stop here.
 5. **Confirm + apply.** Without `--yes`, ask per change. With `--yes`, apply all. Use `Write` to make
    the edits; never touch a file the user didn't consent to.
 6. **Report.** Summarize: files changed, references rewritten, and any `removed`-status reference that
-   still has no replacement wired (flag it loudly — that one breaks at the installed version).
+   still has no replacement wired (flag it loudly - that one breaks at the installed version).
 
 ## Boundaries
 
 - **Preview-first.** Nothing changes before you've shown the diff (or `--yes` was passed).
-- Migrates **this project's references** to GDD paths — it does not rewrite GDD's own source, and it
+- Migrates **this project's references** to GDD paths - it does not rewrite GDD's own source, and it
   never performs a downgrade (reverse migrations are out of scope).
 - Read the registry; never invent a migration that isn't in `reference/DEPRECATIONS.md`.
 

package/dist/claude-code/.claude/skills/new-cycle/SKILL.md

@@ -31,7 +31,7 @@ The cycle is the hierarchical unit above individual pipeline runs: **Cycle > Pip
 
 ## Do Not
 
-- Do not archive prior artifacts here — that's `/gdd:complete-cycle`.
-- Do not overwrite the existing CYCLES.md — append only.
+- Do not archive prior artifacts here - that's `/gdd:complete-cycle`.
+- Do not overwrite the existing CYCLES.md - append only.
 
 ## NEW-CYCLE COMPLETE

package/dist/claude-code/.claude/skills/new-cycle/milestone-completeness-rubric.md

@@ -18,59 +18,59 @@ across consumers and updates land in one place rather than fanning out across N
 
 The lifecycle has four nested layers. A layer is complete only when EVERY criterion at
 that layer is satisfied. Layers above can only flip complete when every layer below has
-flipped complete first — closeout walks bottom-up.
+flipped complete first - closeout walks bottom-up.
 
 ### Task level
 
-The smallest unit of work — one row in a PLAN.md `<tasks>` list.
+The smallest unit of work - one row in a PLAN.md `<tasks>` list.
 
 - Verify command runs with exit 0 (the `<verify>` block's command).
 - The `<done>` criterion is observable (the file exists, the test passes, the output
   matches the contract).
 - If the task is `tdd="true"`: tests pass after the GREEN step; tests fail before it.
-- File diff is scoped to the declared `files_modified` only — no collateral damage.
+- File diff is scoped to the declared `files_modified` only - no collateral damage.
 - A single commit per task in conventional form `{type}({phase}-{plan}): {description}`.
 - Deviations (Rules 1, 2, 3) tracked for the SUMMARY.md "Deviations" section.
 
 ### Plan level
 
-A self-contained chunk of work — one `XX-YY-PLAN.md`.
+A self-contained chunk of work - one `XX-YY-PLAN.md`.
 
 - All tasks complete (per task level above).
 - Plan-level validator passes (e.g. `validate-skill-length.cjs` for Phase 28.5 buckets;
   `validate-frontmatter.ts` for agent-frontmatter plans).
 - SUMMARY.md written at `.planning/phases/XX-name/XX-YY-SUMMARY.md` with the canonical
   shape: deviations, files-modified table, commits, verification result, decisions.
-- No collateral damage outside the plan's declared `files_modified` list — out-of-scope
+- No collateral damage outside the plan's declared `files_modified` list - out-of-scope
   edits are forbidden (executor Rule 5 boundary).
 - A final docs commit aggregates `SUMMARY.md`, `STATE.md`, `ROADMAP.md`, and
   `REQUIREMENTS.md` updates.
 
 ### Phase level
 
-A coherent batch of plans — one `XX-name/` directory under `.planning/phases/`.
+A coherent batch of plans - one `XX-name/` directory under `.planning/phases/`.
 
 - All plans complete (per plan level above).
 - Phase-level verification ALL pass (`<verification>` block in each PLAN.md).
 - ROADMAP.md flipped `[ ]` → `[x]` for all plans in this phase (rule #14: scoped flip
-  only — never flip plans outside this phase).
-- Phase SUMMARY ladder coherent — each `XX-YY-SUMMARY.md` exists and reads top-to-bottom
+  only - never flip plans outside this phase).
+- Phase SUMMARY ladder coherent - each `XX-YY-SUMMARY.md` exists and reads top-to-bottom
   as a single story.
 - All decisions surfaced through the SUMMARY frontmatter and rolled up into STATE.md's
   `<decisions>` block.
 
 ### Cycle level
 
-A shipping milestone — typically one minor version bump in the gdd project.
+A shipping milestone - typically one minor version bump in the gdd project.
 
 - All phases for the cycle's target version complete (per phase level above).
 - 4 manifests version-aligned: `plugin.json`, `marketplace.json`, `package.json`, and
   the phase-20 manifests-version baseline (`test-fixture/baselines/phase-XX/manifests-version.txt`).
 - CHANGELOG.md entry written for the new version with one block per phase.
-- Off-cadence registration if applicable — `tests/semver-compare.test.cjs` adds
+- Off-cadence registration if applicable - `tests/semver-compare.test.cjs` adds
   `OFF_CADENCE_VERSIONS.add('<version>')` for `.5`/`.6`/`.7` insertion-style versions.
 - Regression baseline at `test-fixture/baselines/phase-XX/` exists and the
-  `tests/phase-XX-baseline.test.cjs` suite passes (version-agnostic — reads
+  `tests/phase-XX-baseline.test.cjs` suite passes (version-agnostic - reads
   `package.json#version`).
 - NOTICE attribution updated if any third-party content was adopted in this cycle.
 - Closeout plan's scoped ROADMAP flip touches only this cycle's checkboxes (precedent:
@@ -78,10 +78,10 @@ A shipping milestone — typically one minor version bump in the gdd project.
 
 ## Cross-references
 
-- `./STATE-TEMPLATE.md` — STATE.md schema; closeout updates the `<position>` block's
+- `./STATE-TEMPLATE.md` - STATE.md schema; closeout updates the `<position>` block's
   `last_checkpoint` field.
-- `../skills/turn-closeout/SKILL.md` — consumer at the turn boundary (within a stage).
-- `../skills/new-cycle/SKILL.md` — consumer at cycle ingress.
-- `../skills/complete-cycle/SKILL.md` — consumer at cycle egress.
-- `../skills/quality-gate/SKILL.md` — Stage 4.5 gate that gates the plan-level "verify
+- `../skills/turn-closeout/SKILL.md` - consumer at the turn boundary (within a stage).
+- `../skills/new-cycle/SKILL.md` - consumer at cycle ingress.
+- `../skills/complete-cycle/SKILL.md` - consumer at cycle egress.
+- `../skills/quality-gate/SKILL.md` - Stage 4.5 gate that gates the plan-level "verify
   command runs with exit 0" criterion when project tooling exists.

package/dist/claude-code/.claude/skills/new-project/SKILL.md

@@ -48,6 +48,6 @@ One-time project initialization. Replaces "run scan cold" by gathering context u
 ## Do Not
 
 - Do not delete or overwrite existing `.design/` artifacts if re-initializing.
-- Do not run any pipeline stage automatically — this is init only.
+- Do not run any pipeline stage automatically - this is init only.
 
 ## NEW-PROJECT COMPLETE

package/dist/claude-code/.claude/skills/next/SKILL.md

@@ -5,7 +5,7 @@ tools: Read, Write, mcp__gdd_status, mcp__gdd_phase_current, mcp__gdd_plans_list
 disable-model-invocation: true
 ---
 
-# Get Design Done — Next
+# Get Design Done - Next
 
 **Role:** Lightweight router. Read `.design/STATE.md` and recommend the next command.
 
@@ -13,7 +13,7 @@ disable-model-invocation: true
 
 ## Logic
 
-Two paths — MCP preferred when available, file-read fallback otherwise.
+Two paths - MCP preferred when available, file-read fallback otherwise.
 
 ### MCP path (preferred)
 
@@ -24,7 +24,7 @@ When `mcp__gdd_phase_current` is exposed (Phase 27.7+, registered via `npx @hege
 3. (Optional) Call `mcp__gdd_plans_list` (no args) → current phase plans + status, to identify the next incomplete plan and refine the recommendation.
 4. If `mcp__gdd_status` returns a "STATE.md missing" error, print: "No STATE.md found. Run `/gdd:new-project` to initialize, or `@get-design-done brief` to start the pipeline." and stop. Otherwise, skip to the routing table.
 
-Two to three MCP calls = full routing decision (~3s, ~32k tokens — Storybloq benchmark).
+Two to three MCP calls = full routing decision (~3s, ~32k tokens - Storybloq benchmark).
 
 ### File-read path (fallback)
 
@@ -34,7 +34,7 @@ When MCP tools are not available, fall back to the legacy flow:
    - **No STATE.md** → Print: "No STATE.md found. Run `/gdd:new-project` to initialize, or `@get-design-done brief` to start the pipeline."
 2. If STATE.md exists, parse frontmatter `stage:` field. Proceed to the routing table.
 
-This path loads the same context in 1–2 file reads (~20s, ~46.5k tokens — file-reading baseline).
+This path loads the same context in 1–2 file reads (~20s, ~46.5k tokens - file-reading baseline).
 
 ## Routing table
 
@@ -63,6 +63,6 @@ Status: <status>
 ## Do Not
 
 - Do not modify STATE.md.
-- Do not invoke the next stage automatically — only recommend.
+- Do not invoke the next stage automatically - only recommend.
 
 ## NEXT COMPLETE

package/dist/claude-code/.claude/skills/note/SKILL.md

@@ -8,7 +8,7 @@ disable-model-invocation: true
 
 # /gdd:note
 
-**Role:** Ephemeral design notes. Zero ceremony — no priority, no due date. Backing store: `.design/NOTES.md`.
+**Role:** Ephemeral design notes. Zero ceremony - no priority, no due date. Backing store: `.design/NOTES.md`.
 
 ## File format
 

package/dist/claude-code/.claude/skills/openrouter-status/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: gdd-openrouter-status
-description: "Read-only OpenRouter catalog + tier-mapping diagnostic — surfaces catalog freshness (fetched_at vs the 24h TTL), the last-fetch timestamp, the resolved opus/sonnet/haiku → model mappings (via the Phase-33.6 adapter), and a per-tier preview. Use when investigating which OpenRouter model a tier resolves to, or whether the catalog cache is fresh/stale. Phase 33.6 (v1.33.6) diagnostic — /gdd:openrouter-status."
+description: "Read-only OpenRouter catalog + tier-mapping diagnostic - surfaces catalog freshness (fetched_at vs the 24h TTL), the last-fetch timestamp, the resolved opus/sonnet/haiku → model mappings (via the Phase-33.6 adapter), and a per-tier preview. Use when investigating which OpenRouter model a tier resolves to, or whether the catalog cache is fresh/stale. Phase 33.6 (v1.33.6) diagnostic - /gdd:openrouter-status."
 argument-hint: "[--refresh]"
 tools: Read, Bash
 disable-model-invocation: true
@@ -10,9 +10,9 @@ disable-model-invocation: true
 
 ## Role
 
-You are a deterministic, read-only diagnostic skill. You do **not** spawn agents and you do **not** modify the catalog cache. You read `.design/cache/openrouter-models.json` (the Phase-33.6-01 catalog cache) via `scripts/lib/openrouter/catalog-fetcher.cjs#readCatalog`, resolve the `opus`/`sonnet`/`haiku` tiers via `scripts/lib/tier-resolver-openrouter.cjs#resolve`, and emit a single Markdown status block. Read-only — to refresh the catalog you pass `--refresh` (a single opt-in fetch gated on `OPENROUTER_API_KEY`); there is no other mutation. See `connections/openrouter.md` for setup and `reference/openrouter-tier-mapping.md` for the resolution heuristic.
+You are a deterministic, read-only diagnostic skill. You do **not** spawn agents and you do **not** modify the catalog cache. You read `.design/cache/openrouter-models.json` (the Phase-33.6-01 catalog cache) via `scripts/lib/openrouter/catalog-fetcher.cjs#readCatalog`, resolve the `opus`/`sonnet`/`haiku` tiers via `scripts/lib/tier-resolver-openrouter.cjs#resolve`, and emit a single Markdown status block. Read-only - to refresh the catalog you pass `--refresh` (a single opt-in fetch gated on `OPENROUTER_API_KEY`); there is no other mutation. See `connections/openrouter.md` for setup and `reference/openrouter-tier-mapping.md` for the resolution heuristic.
 
-This is `disable-model-invocation: true` (mirroring `skills/cache-manager/SKILL.md`): the skill is user-invoked only — the model must not auto-spawn it. It never makes a model call.
+This is `disable-model-invocation: true` (mirroring `skills/cache-manager/SKILL.md`): the skill is user-invoked only - the model must not auto-spawn it. It never makes a model call.
 
 ## Invocation Contract
 
@@ -45,7 +45,7 @@ Tier resolution is currently falling back to the native provider (graceful degra
 
 ### 3. Compute freshness
 
-Read `fetched_at` from the cache object and compare against the 24h TTL (D-02): `age = now - fetched_at`. `age < 24h` → **fresh**; otherwise → **stale** (a stale catalog still resolves — the adapter uses the last good cache).
+Read `fetched_at` from the cache object and compare against the 24h TTL (D-02): `age = now - fetched_at`. `age < 24h` → **fresh**; otherwise → **stale** (a stale catalog still resolves - the adapter uses the last good cache).
 
 ### 4. Resolve the tiers
 

package/dist/claude-code/.claude/skills/optimize/SKILL.md

@@ -1,16 +1,16 @@
 ---
 name: optimize
-description: "Reads .design/telemetry/costs.jsonl + .design/agent-metrics.json, runs rule-based analysis, writes .design/OPTIMIZE-RECOMMENDATIONS.md. Pure advisory — no auto-apply. User reviews + decides."
+description: "Reads .design/telemetry/costs.jsonl + .design/agent-metrics.json, runs rule-based analysis, writes .design/OPTIMIZE-RECOMMENDATIONS.md. Pure advisory - no auto-apply. User reviews + decides."
 argument-hint: "[--refresh] [--min-spawns=N]"
 user-invocable: true
 tools: Read, Bash, Grep, Write
 ---
 
-# /gdd:optimize — Optimization Advisor
+# /gdd:optimize - Optimization Advisor
 
 ## Role
 
-Read the telemetry ledger (`.design/telemetry/costs.jsonl`) and per-agent aggregate (`.design/agent-metrics.json`), apply a fixed set of rule-based heuristics, and emit recommendations to `.design/OPTIMIZE-RECOMMENDATIONS.md`. Never modify agent files, budget config, or cache state. Output is a markdown table of proposals the user reviews manually, mirroring Phase 11 `/gdd:apply-reflections`. **Advisory only**: never edits `agents/*.md`, `.design/budget.json`, `.design/cache-manifest.json`. Never makes model calls — every rule is deterministic. See `./reference/heuristics.md` §"Optimization rules" for the full rule catalog.
+Read the telemetry ledger (`.design/telemetry/costs.jsonl`) and per-agent aggregate (`.design/agent-metrics.json`), apply a fixed set of rule-based heuristics, and emit recommendations to `.design/OPTIMIZE-RECOMMENDATIONS.md`. Never modify agent files, budget config, or cache state. Output is a markdown table of proposals the user reviews manually, mirroring Phase 11 `/gdd:apply-reflections`. **Advisory only**: never edits `agents/*.md`, `.design/budget.json`, `.design/cache-manifest.json`. Never makes model calls - every rule is deterministic. See `./reference/heuristics.md` §"Optimization rules" for the full rule catalog.
 
 ## Refresh Step
 
@@ -24,24 +24,24 @@ Idempotent. If `--refresh` absent and `.design/agent-metrics.json` generated wit
 
 ## Inputs
 
-- `.design/telemetry/costs.jsonl` — append-only; tolerant of malformed lines.
-- `.design/agent-metrics.json` — per-agent aggregate; source of truth for `cache_hit_rate`, `lazy_skip_rate`, `total_cost_usd`, `total_spawns`.
-- `agents/*.md` — frontmatter cross-reference for tier override churn + typical-duration drift.
-- `.design/budget.json` — `tier_overrides` table (optional).
+- `.design/telemetry/costs.jsonl` - append-only; tolerant of malformed lines.
+- `.design/agent-metrics.json` - per-agent aggregate; source of truth for `cache_hit_rate`, `lazy_skip_rate`, `total_cost_usd`, `total_spawns`.
+- `agents/*.md` - frontmatter cross-reference for tier override churn + typical-duration drift.
+- `.design/budget.json` - `tier_overrides` table (optional).
 
 ## Optional Arguments
 
-- `--refresh` — force aggregator refresh even if metrics file is fresh.
-- `--min-spawns=N` — only emit recommendations for agents with ≥ N spawns (default 5).
+- `--refresh` - force aggregator refresh even if metrics file is fresh.
+- `--min-spawns=N` - only emit recommendations for agents with ≥ N spawns (default 5).
 
 ## Rules
 
 Rule-based analysis. Full thresholds + emission templates in `./reference/heuristics.md` §"Optimization rules"; here, the short rule catalog:
 
-- **R1 — Low cache hit rate.** IF `total_spawns >= --min-spawns` AND `cache_hit_rate < 0.20` → propose batching + investigate shared-preamble ordering.
-- **R2 — Expensive + rarely lazy-skipped.** IF `total_cost_usd > 0.50` AND `lazy_skip_rate < 0.10` → propose adding a lazy gate at `agents/{agent}-gate.md` (Plan 10.1-04 pattern).
-- **R3 — Tier override churn.** IF measured `tier` differs from frontmatter `default-tier` for multiple rows → propose updating frontmatter or removing budget.json override.
-- **R4 — Typical duration drift.** IF measured `typical_duration_seconds` differs from frontmatter by > 50% → propose frontmatter update. (v1 only computes wall-clock duration if both spawn + complete rows have matching correlation IDs; otherwise flag "insufficient data".)
+- **R1 - Low cache hit rate.** IF `total_spawns >= --min-spawns` AND `cache_hit_rate < 0.20` → propose batching + investigate shared-preamble ordering.
+- **R2 - Expensive + rarely lazy-skipped.** IF `total_cost_usd > 0.50` AND `lazy_skip_rate < 0.10` → propose adding a lazy gate at `agents/{agent}-gate.md` (Plan 10.1-04 pattern).
+- **R3 - Tier override churn.** IF measured `tier` differs from frontmatter `default-tier` for multiple rows → propose updating frontmatter or removing budget.json override.
+- **R4 - Typical duration drift.** IF measured `typical_duration_seconds` differs from frontmatter by > 50% → propose frontmatter update. (v1 only computes wall-clock duration if both spawn + complete rows have matching correlation IDs; otherwise flag "insufficient data".)
 
 ## Output Format
 
@@ -87,8 +87,8 @@ The Phase 11 reflector (`agents/design-reflector.md`) reads both `costs.jsonl` a
 
 - Does not make model calls (rule-based, deterministic).
 - Does not modify config.
-- Does not propose changes outside the four rules — future rules added by future phases.
-- Does not learn from history — Phase 11 reflector territory.
+- Does not propose changes outside the four rules - future rules added by future phases.
+- Does not learn from history - Phase 11 reflector territory.
 
 ## Failure Modes
 

package/dist/claude-code/.claude/skills/pause/SKILL.md

@@ -13,7 +13,7 @@ disable-model-invocation: true
 
 Captures enough state that a killed or stopped session can resume cleanly via `/gdd:resume` or `/gdd:continue`.
 
-Each invocation writes an **immutable numbered checkpoint** — it does not overwrite previous pauses. This enables branched cycles: you can pause, take a detour via `/gdd:sketch`, compare, and resume an older snapshot via `/gdd:resume N`.
+Each invocation writes an **immutable numbered checkpoint** - it does not overwrite previous pauses. This enables branched cycles: you can pause, take a detour via `/gdd:sketch`, compare, and resume an older snapshot via `/gdd:resume N`.
 
 ## Steps
 
@@ -21,7 +21,7 @@ Each invocation writes an **immutable numbered checkpoint** — it does not over
    - Current `stage` and `cycle`
    - `last_checkpoint` timestamp
    - `task_progress` and `status` for the current run
-   - Open todos (from `.design/TODO.md` if present — this file is outside the MCP catalog, so `Read` is still used)
+   - Open todos (from `.design/TODO.md` if present - this file is outside the MCP catalog, so `Read` is still used)
    - Active sketch/spike directories (scan `.design/sketches/` and `.design/spikes/` for in-progress markers)
 
 2. **Determine checkpoint number**: run
@@ -34,7 +34,7 @@ Each invocation writes an **immutable numbered checkpoint** — it does not over
    "What are you in the middle of? (optional context to capture)"
 
 4. **Flip status via MCP** so `/gdd:resume` can detect the pause and recover the prior status:
-   1. `mcp__gdd_state__set_status` with `status: "paused:<prior-status>"` — the `paused:` prefix preserves the prior status for resume parsing.
+   1. `mcp__gdd_state__set_status` with `status: "paused:<prior-status>"` - the `paused:` prefix preserves the prior status for resume parsing.
    2. If the user supplied a context/blocker message: `mcp__gdd_state__add_blocker` with `{ stage: <current>, date: <today>, text: <message> }`.
    3. `mcp__gdd_state__checkpoint` to stamp `last_checkpoint` via MCP.
 
@@ -69,9 +69,9 @@ Each invocation writes an **immutable numbered checkpoint** — it does not over
 
 ## Do Not
 
-- Do not mutate STATE.md directly — all STATE.md writes go through the `gdd-state` MCP tools above. Checkpoint files + HANDOFF.md are sibling artifacts, written with `Write`.
+- Do not mutate STATE.md directly - all STATE.md writes go through the `gdd-state` MCP tools above. Checkpoint files + HANDOFF.md are sibling artifacts, written with `Write`.
 - Do not abort in-progress sketches; just record them.
 - Do not delete previous checkpoint files.
-- Do not call `mcp__gdd_state__transition_stage` — pause is status-only, never a stage transition.
+- Do not call `mcp__gdd_state__transition_stage` - pause is status-only, never a stage transition.
 
 ## PAUSE COMPLETE

package/dist/claude-code/.claude/skills/peer-cli-add/SKILL.md

@@ -11,7 +11,7 @@ tools: Read, Edit, Write, Bash, Grep
 
 ## Role
 
-You add a brand-new peer-CLI to gdd's delegation layer. v1.27.0 ships 5 peers (codex, gemini, cursor, copilot, qwen). When the user wants a 6th — a peer that exists in the wild but isn't in our capability matrix — you walk them through the verification ladder and produce the 3-file footprint that integrates the peer cleanly. The procedural ladder, adapter scaffold shape, and verification gate live in `./peer-cli-protocol.md`.
+You add a brand-new peer-CLI to gdd's delegation layer. v1.27.0 ships 5 peers (codex, gemini, cursor, copilot, qwen). When the user wants a 6th - a peer that exists in the wild but isn't in our capability matrix - you walk them through the verification ladder and produce the 3-file footprint that integrates the peer cleanly. The procedural ladder, adapter scaffold shape, and verification gate live in `./peer-cli-protocol.md`.
 
 ## Invocation Contract
 
@@ -20,7 +20,7 @@ You add a brand-new peer-CLI to gdd's delegation layer. v1.27.0 ships 5 peers (c
 
 ## Procedure
 
-### Step 1 — Verification ladder (no edits yet)
+### Step 1 - Verification ladder (no edits yet)
 
 Walk the four-rung ladder in `./peer-cli-protocol.md` §"Verification ladder":
 
@@ -31,26 +31,26 @@ Walk the four-rung ladder in `./peer-cli-protocol.md` §"Verification ladder":
 
 Stop at the first failing rung. Do not proceed to scaffold a broken adapter.
 
-### Step 2 — Generate the adapter scaffold
+### Step 2 - Generate the adapter scaffold
 
-Copy one of `scripts/lib/peer-cli/adapters/{codex,gemini,cursor,copilot,qwen}.cjs` as the template (pick by protocol — ASP for `<protocol>=asp`, else ACP). Replace `ROLES_CLAIMED`, `ROLE_PREFIX`, `name`, `protocol` with the user's values from Step 1. The full adapter scaffold shape — `claims`, `dispatch`, exports — lives in `./peer-cli-protocol.md` §"Adapter scaffold shape" so consumers (codex/gemini/cursor/copilot/qwen) stay byte-similar.
+Copy one of `scripts/lib/peer-cli/adapters/{codex,gemini,cursor,copilot,qwen}.cjs` as the template (pick by protocol - ASP for `<protocol>=asp`, else ACP). Replace `ROLES_CLAIMED`, `ROLE_PREFIX`, `name`, `protocol` with the user's values from Step 1. The full adapter scaffold shape - `claims`, `dispatch`, exports - lives in `./peer-cli-protocol.md` §"Adapter scaffold shape" so consumers (codex/gemini/cursor/copilot/qwen) stay byte-similar.
 
 Write the result to `scripts/lib/peer-cli/adapters/<new-peer-id>.cjs`.
 
-### Step 3 — Three-file footprint
+### Step 3 - Three-file footprint
 
 Per `./peer-cli-protocol.md` §"Three-file footprint":
 
 1. New adapter at `scripts/lib/peer-cli/adapters/<new-peer-id>.cjs` (Step 2).
-2. Edit `scripts/lib/install/runtimes.cjs` — add `peerBinary` field (platform-aware: `<peer-binary>.cmd` on Windows, plain on POSIX).
-3. Edit `reference/peer-cli-capabilities.md` — add matrix row + per-peer section citing the Step 1 verification evidence.
-4. Edit `scripts/lib/peer-cli/registry.cjs` — append to `CAPABILITY_MATRIX` (and `KNOWN_PEERS` if separate).
+2. Edit `scripts/lib/install/runtimes.cjs` - add `peerBinary` field (platform-aware: `<peer-binary>.cmd` on Windows, plain on POSIX).
+3. Edit `reference/peer-cli-capabilities.md` - add matrix row + per-peer section citing the Step 1 verification evidence.
+4. Edit `scripts/lib/peer-cli/registry.cjs` - append to `CAPABILITY_MATRIX` (and `KNOWN_PEERS` if separate).
 
-### Step 4 — Verification gate
+### Step 4 - Verification gate
 
-Run the four-check gate in `./peer-cli-protocol.md` §"Verification gate": `tsc --noEmit`, peer-cli tests, reference-registry round-trip, frontmatter validator. Any failure — surface error + offer revert.
+Run the four-check gate in `./peer-cli-protocol.md` §"Verification gate": `tsc --noEmit`, peer-cli tests, reference-registry round-trip, frontmatter validator. Any failure - surface error + offer revert.
 
-### Step 5 — Surface the summary
+### Step 5 - Surface the summary
 
 ```
 ## peer-cli-add summary