@hegemonart/get-design-done 1.42.0 → 1.43.0

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

@@ -1,12 +1,12 @@
 ---
 name: start
-description: "First-Run Proof Path — one command that scans your UI code and returns one concrete first fix. Leaf command, no STATE.md writes, no pipeline entry. Writes .design/START-REPORT.md and exits."
+description: "First-Run Proof Path - one command that scans your UI code and returns one concrete first fix. Leaf command, no STATE.md writes, no pipeline entry. Writes .design/START-REPORT.md and exits."
 argument-hint: "[--budget <fast|balanced|thorough>] [--skip-interview] [--dismiss-nudge]"
 tools: Read, Grep, Glob, Bash, Write, Task
 disable-model-invocation: true
 ---
 
-# Get Design Done — /gdd:start
+# Get Design Done - /gdd:start
 
 **Role:** the canonical 0→1 proof path. A new user runs `/gdd:start`, answers five short questions, and receives `.design/START-REPORT.md` with three concrete findings in the user's own code, one `best_first_proof` selected by a deterministic rubric, and a single next command to run.
 
@@ -21,9 +21,9 @@ disable-model-invocation: true
 
 ## When NOT to use
 
-- `.design/STATE.md` already exists — route to `/gdd:progress` instead.
-- User asked for a full audit — route to `/gdd:scan`.
-- User asked to fix a specific file — route to `/gdd:fast`.
+- `.design/STATE.md` already exists - route to `/gdd:progress` instead.
+- User asked for a full audit - route to `/gdd:scan`.
+- User asked to fix a specific file - route to `/gdd:fast`.
 
 ---
 
@@ -52,7 +52,7 @@ Six steps, all documented in `./start-procedure.md`. Companion file `./reference
 | 4 | Spawn `design-start-writer` Task → emit `.design/START-REPORT.md` (7 H2 sections + JSON block, no STATE.md write) | `start-procedure.md#step-4-spawn-the-writer` |
 | 5 | Print one-line handoff with suggested command (fallback: `/gdd:brief` if `bestFirstProofId` is null); emit `## START COMPLETE` | `start-procedure.md#step-5-print-the-handoff` |
 
-Failure handling: every error path exits with `## START COMPLETE` plus a one-line pointer. Do not half-write files — if the writer fails, keep `.design/.start-context.json` and tell the user they can rerun. Do not delete `.design/` unless it was empty before the run.
+Failure handling: every error path exits with `## START COMPLETE` plus a one-line pointer. Do not half-write files - if the writer fails, keep `.design/.start-context.json` and tell the user they can rerun. Do not delete `.design/` unless it was empty before the run.
 
 ---
 
@@ -61,7 +61,7 @@ Failure handling: every error path exits with `## START COMPLETE` plus a one-lin
 - Do not write or mutate `.design/STATE.md`.
 - Do not modify source code.
 - Do not auto-install MCPs or write to `.design/config.json`.
-- Do not take more than the budgeted wall-clock — let the engine truncate findings rather than hang.
-- Do not invent findings — the findings engine output is the sole source of truth.
+- Do not take more than the budgeted wall-clock - let the engine truncate findings rather than hang.
+- Do not invent findings - the findings engine output is the sole source of truth.
 
 ## START COMPLETE

package/dist/claude-code/.claude/skills/start/start-procedure.md

@@ -7,7 +7,7 @@ tags: [start, first-run, proof-path, scan, writer-agent, handoff]
 last_updated: 2026-05-18
 ---
 
-# Start Skill — Full Procedure
+# Start Skill - Full Procedure
 
 Extracted from `skills/start/SKILL.md` per Phase 28.5 D-10 (extract-then-link, never delete
 content). The skill keeps its arguments table, step headings, and non-goals; the per-step
@@ -17,7 +17,7 @@ template) lives here so the SKILL stays under the 100-line cap.
 The companion file `./start-interview.md` (Phase 27 ship) holds the 5-question copy,
 defaults, and validation rules. This file documents what `/gdd:start` does WITH the answers.
 
-## Step 0 — Dismiss-only shortcut
+## Step 0 - Dismiss-only shortcut
 
 If invoked with `--dismiss-nudge`:
 
@@ -27,7 +27,7 @@ If invoked with `--dismiss-nudge`:
 
 Do not proceed to any other step.
 
-## Step 1 — Detect UI root
+## Step 1 - Detect UI root
 
 Run the detector:
 
@@ -38,11 +38,11 @@ node "${CLAUDE_PLUGIN_ROOT}/scripts/lib/detect-ui-root.cjs" "$(pwd)"
 Capture the JSON output. Branches:
 
 - `kind: "backend-only"` → print the frontend-only diagnostic below, write nothing, exit with `## START COMPLETE`. The diagnostic copy is:
-  > `/gdd:start` is for frontend codebases. This repo looks backend-only (detected `<framework>`). The plugin can still help with design references and component libraries imported by your clients — but there is no UI surface here to scan. Exiting without creating `.design/`.
-- `kind: null` (no package.json, no UI dir) → print a short "Nothing recognizable here — point me at a frontend repo and try again." and exit.
+  > `/gdd:start` is for frontend codebases. This repo looks backend-only (detected `<framework>`). The plugin can still help with design references and component libraries imported by your clients - but there is no UI surface here to scan. Exiting without creating `.design/`.
+- `kind: null` (no package.json, no UI dir) → print a short "Nothing recognizable here - point me at a frontend repo and try again." and exit.
 - Any other `kind` → proceed with `detected.path` as the scan root.
 
