@hegemonart/get-design-done 1.28.0 → 1.28.6

package/skills/style/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: get-design-done:style
-description: "Generate a component handoff doc (.design/DESIGN-STYLE-[ComponentName].md) from existing pipeline artifacts or source files. Two modes: post-pipeline (uses DESIGN-SUMMARY.md) and pre-pipeline fallback (uses DESIGN.md + source). Invoke with a ComponentName argument, or with no argument to list available components."
+description: "Generate a component handoff doc at `.design/DESIGN-STYLE-<ComponentName>.md` by dispatching the `design-doc-writer` agent in one of two modes: post-pipeline (uses `DESIGN-SUMMARY.md`) or pre-pipeline fallback (uses `DESIGN.md` + source). Use when the user wants a single-component spec covering tokens, states, and AI-slop detection. Invoke with a ComponentName, or with no argument to list available components."
 argument-hint: "[ComponentName]"
 user-invocable: true
 ---
@@ -9,6 +9,8 @@ user-invocable: true
 
 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.
 
 ---
@@ -27,134 +29,24 @@ This separation is a pre-roadmap decision recorded in `.planning/STATE.md`: util
 
 ---
 
-## Argument Handling
-
-**If `$ARGUMENTS` contains a ComponentName** → proceed to Mode Detection with that name.
-
-**If `$ARGUMENTS` is empty** → do not generate a doc. Instead:
-
-1. List available component files by globbing:
-   - `src/components/*.tsx`
-   - `src/components/*.jsx`
-   - `src/**/*.vue`
-   - `src/**/*.svelte`
-   - `components/*.tsx`
-   - `components/*.jsx`
-2. Also list task names from `.design/tasks/*.md` (if directory exists).
-3. Display the list to the user and prompt: "Specify a ComponentName to generate a style spec. Example: `/get-design-done style Button`"
-4. Exit without generating any file.
-
----
-
-## Mode Detection
-
-Before spawning the agent, detect which mode to use:
-
-```
-If .design/DESIGN-SUMMARY.md exists:
-  mode = post-pipeline   (STYL-03)
-  pipeline_complete = true
-
-Elif .design/DESIGN.md exists:
-  mode = pre-pipeline    (STYL-04)
-  pipeline_complete = false
-
-Else:
-  Abort: "No .design/ artifacts found. Run /get-design-done scan first to initialize."
-```
-
-The mode controls which files are supplied to the agent in `<required_reading>`.
-
----
-
-## Component Source Resolution
-
-Search for a source file matching the provided ComponentName (case-insensitive):
-
-1. `src/components/[ComponentName].tsx`
-2. `src/components/[ComponentName].jsx`
-3. `src/components/[ComponentName].vue`
-4. `src/components/[ComponentName].svelte`
-5. `src/**/[ComponentName]/index.tsx`
-6. `src/**/[ComponentName]/index.jsx`
-7. `components/[ComponentName].tsx`
-8. `components/[ComponentName].jsx`
-9. `components/[ComponentName].vue`
-10. `components/[ComponentName].svelte`
-
-**If multiple matches found:** Present the list to the user and prompt them to specify the exact path. Do not proceed until a single file is selected.
-
-**If zero matches found:** Abort with: "Component [ComponentName] not found in expected paths. Verify the name matches a file in src/components/ or components/."
-
----
-
-## Agent Spawn
-
-Once mode and source path are resolved, spawn the `design-doc-writer` agent:
-
-```
-Task("design-doc-writer", """
-<required_reading>
-[If pipeline_complete=true:]
-@.design/STATE.md
-@.design/DESIGN-SUMMARY.md
-@.design/DESIGN-CONTEXT.md
-@<component_source_path>
-[Else (pipeline_complete=false):]
-@.design/DESIGN.md
-@<component_source_path>
-@reference/anti-patterns.md
-@reference/audit-scoring.md
-</required_reading>
-
-Generate a handoff spec for component <ComponentName>.
-
-Context:
-  component_name: <ComponentName>
-  component_source_path: <resolved absolute path>
-  pipeline_complete: <true|false>
-  output_path: .design/DESIGN-STYLE-<ComponentName>.md
-
-Produce the doc per STYL-05 sections:
-  - Spacing Tokens (used by component)
-  - Color Tokens (used by component)
-  - Typography Scale (used by component)
-  - Component States (default, hover, focus, active, disabled, etc.)
-  - Token Semantic Health Score (raw-hex-ratio formula)
-  - AI-Slop Detection (using reference/anti-patterns.md BAN/SLOP patterns)
-  [If pipeline_complete=true:]
-  - Decisions Applied (D-XX from DESIGN-SUMMARY.md that mention this component)
-
-Emit ## DOC COMPLETE when the output file is written.
-""")
-```
-
-After the agent emits `## DOC COMPLETE`, confirm the file exists at `output_path` and report success to the user.
-
----
-
-## Output Location
-
-Output is written by the agent to:
-
-```
-.design/DESIGN-STYLE-[ComponentName].md
-```
-
-This artifact is **outside the pipeline namespace**. The `DESIGN-STYLE-` prefix is distinct from all pipeline-owned artifacts (`DESIGN.md`, `DESIGN-CONTEXT.md`, `DESIGN-PLAN.md`, `DESIGN-SUMMARY.md`, `DESIGN-VERIFICATION.md`). There is no naming conflict.
+## Workflow
 