-## Step 2 — Run the 5-question interview
+## Step 2 - Run the 5-question interview
 
 Read `./start-interview.md` for the exact question copy, defaults, and validation rules.
 
@@ -71,7 +71,7 @@ Store the answers + detection result in `.design/.start-context.json`:
 
 `.design/` is created here for the first time. `.design/STATE.md` is NOT written.
 
-## Step 3 — Scan findings
+## Step 3 - Scan findings
 
 Run the findings engine:
 
@@ -86,7 +86,7 @@ Capture the JSON. The output carries at most three findings, each with stable ID
 
 Append the engine output to `.design/.start-context.json` under a `scan` key.
 
-## Step 4 — Spawn the writer
+## Step 4 - Spawn the writer
 
 Dispatch `Task` with:
 
@@ -96,7 +96,7 @@ Dispatch `Task` with:
 
 Wait for the agent to complete. The agent writes `.design/START-REPORT.md`.
 
-## Step 5 — Print the handoff
+## Step 5 - Print the handoff
 
 Read the final line of `.design/START-REPORT.md` to capture the suggested command.
 

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

@@ -1,6 +1,6 @@
 ---
 name: gdd-stats
-description: "Cycle stats — decisions made, tasks completed, commits, timeline, git metrics."
+description: "Cycle stats - decisions made, tasks completed, commits, timeline, git metrics."
 tools: Read, Bash
 disable-model-invocation: true
 ---
@@ -9,13 +9,13 @@ disable-model-invocation: true
 
 **Role:** Print cycle metrics.
 
-## Step 1 — Read state
+## Step 1 - Read state
 
 Read `.design/STATE.md`. Extract:
 - `cycle:` and `started_at` (or per-cycle start date if present in CYCLES.md)
 - D-XX count under `<decisions>`
 
-## Step 2 — Collect git metrics
+## Step 2 - Collect git metrics
 
 Let `<since>` = cycle start date (fallback to STATE.md `started_at`).
 
@@ -26,7 +26,7 @@ git diff --stat HEAD~N HEAD                          # files changed since cycle
 
 If git unavailable, print `git: unavailable` and skip git metrics.
 
-## Step 3 — Count todos
+## Step 3 - Count todos
 
 Read `.design/TODO.md` if present:
 - pending: count `- [ ]`
@@ -34,7 +34,7 @@ Read `.design/TODO.md` if present:
 - done: count `- [x]`
 - group pending by P0/P1/P2/P3 section
 
-## Step 4 — Output
+## Step 4 - Output
 
 ```
 ━━━ Cycle stats ━━━

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

@@ -5,13 +5,13 @@ argument-hint: "[ComponentName]"
 user-invocable: true
 ---
 
-# gdd-style — Component Handoff Doc Generator
+# gdd-style - Component Handoff Doc Generator
 
 Generates a per-component style spec at `.design/DESIGN-STYLE-[ComponentName].md`. This is a **standalone command**, not a pipeline stage.
 
 For the full mode-detection logic, source-resolution fallback chain (10 paths), agent-spawn payload, and STYL-05 section spec, see `./style-doc-procedure.md`. For the cross-skill output discipline (artifact prefix, completion marker, MUST-NOT-write list), see `../../reference/shared-preamble.md#output-contract-reminders`. For the raw-hex audit signal used in Token Semantic Health Score, see `../../reference/shared-preamble.md#token-first-reasoning`.
 
-Output artifact naming: `.design/DESIGN-STYLE-[ComponentName].md` — Title-cased component name, one file per invocation.
+Output artifact naming: `.design/DESIGN-STYLE-[ComponentName].md` - Title-cased component name, one file per invocation.
 
 ---
 
@@ -19,11 +19,11 @@ Output artifact naming: `.design/DESIGN-STYLE-[ComponentName].md` — Title-case
 
 This command is **additive and non-destructive**:
 
-- It is NOT a pipeline stage — no `.design/STATE.md` read or write contract.
-- Output lives in the `DESIGN-STYLE-*.md` namespace — distinct from the pipeline namespace (`DESIGN.md`, `DESIGN-CONTEXT.md`, `DESIGN-PLAN.md`, `DESIGN-SUMMARY.md`, `DESIGN-VERIFICATION.md`).
+- It is NOT a pipeline stage - no `.design/STATE.md` read or write contract.
+- Output lives in the `DESIGN-STYLE-*.md` namespace - distinct from the pipeline namespace (`DESIGN.md`, `DESIGN-CONTEXT.md`, `DESIGN-PLAN.md`, `DESIGN-SUMMARY.md`, `DESIGN-VERIFICATION.md`).
 - It does not modify any pipeline artifact.
 - It does not invoke the pipeline router.
-- One doc per invocation — no batch mode in v3.
+- One doc per invocation - no batch mode in v3.
 
 This separation is a pre-roadmap decision recorded in `.planning/STATE.md`: utility commands use distinct prefixes (`DESIGN-STYLE-[Component].md`); the pipeline owns the `DESIGN-*.md` namespace without qualifiers.
 
@@ -31,11 +31,11 @@ This separation is a pre-roadmap decision recorded in `.planning/STATE.md`: util
 
 ## Workflow
 