-The `.design/` directory is gitignored (developer tooling only — not shipped with the plugin).
+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.
 
 ---
 
 ## Constraints
 
-This command MUST NOT:
+This command MUST NOT (per `../../reference/shared-preamble.md#output-contract-reminders`):
 
-- MUST NOT write to `DESIGN.md`, `DESIGN-SUMMARY.md`, `DESIGN-VERIFICATION.md`, `DESIGN-CONTEXT.md`, or `.design/STATE.md`
-- MUST NOT invoke the pipeline router (this command is a leaf invocation, not a pipeline stage)
-- MUST NOT require Figma or Refero MCPs — v3 uses only local source files and `.design/` artifacts (MCP enrichment is reserved for a future version)
-- MUST NOT produce more than one output file per invocation — no batch mode in v3
+- 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
 
 ---
 
@@ -166,12 +58,7 @@ This command MUST NOT:
 /get-design-done style Button
 ```
 
-- Resolves component: `src/components/Button.tsx`
-- Detects mode: DESIGN-SUMMARY.md exists → post-pipeline
-- Spawns `design-doc-writer` with `pipeline_complete: true`
-- Output: `.design/DESIGN-STYLE-Button.md`
-
----
+Resolves `src/components/Button.tsx`, detects post-pipeline mode (DESIGN-SUMMARY.md exists), spawns `design-doc-writer` with `pipeline_complete: true`, writes `.design/DESIGN-STYLE-Button.md`.
 
 **Example 2: No argument (list mode)**
 
@@ -179,15 +66,6 @@ This command MUST NOT:
 /get-design-done style
 ```
 
-- Globs component files from `src/components/`
-- Displays list to user:
-  ```
-  Available components:
-    Button
-    CardHeader
-    Input
-    Modal
-    Toast
-  Specify: /get-design-done style [ComponentName]
-  ```
-- Exits without generating any file.
+Globs component files and prompts the user to specify a ComponentName. Exits without generating any file. See `./style-doc-procedure.md#component-source-resolution` for the full glob path list.
+
+## STYLE COMPLETE

package/skills/style/style-doc-procedure.md