-1. **Argument check** — if `$ARGUMENTS` is empty, enter list mode (see `./style-doc-procedure.md#component-source-resolution`); display available components from `src/components/` + `.design/tasks/`, then exit.
-2. **Mode detect** — `DESIGN-SUMMARY.md` exists → post-pipeline; else `DESIGN.md` exists → pre-pipeline; else abort with a "run /get-design-done scan first" message. Full decision tree at `./style-doc-procedure.md#mode-detection`.
-3. **Source resolve** — search the 10-path fallback chain for a file matching the ComponentName. On zero matches: abort. On multiple matches: prompt the user to disambiguate.
-4. **Agent spawn** — dispatch `design-doc-writer` with the mode-specific `<required_reading>` block and the STYL-05 section list. The full Task payload + STYL-05 spec live in `./style-doc-procedure.md#agent-spawn-payload`.
-5. **Confirm + report** — after the agent emits `## DOC COMPLETE`, verify the output path exists and report success.
+1. **Argument check** - if `$ARGUMENTS` is empty, enter list mode (see `./style-doc-procedure.md#component-source-resolution`); display available components from `src/components/` + `.design/tasks/`, then exit.
+2. **Mode detect** - `DESIGN-SUMMARY.md` exists → post-pipeline; else `DESIGN.md` exists → pre-pipeline; else abort with a "run /get-design-done scan first" message. Full decision tree at `./style-doc-procedure.md#mode-detection`.
+3. **Source resolve** - search the 10-path fallback chain for a file matching the ComponentName. On zero matches: abort. On multiple matches: prompt the user to disambiguate.
+4. **Agent spawn** - dispatch `design-doc-writer` with the mode-specific `<required_reading>` block and the STYL-05 section list. The full Task payload + STYL-05 spec live in `./style-doc-procedure.md#agent-spawn-payload`.
+5. **Confirm + report** - after the agent emits `## DOC COMPLETE`, verify the output path exists and report success.
 
 ---
 
@@ -45,8 +45,8 @@ This command MUST NOT (per `../../reference/shared-preamble.md#output-contract-r
 
 - Write to `DESIGN.md`, `DESIGN-SUMMARY.md`, `DESIGN-VERIFICATION.md`, `DESIGN-CONTEXT.md`, or `.design/STATE.md`
 - Invoke the pipeline router (this command is a leaf invocation, not a pipeline stage)
-- Require Figma or Refero MCPs — v3 uses only local source files and `.design/` artifacts (MCP enrichment is reserved for a future version)
-- Produce more than one output file per invocation — no batch mode in v3
+- Require Figma or Refero MCPs - v3 uses only local source files and `.design/` artifacts (MCP enrichment is reserved for a future version)
+- Produce more than one output file per invocation - no batch mode in v3
 
 ---
 

package/dist/claude-code/.claude/skills/style/style-doc-procedure.md

@@ -7,17 +7,17 @@ tags: [style, handoff, component-spec, doc-writer, procedure, extracted]
 last_updated: 2026-05-18
 ---
 
-Source: extracted from `skills/style/SKILL.md` (Phase 28.5 rework — D-10 extract-then-link).
-The skill's load-bearing routing + mode-detection stays in `../skills/style/SKILL.md`; this file
+Source: extracted from `skills/style/SKILL.md` (Phase 28.5 rework - D-10 extract-then-link).
+The skill's essential routing + mode-detection stays in `../skills/style/SKILL.md`; this file
 holds the agent-spawn payload, source-resolution paths, and the per-section spec the
 `design-doc-writer` agent produces. See `./shared-preamble.md#output-contract-reminders` for
 the cross-skill output discipline.
 
 # Style Doc Procedure
 
-Detailed procedure for the `gdd-style` standalone command — companion to
+Detailed procedure for the `gdd-style` standalone command - companion to
 `../skills/style/SKILL.md`. Read this file when executing the agent-spawn step (Step 4 in the
-skill) or when wiring the source-resolution fallback chain. The SKILL.md keeps the load-bearing
+skill) or when wiring the source-resolution fallback chain. The SKILL.md keeps the essential
 mode detection + decision tree; this file holds the deep methodology.
 
 ---
@@ -60,7 +60,7 @@ Search for a source file matching the provided ComponentName (case-insensitive):
 
 **If zero matches found:** Abort with: "Component [ComponentName] not found in expected paths. Verify the name matches a file in src/components/ or components/."
 
-When `$ARGUMENTS` is empty, the skill enters **list mode** — glob the same source roots, also list task names from `.design/tasks/*.md` (if directory exists), display the list, and prompt the user to specify a ComponentName. Exit without generating any file.
+When `$ARGUMENTS` is empty, the skill enters **list mode** - glob the same source roots, also list task names from `.design/tasks/*.md` (if directory exists), display the list, and prompt the user to specify a ComponentName. Exit without generating any file.
 
 ---
 