@@ -0,0 +1,150 @@
+---
+name: style-doc-procedure
+type: meta-rules
+version: 1.0.0
+phase: 28.5
+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
+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 `get-design-done: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
+mode detection + decision tree; this file holds the deep methodology.
+
+---
+
+## Mode Detection
+
+```
+If .design/DESIGN-SUMMARY.md exists:
+  mode = post-pipeline   (STYL-03)
+  pipeline_complete = true
+
+Elif .design/DESIGN.md exists:
+  mode = pre-pipeline    (STYL-04)
+  pipeline_complete = false
+
+Else:
+  Abort: "No .design/ artifacts found. Run /get-design-done scan first to initialize."
+```
+
+The mode controls which files are supplied to the agent in `<required_reading>`.
+
+---
+
+## Component Source Resolution
+
+Search for a source file matching the provided ComponentName (case-insensitive):
+
+1. `src/components/[ComponentName].tsx`
+2. `src/components/[ComponentName].jsx`
+3. `src/components/[ComponentName].vue`
+4. `src/components/[ComponentName].svelte`
+5. `src/**/[ComponentName]/index.tsx`
+6. `src/**/[ComponentName]/index.jsx`
+7. `components/[ComponentName].tsx`
+8. `components/[ComponentName].jsx`
+9. `components/[ComponentName].vue`
+10. `components/[ComponentName].svelte`
+
+**If multiple matches found:** Present the list to the user and prompt them to specify the exact path. Do not proceed until a single file is selected.
+
+**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.
+
+---
+
+## Agent Spawn Payload
+
+Once mode and source path are resolved, spawn the `design-doc-writer` agent:
+
+```
+Task("design-doc-writer", """
+<required_reading>
+[If pipeline_complete=true:]
+@.design/STATE.md
+@.design/DESIGN-SUMMARY.md
+@.design/DESIGN-CONTEXT.md
+@<component_source_path>
+[Else (pipeline_complete=false):]
+@.design/DESIGN.md
+@<component_source_path>
+@reference/anti-patterns.md
+@reference/audit-scoring.md
+</required_reading>
+
+Generate a handoff spec for component <ComponentName>.
+
+Context:
+  component_name: <ComponentName>
+  component_source_path: <resolved absolute path>
+  pipeline_complete: <true|false>
+  output_path: .design/DESIGN-STYLE-<ComponentName>.md
+
+Produce the doc per STYL-05 sections:
+  - Spacing Tokens (used by component)
+  - Color Tokens (used by component)
+  - Typography Scale (used by component)
+  - Component States (default, hover, focus, active, disabled, etc.)
+  - Token Semantic Health Score (raw-hex-ratio formula — see ./shared-preamble.md#token-first-reasoning)
+  - AI-Slop Detection (using ./anti-patterns.md BAN/SLOP patterns)
+  [If pipeline_complete=true:]
+  - Decisions Applied (D-XX from DESIGN-SUMMARY.md that mention this component)
+
+Emit ## DOC COMPLETE when the output file is written.
+""")
+```
+
+After the agent emits `## DOC COMPLETE`, confirm the file exists at `output_path` and report success to the user.
+
+---
+
+## STYL-05 Section Spec
+
+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.
+
+---
+
+## Examples
+
+**Example 1: Named component**
+
+```
+/get-design-done style Button
+```
+
+- Resolves component: `src/components/Button.tsx`
+- Detects mode: DESIGN-SUMMARY.md exists → post-pipeline
+- Spawns `design-doc-writer` with `pipeline_complete: true`
+- Output: `.design/DESIGN-STYLE-Button.md`
+
+**Example 2: No argument (list mode)**
+
+```
+/get-design-done style
+```
+
+- Globs component files from `src/components/`
+- Displays available components and exits without generating any file.
+
+---
+
+*Imported by: `../skills/style/SKILL.md`. Maintained as part of Phase 28.5 (Bucket 2 rework).*

package/skills/synthesize/SKILL.md

@@ -3,6 +3,7 @@ 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."
 tools: Read, Task
 user-invocable: false
+disable-model-invocation: true
 ---
 
 @reference/shared-preamble.md

package/skills/timeline/SKILL.md

@@ -3,6 +3,7 @@ name: gdd-timeline
 description: "Narrative retrospective across cycles: reads EXPERIENCE.md files and git log to produce a timeline view."
 argument-hint: "[<cycle-N> | <from>-<to> | all]"
 tools: Read, Bash, Glob
+disable-model-invocation: true
 ---
 
 @reference/retrieval-contract.md

package/skills/todo/SKILL.md

@@ -3,6 +3,7 @@ name: gdd-todo
 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
 ---
 
 # /gdd:todo

package/skills/turn-closeout/SKILL.md

@@ -9,107 +9,87 @@ tools: Read, Bash
 
 ## Role
 