@@ -113,13 +113,13 @@ After the agent emits `## DOC COMPLETE`, confirm the file exists at `output_path
 
 Each generated `.design/DESIGN-STYLE-[ComponentName].md` SHOULD contain (in this order):
 
-1. **Spacing Tokens** — every spacing token the component uses (paddings, gaps, margins). Cross-reference `./composition.md` for the 4 px / 8 px modular scale discipline.
-2. **Color Tokens** — every color token the component uses (background, foreground, border, focus ring, state-overlays). Cross-reference `./palette-catalog.md` for naming convention and `./shared-preamble.md#token-first-reasoning` for the raw-hex audit threshold.
-3. **Typography Scale** — type ramps the component reaches into (label, body, code, etc.) with size + line-height + weight. Cross-reference `./typography.md`.
-4. **Component States** — default, hover, focus, active, disabled, loading, error. Each row: token diff vs default.
-5. **Token Semantic Health Score** — raw-hex ratio = `raw_hex_count / total_color_uses`. Healthy < 5 %.
-6. **AI-Slop Detection** — apply `./anti-patterns.md` `BAN-*` and `SLOP-*` patterns to the component source. List violations.
-7. **Decisions Applied** (post-pipeline only) — D-XX entries from `DESIGN-SUMMARY.md` that name or describe this component.
+1. **Spacing Tokens** - every spacing token the component uses (paddings, gaps, margins). Cross-reference `./composition.md` for the 4 px / 8 px modular scale discipline.
+2. **Color Tokens** - every color token the component uses (background, foreground, border, focus ring, state-overlays). Cross-reference `./palette-catalog.md` for naming convention and `./shared-preamble.md#token-first-reasoning` for the raw-hex audit threshold.
+3. **Typography Scale** - type ramps the component reaches into (label, body, code, etc.) with size + line-height + weight. Cross-reference `./typography.md`.
+4. **Component States** - default, hover, focus, active, disabled, loading, error. Each row: token diff vs default.
+5. **Token Semantic Health Score** - raw-hex ratio = `raw_hex_count / total_color_uses`. Healthy < 5 %.
+6. **AI-Slop Detection** - apply `./anti-patterns.md` `BAN-*` and `SLOP-*` patterns to the component source. List violations.
+7. **Decisions Applied** (post-pipeline only) - D-XX entries from `DESIGN-SUMMARY.md` that name or describe this component.
 
 ---
 

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

@@ -1,6 +1,6 @@
 ---
 name: synthesize
-description: "Streaming synthesizer — collapses N parallel-agent markdown outputs into one compact merged summary via a single Haiku 4.5 call. Invoked inline by orchestrators (skills/map/, skills/discover/, skills/plan/) after parallel spawns return. Not user-invocable."
+description: "Streaming synthesizer - collapses N parallel-agent markdown outputs into one compact merged summary via a single Haiku 4.5 call. Invoked inline by orchestrators (skills/map/, skills/discover/, skills/plan/) after parallel spawns return. Not user-invocable."
 tools: Read, Task
 user-invocable: false
 disable-model-invocation: true
@@ -12,7 +12,7 @@ disable-model-invocation: true
 
 ## Role
 
-Reusable streaming synthesizer. You receive N markdown strings (parallel-agent outputs) plus a directive, emit one compact merged output in the format the directive specifies. Inline-invoked — no Task() spawn overhead; thin Haiku 4.5 merge call wrapped in a skill.
+Reusable streaming synthesizer. You receive N markdown strings (parallel-agent outputs) plus a directive, emit one compact merged output in the format the directive specifies. Inline-invoked - no Task() spawn overhead; thin Haiku 4.5 merge call wrapped in a skill.
 
 You are not an orchestrator, not an auditor, not a second-pass reviewer. You preserve every distinct signal from the inputs, consolidate duplicates with source tags, and return a single merged artifact. The invoking orchestrator writes the result to disk; you do not touch the filesystem.
 
@@ -21,7 +21,7 @@ You are not an orchestrator, not an auditor, not a second-pass reviewer. You pre
 **Use synthesize when:**
 - Parallel-mapper / parallel-researcher produced N overlapping outputs and main-context doesn't need them verbatim.
 - The downstream consumer wants one cross-cutting summary (e.g., `.design/DESIGN-PATTERNS.md` merged from 5 per-concern mappers).
-- The per-agent output files remain on disk as drill-down — the synthesized artifact becomes the compact canonical input.
+- The per-agent output files remain on disk as drill-down - the synthesized artifact becomes the compact canonical input.
 
 **Do NOT use synthesize when:**
 - A single-agent flow produced the output (nothing to merge).
@@ -32,9 +32,9 @@ You are not an orchestrator, not an auditor, not a second-pass reviewer. You pre
 
 The invoking orchestrator passes three fields:
 
-- `outputs: string[]` — N labeled strings, each pre-labeled with `=== from <agent-name> ===\n<content>` so the merge call can trace per-signal provenance.
-- `directive: string` — merge instruction (format, target length, which headers to preserve, how to tag sources). Default when empty: `"produce a single merged summary preserving all distinct signals, grouped by natural section headers"`.
-- `output_shape: "markdown" | "json"` — controls the output format. Defaults to `"markdown"`.
+- `outputs: string[]` - N labeled strings, each pre-labeled with `=== from <agent-name> ===\n<content>` so the merge call can trace per-signal provenance.
+- `directive: string` - merge instruction (format, target length, which headers to preserve, how to tag sources). Default when empty: `"produce a single merged summary preserving all distinct signals, grouped by natural section headers"`.
+- `output_shape: "markdown" | "json"` - controls the output format. Defaults to `"markdown"`.
 
 ## Implementation
 
@@ -57,7 +57,7 @@ requests section preservation.
 Emit ONLY the merged output — no preamble, no meta-commentary.
 ```
 
-Tier is hard-coded to `haiku` per D-14. Orchestrators should **not** re-route this to Sonnet — the merge is structure-preserving, not generative, and Haiku handles it without quality loss.
+Tier is hard-coded to `haiku` per D-14. Orchestrators should **not** re-route this to Sonnet - the merge is structure-preserving, not generative, and Haiku handles it without quality loss.
 
 ## Output Contract
 
@@ -71,11 +71,11 @@ The orchestrator is responsible for:
 
 ## Cost and Tier
 
-Hard-coded to Haiku 4.5 per D-14. `budget.json.tier_overrides.synthesize` can override. Typical cost per invocation: $0.002–$0.02 — dominated by input tokens (5 × ~1500-line mapper outputs ≈ 7.5k input tokens, merge output ≈ 1k output tokens).
+Hard-coded to Haiku 4.5 per D-14. `budget.json.tier_overrides.synthesize` can override. Typical cost per invocation: $0.002–$0.02 - dominated by input tokens (5 × ~1500-line mapper outputs ≈ 7.5k input tokens, merge output ≈ 1k output tokens).
 
 ## Failure Modes
 
-- **Empty `outputs: []`** → emit an empty string followed immediately by `## SYNTHESIS COMPLETE`. Do NOT error — the orchestrator handles the empty case (e.g., `--only <name>` in map skipped the parallel dispatch).
+- **Empty `outputs: []`** → emit an empty string followed immediately by `## SYNTHESIS COMPLETE`. Do NOT error - the orchestrator handles the empty case (e.g., `--only <name>` in map skipped the parallel dispatch).
 - **Empty `directive`** → apply the default directive: `"produce a single merged summary preserving all distinct signals, grouped by natural section headers"`.
 - **Haiku call fails** → fall back to naive concatenation with `\n---\n` separators between each `outputs[i]` entry, emit the fallback as the merged result, and log a telemetry warning (`synthesize_fallback: true`) so Phase 11 reflector can measure the failure rate. Always emit `## SYNTHESIS COMPLETE` after the fallback body.
 - **`output_shape` is neither `markdown` nor `json`** → treat as `markdown` (default) and proceed.
@@ -84,7 +84,7 @@ Hard-coded to Haiku 4.5 per D-14. `budget.json.tier_overrides.synthesize` can ov
 
 - Does **NOT** spawn Task() agents. Synthesize is a thin skill, not an orchestrator.
 - Does **NOT** write files. The invoking orchestrator owns the target path.
-- Does **NOT** validate directive semantics. If the directive is nonsensical, the merge output will reflect that — garbage in, garbage out is acceptable for an internal-use skill.
+- Does **NOT** validate directive semantics. If the directive is nonsensical, the merge output will reflect that - garbage in, garbage out is acceptable for an internal-use skill.
 - Does **NOT** re-rank or re-score the inputs. Preservation is the contract.
 
 ## Completion Marker

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

@@ -16,14 +16,14 @@ Generates a narrative retrospective across one or more completed cycles by readi
 ## Steps
 
 1. **Parse argument**: accepted forms:
-   - `cycle-N` or `N` — single cycle
-   - `N-M` — inclusive range
-   - `all` or no argument — all archived cycles
+   - `cycle-N` or `N` - single cycle
+   - `N-M` - inclusive range
+   - `all` or no argument - all archived cycles
 
 2. **Discover archives**: glob `.design/archive/cycle-*/EXPERIENCE.md`. Sort by cycle number. Filter to requested range.
 
 3. **For each cycle archive**:
-   a. Read `EXPERIENCE.md` — extract sections: Goal, Decisions made, Learnings graduated, What died, Handoff to next cycle.
+   a. Read `EXPERIENCE.md` - extract sections: Goal, Decisions made, Learnings graduated, What died, Handoff to next cycle.
    b. Read `DESIGN-SUMMARY.md` (if present) for shipped artifacts list.
    c. Run:
       ```bash

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

@@ -1,6 +1,6 @@
 ---
 name: gdd-todo
-description: "Design backlog — add/list/pick design tasks. Writes to .design/TODO.md."
+description: "Design backlog - add/list/pick design tasks. Writes to .design/TODO.md."
 argument-hint: "<add|list|pick> [text]"
 tools: Read, Write, AskUserQuestion, mcp__gdd_state__get, mcp__gdd_state__add_decision, mcp__gdd_state__add_must_have
 disable-model-invocation: true
@@ -8,7 +8,7 @@ disable-model-invocation: true
 
 # /gdd:todo
 
-**Role:** Design todo list. Three subcommands: `add`, `list`, `pick`. Backing store: `.design/TODO.md`. For items that are pipeline-level decisions or must-haves (not free-form backlog), route through the `gdd-state` MCP tools instead — see **Pipeline-linked items** below.
+**Role:** Design todo list. Three subcommands: `add`, `list`, `pick`. Backing store: `.design/TODO.md`. For items that are pipeline-level decisions or must-haves (not free-form backlog), route through the `gdd-state` MCP tools instead - see **Pipeline-linked items** below.
 
 ## File format
 
@@ -59,6 +59,6 @@ When the user promotes a todo to a pipeline decision or must-have, route through
 
 - Do not modify files outside `.design/`.
 - Preserve existing sections and ordering on write.
-- Do not mutate STATE.md directly — use the MCP tools above.
+- Do not mutate STATE.md directly - use the MCP tools above.
 
 ## TODO COMPLETE

package/dist/claude-code/.claude/skills/turn-closeout/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: gdd-turn-closeout
 description: "Portable mirror of the gdd-turn-closeout Stop hook (D-11). Closes the events.jsonl gap at turn-end and surfaces a stage-completion or paused-mid-task nudge. Tail-called by orchestrator skills (/gdd:next, /gdd:design, /gdd:verify) at exit on the 13 non-Claude runtimes that lack a Stop hook surface. Idempotent, non-blocking, ≤10ms typical."
-argument-hint: "(none — reads .design/STATE.md and .design/telemetry/events.jsonl from cwd)"
+argument-hint: "(none - reads .design/STATE.md and .design/telemetry/events.jsonl from cwd)"
 tools: Read, Bash
 ---
 
@@ -11,12 +11,12 @@ tools: Read, Bash
 
 You are a deterministic **closeout** skill. You close the per-turn telemetry gap on runtimes that don't expose a Stop event (codex, gemini, and 11 others). You are a code-level mirror of `hooks/gdd-turn-closeout.js` (D-10): same conditions, same idempotence, same emitted event shape. The only difference: the JS hook emits the nudge as `additionalContext` via the harness; this skill prints the nudge directly to the user. See `./../new-cycle/milestone-completeness-rubric.md` §"Task level" for the broader closeout discipline (what "turn complete" means within a stage).
 
-**When to invoke:** orchestrator skills (`/gdd:next`, `/gdd:design`, `/gdd:verify`) tail-call this skill as their final step before returning. Adoption is incremental — each orchestrator can wire the tail-call independently; the skill exists as a stable, callable surface today.
+**When to invoke:** orchestrator skills (`/gdd:next`, `/gdd:design`, `/gdd:verify`) tail-call this skill as their final step before returning. Adoption is incremental - each orchestrator can wire the tail-call independently; the skill exists as a stable, callable surface today.
 
 ## Invocation Contract
 
 - **Input**: none. Operates on `.design/STATE.md` and `.design/telemetry/events.jsonl` in cwd.
-- **Output**: at most one printed line — the nudge — or silent return.
+- **Output**: at most one printed line - the nudge - or silent return.
 - **Latency budget**: ≤10ms typical. Read **only** STATE.md and the tail of events.jsonl.
 - **Idempotence**: if the most recent event is already a `turn_end` for the current `(stage, task_progress)` tuple, skip append but still print nudge.
 - **Non-blocking**: any I/O failure → silent return. This skill never gates the user.
@@ -25,17 +25,17 @@ You are a deterministic **closeout** skill. You close the per-turn telemetry gap
 
 Execute in order; stop at the first early-return.
 
-### Step 1 — Read STATE.md
+### Step 1 - Read STATE.md
 
 Read `.design/STATE.md`. Missing or unreadable → **return silently** (no print, no append).
 
-### Step 2 — Parse `<position>` block
+### Step 2 - Parse `<position>` block
 
 Lightweight-parse only `<position>…</position>` (regex `/<position>([\s\S]*?)<\/position>/` then per-line `key: value`). Extract `stage`, `status`, `task_progress`. Do not invoke the full STATE parser.
 
-If `status != "in_progress"` → **return silently**. Pipeline is initialized / completed / blocked — no turn-end gap to close.
+If `status != "in_progress"` → **return silently**. Pipeline is initialized / completed / blocked - no turn-end gap to close.
 
-### Step 3 — Tail the last event line
+### Step 3 - Tail the last event line
 
 Read **only the last 8 KiB** of `.design/telemetry/events.jsonl`. Treat as "stale by definition":
 
@@ -46,7 +46,7 @@ Read **only the last 8 KiB** of `.design/telemetry/events.jsonl`. Treat as "stal
 
 Otherwise compute `now - last_event.timestamp`. Gap < 60 seconds → user is actively mid-turn → **return silently** (next real event closes the gap naturally). Bash one-liner for the tail: `tail -n 1 .design/telemetry/events.jsonl 2>/dev/null`.
 
-### Step 4 — Idempotence check, then append
+### Step 4 - Idempotence check, then append
 
 If last event is already `{type:"turn_end", stage:<same>, payload:{task_progress:<same>}}` for the exact `(stage, task_progress)` from Step 2: **skip append** but proceed to Step 5.
 
@@ -58,14 +58,14 @@ Otherwise append one JSONL line to `.design/telemetry/events.jsonl`:
 
 Create `.design/telemetry/` if missing. Append is a single `appendFile`-equivalent call (writer assumes append-atomicity per Plan 20-06).
 
-### Step 5 — Print the nudge
+### Step 5 - Print the nudge
 
 Match `task_progress` against `^(\d+)/(\d+)$`:
 
 - **Numerator equals denominator and denominator > 0** (e.g. `5/5`): `Stage <stage> complete — run /gdd:next or /gdd:reflect`.
 - **Otherwise** (mid-task, e.g. `3/7`, `0/0`, malformed): `Stage <stage> paused mid-task — resume with /gdd:resume`.
 
-One line exactly. No commentary — the nudge is the user-facing surface.
+One line exactly. No commentary - the nudge is the user-facing surface.
 
 ## Failure Modes
 

package/dist/claude-code/.claude/skills/unlock-decision/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: gdd-unlock-decision
-description: "Reopens a LOCKED design decision — the only escape hatch from the hard lock. Requires an explicit --approver and writes an audit entry, then moves the decision locked → reviewing (via scripts/lib/collab/review-queue.cjs). Previews the audit record before writing; never unlocks silently. Use when a locked decision genuinely must change (a later constraint invalidated it) and a reviewer has signed off."
+description: "Reopens a LOCKED design decision - the only escape hatch from the hard lock. Requires an explicit --approver and writes an audit entry, then moves the decision locked → reviewing (via scripts/lib/collab/review-queue.cjs). Previews the audit record before writing; never unlocks silently. Use when a locked decision genuinely must change (a later constraint invalidated it) and a reviewer has signed off."
 argument-hint: "<decision-id> --approver <who> [--reason <text>] [--dry-run]"
 user-invocable: true
 tools: Read, Write, Bash, Grep, Glob
@@ -8,7 +8,7 @@ tools: Read, Write, Bash, Grep, Glob
 
 # /gdd:unlock-decision
 
-A `locked` decision is hard — it cannot be amended. This skill is the **only** way back, and it is
+A `locked` decision is hard - it cannot be amended. This skill is the **only** way back, and it is
 deliberately heavyweight: it requires a named approver and records an audit entry, so reopening a
 locked decision is always traceable. Contract: `../../reference/multi-author-model.md`.
 
@@ -27,7 +27,7 @@ locked decision is always traceable. Contract: `../../reference/multi-author-mod
 2. **Load the entry** from `.design/reviews/<decision-id>/state.json`. Not found → report it. Not in
    `locked` state → print `unlock-decision: <id> is not locked (state: <state>); nothing to unlock.`
 3. **Preview.** Show the audit entry that will be appended (`{ action: unlock, from: locked, to:
-   reviewing, approver, reason }`) and the resulting state. If `--dry-run`, stop here.
+   reviewing, approver, reason }`) and the resulting state. If ``--dry-run``, stop here.
 4. **Apply** via the pure helper:
 
    ```bash

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