-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.
+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, so the user sees a closing nudge that matches what Claude Code users see via the Stop hook. 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 the current working directory.
+- **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.
-- **Latency budget**: ≤10ms typical (matches D-10). Read **only** STATE.md and the tail of events.jsonl; never load the full event stream.
-- **Idempotence**: if the most recent event line is already a `turn_end` for the current `(stage, task_progress)` tuple, skip the append but still print the nudge.
-- **Non-blocking**: any I/O failure → silent return. This skill must never gate the user.
+- **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.
 
 ## Algorithm
 
-Execute these steps **in order** and stop at the first early-return.
+Execute in order; stop at the first early-return.
 
-### Step 1 — Try to read STATE.md
+### Step 1 — Read STATE.md
 
-Read `.design/STATE.md`. If the file is missing or unreadable: **return silently** (no print, no append). Mirrors the JS hook's "missing STATE.md" branch.
+Read `.design/STATE.md`. Missing or unreadable → **return silently** (no print, no append).
 
-### Step 2 — Parse the `<position>` block
+### Step 2 — Parse `<position>` block
 
-Lightweight-parse only the `<position>…</position>` block (the rest of STATE.md is irrelevant here). Extract `stage`, `status`, `task_progress`. A regex pass (`/<position>([\s\S]*?)<\/position>/` then per-line `key: value`) is sufficient — do **not** invoke the full STATE parser (cost overhead).
+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**. The pipeline is either initialized, completed, or 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
 
-Read **only the last 8 KiB** of `.design/telemetry/events.jsonl` (a single event line is ≪64 KiB). Treat all of these as "stale by definition":
-- The file is missing.
-- The file is empty.
-- The last line fails to parse as JSON.
-- The last line's `timestamp` is missing or unparseable.
+Read **only the last 8 KiB** of `.design/telemetry/events.jsonl`. Treat as "stale by definition":
 
-Otherwise compute `now - last_event.timestamp`. If the gap is **<60 seconds**, the user is actively mid-turn — **return silently** (the next real event will close the gap naturally).
+- File missing.
+- File empty.
+- Last line fails JSON parse.
+- Last line's `timestamp` is missing or unparseable.
 
-A reasonable Bash one-liner for the tail when running this skill in a runtime that lacks a Read-tail primitive: `tail -n 1 .design/telemetry/events.jsonl 2>/dev/null`.
+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
 
-If the last event is already shaped `{type: "turn_end", stage: <same>, payload: {task_progress: <same>}}` for the **exact** `(stage, task_progress)` tuple from Step 2: **skip the append** but proceed to Step 5.
+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.
 
-Otherwise append a single JSONL line to `.design/telemetry/events.jsonl`:
+Otherwise append one JSONL line to `.design/telemetry/events.jsonl`:
 
 ```json
 {"type":"turn_end","timestamp":"<ISO 8601 now>","sessionId":"<session-id-or-'turn-closeout'>","stage":"<stage>","payload":{"task_progress":"<N/M>"},"_meta":{"source":"gdd-turn-closeout-skill"}}
 ```
 
-Create `.design/telemetry/` if missing. The append must be a single `appendFile`-equivalent call (the writer assumes append-atomicity per Plan 20-06).
+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
 
 Match `task_progress` against `^(\d+)/(\d+)$`:
 
-- **Numerator equals denominator and denominator > 0** (e.g. `5/5`, stage-complete):
+- **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`.
 
-  > 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`
-
-Print exactly one of these two lines. No additional commentary, no explanations of what the skill did — the nudge is the user-facing surface.
+One line exactly. No commentary — the nudge is the user-facing surface.
 
 ## Failure Modes
 
-Every step above has an explicit silent-return on failure. The skill must remain non-blocking under all conditions:
-
 | Condition | Behavior |
 |-----------|----------|
-| `.design/STATE.md` missing or unreadable | Silent return |
-| `<position>` block absent or malformed | Silent return |
+| STATE.md missing/unreadable | Silent return |
+| `<position>` absent or malformed | Silent return |
 | `status != "in_progress"` | Silent return |