@@ -12,18 +12,18 @@ Updates the `get-design-done` plugin to the latest release (or a specific tag),
 
 ## Steps
 
-1. **Pre-flight check** — read current version from `.claude-plugin/plugin.json` (fallback: `plugin.json` at project root). Print current version and, when available, the latest release tag from GitHub.
-2. **Dry-run** — if `--dry-run` is passed, print the planned steps and exit without making changes.
-3. **Backup** — read `.design/config.json` into memory. Snapshot the file list under `./.claude/skills/` so we can detect collisions later. **Additionally, snapshot the text contents of `scripts/lib/pseudonymize.cjs`, `scripts/lib/issue-reporter/payload-assembly.cjs`, and `scripts/lib/issue-reporter/destination.cjs` to a tempdir (mirroring the same relative paths under that tempdir's root). This is the OLD tree used by the privacy-diff step below. Also read the previous-version string from `.design/privacy-diff-last-version.txt` if it exists, into a variable `prevVersion` (null if the file is absent).** (Plan 30-07 D-09)
-4. **Pull update** — run `claude plugin install hegemonart/get-design-done` (or `claude plugin install hegemonart/get-design-done@<tag>` when `--version <tag>` is passed). This re-syncs all plugin files from the release.
-5. **Restore config** — write `.design/config.json` back from the in-memory backup. The installer may reset the config to defaults; this step guarantees user settings survive.
-5.5. **Privacy diff** — `const pd = require('./scripts/lib/issue-reporter/privacy-diff.cjs');` Compute `showDiff = pd.shouldAutoShow(prevVersion, currentVersion, oldTreeTempdir, repoRoot) || flags.showPrivacyDiff`. If `showDiff` is true: call `pd.computePrivacyDiff(oldTreeTempdir, repoRoot)`, pass the result to `pd.renderPrivacyDiff`, and print the returned markdown to stdout under a clear "## Privacy-critical changes" banner. If `--show-privacy-diff` was passed but `prevVersion === null` (first-ever upgrade), print: "Privacy diff requested but no previous version is recorded. Snapshot file `.design/privacy-diff-last-version.txt` will be written now; the next upgrade will be able to diff against this version." After printing (or skipping), write `currentVersion` to `.design/privacy-diff-last-version.txt` so the next upgrade compares against THIS version. (Plan 30-07 D-09)
-6. **Preserve local skills** — `./.claude/skills/` is project-local and outside the plugin tree. Re-list the directory and confirm none of the pre-update files disappeared. Warn loudly if any did.
-7. **Post-update advisory** — print:
+1. **Pre-flight check** - read current version from `.claude-plugin/plugin.json` (fallback: `plugin.json` at project root). Print current version and, when available, the latest release tag from GitHub.
+2. **Dry-run** - if `--dry-run` is passed, print the planned steps and exit without making changes.
+3. **Backup** - read `.design/config.json` into memory. Snapshot the file list under `./.claude/skills/` so we can detect collisions later. **Additionally, snapshot the text contents of `scripts/lib/pseudonymize.cjs`, `scripts/lib/issue-reporter/payload-assembly.cjs`, and `scripts/lib/issue-reporter/destination.cjs` to a tempdir (mirroring the same relative paths under that tempdir's root). This is the OLD tree used by the privacy-diff step below. Also read the previous-version string from `.design/privacy-diff-last-version.txt` if it exists, into a variable `prevVersion` (null if the file is absent).** (Plan 30-07 D-09)
+4. **Pull update** - run `claude plugin install hegemonart/get-design-done` (or `claude plugin install hegemonart/get-design-done@<tag>` when `--version <tag>` is passed). This re-syncs all plugin files from the release.
+5. **Restore config** - write `.design/config.json` back from the in-memory backup. The installer may reset the config to defaults; this step guarantees user settings survive.
+5.5. **Privacy diff** - `const pd = require('./scripts/lib/issue-reporter/privacy-diff.cjs');` Compute `showDiff = pd.shouldAutoShow(prevVersion, currentVersion, oldTreeTempdir, repoRoot) || flags.showPrivacyDiff`. If `showDiff` is true: call `pd.computePrivacyDiff(oldTreeTempdir, repoRoot)`, pass the result to `pd.renderPrivacyDiff`, and print the returned markdown to stdout under a clear "## Privacy-critical changes" banner. If `--show-privacy-diff` was passed but `prevVersion === null` (first-ever upgrade), print: "Privacy diff requested but no previous version is recorded. Snapshot file `.design/privacy-diff-last-version.txt` will be written now; the next upgrade will be able to diff against this version." After printing (or skipping), write `currentVersion` to `.design/privacy-diff-last-version.txt` so the next upgrade compares against THIS version. (Plan 30-07 D-09)
+6. **Preserve local skills** - `./.claude/skills/` is project-local and outside the plugin tree. Re-list the directory and confirm none of the pre-update files disappeared. Warn loudly if any did.
+7. **Post-update advisory** - print:
 
    > Run `/gdd:reapply-patches` if you have customized any `reference/` files to restore your modifications.
 
-7.5. **Deprecation advisory** (Phase 39.5) — load the path-migration registry and report anything that
+7.5. **Deprecation advisory** (Phase 39.5) - load the path-migration registry and report anything that
    crossed into `deprecated` or `removed` over the `[prevVersion → currentVersion]` window:
 
    ```bash

package/dist/claude-code/.claude/skills/using-gdd/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: using-gdd
-description: "Use when starting any GDD session — establishes how to find and apply GDD skills."
+description: "Use when starting any GDD session - establishes how to find and apply GDD skills."
 disable-model-invocation: true
 ---
 <SUBAGENT-STOP>
@@ -14,37 +14,37 @@ first; it tells you how to find and apply the right GDD skill before you act.
 
 **If you think there is even a 1% chance a skill might apply, you ABSOLUTELY MUST invoke the skill.**
 
-In GDD, almost every request maps to a pipeline stage — brief, explore, plan, design,
-verify — or to a cross-cutting skill (discuss, audit, style, darkmode). When in doubt,
+In GDD, almost every request maps to a pipeline stage - brief, explore, plan, design,
+verify - or to a cross-cutting skill (discuss, audit, style, darkmode). When in doubt,
 search for and read the skill's body. The cost of reading a skill is trivial; the cost of
 free-handing a stage is rework, scope creep, and a broken pipeline state.
 
-## Red flags — Thought → Reality
+## Red flags - Thought → Reality
 
 When you catch yourself thinking any of the following, STOP and check for a skill.
 
 | Thought | Reality |
 | --- | --- |
 | This is just a simple design question. | Questions are tasks. Check for a skill. |
-| I'll just tweak the CSS directly. | Token changes go through the pipeline — check /gdd:design. |
+| I'll just tweak the CSS directly. | Token changes go through the pipeline - check /gdd:design. |
 | I already know the codebase, skip explore. | Explore probes connections you haven't re-checked this cycle. |
 | This change is too small to plan. | Plan-skipped tasks blow scope per cycle telemetry. Run /gdd:plan. |
-| I can write the brief later. | No brief means no shared problem statement — /gdd:brief comes first. |
+| I can write the brief later. | No brief means no shared problem statement - /gdd:brief comes first. |
 | The user clearly wants X, I'll skip discuss. | Ambiguity hides here. /gdd:discuss surfaces the real constraint. |
-| I'll verify by eyeballing it. | Verification is a stage with criteria — run /gdd:verify, don't guess. |
-| It's obviously a dark-mode tweak. | Color-scheme work has its own skill — check /gdd:darkmode. |
-| Let me just compare these two designs quickly. | Comparison is an audit task — /gdd:compare has the rubric. |
+| I'll verify by eyeballing it. | Verification is a stage with criteria - run /gdd:verify, don't guess. |
+| It's obviously a dark-mode tweak. | Color-scheme work has its own skill - check /gdd:darkmode. |
+| Let me just compare these two designs quickly. | Comparison is an audit task - /gdd:compare has the rubric. |
 | This is a one-off, no skill needed. | "One-off" is the most common rationalization in the telemetry. Check anyway. |
 | I'll refactor the style tokens by hand. | /gdd:style owns token edits so the pipeline stays consistent. |
-| The audit can wait until after I ship. | An un-audited cycle is an unverified cycle — /gdd:audit before close. |
+| The audit can wait until after I ship. | An un-audited cycle is an unverified cycle - /gdd:audit before close. |
 
 ## Skill priority order
 
 When more than one skill could apply, resolve in this order:
 
-1. **Process** — brief / explore / discuss. Establish the problem and context first.
-2. **Implementation** — design / style / darkmode. Only after process is settled.
-3. **Audit** — verify / compare / audit. Close the loop before declaring done.
+1. **Process** - brief / explore / discuss. Establish the problem and context first.
+2. **Implementation** - design / style / darkmode. Only after process is settled.
+3. **Audit** - verify / compare / audit. Close the loop before declaring done.
 
 Never run an Implementation skill before the Process skills that gate it have produced
 their artifact. Never declare a cycle complete without an Audit skill.
@@ -53,9 +53,9 @@ their artifact. Never declare a cycle complete without an Audit skill.
 
 When instructions conflict, obey this precedence (highest first):
 
-1. **The user's CLAUDE.md** — project- and user-level directives always win.
-2. **GDD skills** — the skill body is the source of truth for how a stage runs.
-3. **Defaults** — your own general training and habits come last.
+1. **The user's CLAUDE.md** - project- and user-level directives always win.
+2. **GDD skills** - the skill body is the source of truth for how a stage runs.
+3. **Defaults** - your own general training and habits come last.
 
 If a GDD skill contradicts the user's CLAUDE.md, the CLAUDE.md wins and you flag the
 conflict. If your instinct contradicts a GDD skill, the skill wins.
@@ -66,7 +66,7 @@ The core flow is **Brief → Explore → Plan → Design → Verify**, with bran
 
 - **Brief** captures the problem (`/gdd:brief`). Branch: a rough idea can sketch or spike
   off the brief before exploration; a changed problem loops back via `--re-brief`.
-- **Explore** scans the codebase and connections (`/gdd:explore`) — even on a familiar
+- **Explore** scans the codebase and connections (`/gdd:explore`) - even on a familiar
   repo, because connections drift each cycle.
 - **Plan** decomposes work into tasks (`/gdd:plan`). Skipping it is the top cause of scope
   blow-up; small tasks still get a plan.