-| `.design/telemetry/events.jsonl` missing | Treat as stale → fall through to append + nudge |
-| Last event line unparseable | Treat as stale → fall through |
-| Last event timestamp <60s old | Silent return |
-| Append fails (permission, disk full) | Print the nudge anyway; do not surface the I/O error |
-| Any uncaught throw at any step | Silent return |
+| `events.jsonl` missing | Treat as stale → fall through to append + nudge |
+| Last event unparseable | Treat as stale → fall through |
+| Last event < 60s old | Silent return |
+| Append fails (permission, disk full) | Print nudge anyway; do not surface I/O error |
+| Any uncaught throw | Silent return |
 
 ## Equivalence with the JS hook
 
-This skill and `hooks/gdd-turn-closeout.js` MUST stay code-level equivalent. Specifically:
-
-- Same four early-return branches (no STATE / not in_progress / fresh event / no-op).
-- Same staleness threshold: **60 seconds**.
-- Same idempotence guard: `(type=turn_end, stage, payload.task_progress)` triple.
-- Same emitted event shape (only `_meta.source` differs: `gdd-turn-closeout` vs `gdd-turn-closeout-skill`, so reflector telemetry can distinguish hook-driven vs skill-driven turn-ends).
-- Same nudge wording for both `N/N` and mid-task cases.
-
-If you change one, change the other in the same plan. Plan 25-09's `tests/turn-closeout-hook.test.cjs` covers the JS hook; the parallel coverage for this skill rides on Plan 25-09's Phase 25 baseline.
+This skill and `hooks/gdd-turn-closeout.js` MUST stay code-level equivalent: same four early-return branches, same 60-second staleness threshold, same idempotence guard (`type=turn_end, stage, payload.task_progress`), same event shape (only `_meta.source` differs: `gdd-turn-closeout` vs `gdd-turn-closeout-skill` so reflector telemetry can distinguish hook-driven vs skill-driven). Same nudge wording for both N/N and mid-task cases. Change one → change the other in the same plan. Plan 25-09's `tests/turn-closeout-hook.test.cjs` covers the JS hook.
 
 ## Non-Goals
 
-- **Not a state writer.** This skill never edits STATE.md. The events.jsonl append is the only side effect.
-- **Not a stage transition.** A `turn_end` event is a within-stage observation, not a state-machine move; downstream tools that gate on stage transitions ignore it.
-- **Not a Stop-event harness.** Cross-runtime Stop-event support at the harness level is explicit out-of-scope for Phase 25 (see CONTEXT.md OOS section).
+- **Not a state writer.** Never edits STATE.md. The events.jsonl append is the only side effect.
+- **Not a stage transition.** `turn_end` is within-stage, not a state-machine move; downstream tools ignore it for transition gating.
+- **Not a Stop-event harness.** Cross-runtime Stop-event support at the harness level is out-of-scope for Phase 25 (CONTEXT.md OOS).
 
 ## Integration Point
 
-The canonical tail-call sites (per D-11) are `/gdd:next`, `/gdd:design`, `/gdd:verify`. Each orchestrator's final step, immediately before returning to the user, should be:
-
-> Invoke skill `gdd-turn-closeout`.
-
-Tail-call wiring is intentionally not part of v1.25 (Plan 25-04 ships only the callable surface). Each orchestrator can adopt the wiring independently in a follow-up.
+Canonical tail-call sites per D-11: `/gdd:next`, `/gdd:design`, `/gdd:verify`. Each orchestrator's final step before returning to the user invokes `gdd-turn-closeout`. Tail-call wiring intentionally not part of v1.25 (Plan 25-04 ships only the callable surface).

package/skills/undo/SKILL.md

@@ -3,6 +3,7 @@ name: gdd-undo
 description: "Safe design change revert. Uses git log to find design commits, checks dependencies, reverts safely."
 argument-hint: "[<commit SHA>]"
 tools: Read, Write, Bash, AskUserQuestion
+disable-model-invocation: true
 ---
 
 # /gdd:undo

package/skills/update/SKILL.md

@@ -3,6 +3,7 @@ name: gdd-update
 description: "Update get-design-done to the latest release. Preserves .design/config.json and ./.claude/skills/."
 argument-hint: "[--dry-run] [--version <tag>]"
 tools: Read, Write, Bash
+disable-model-invocation: true
 ---
 
 # gdd-update