@hegemonart/get-design-done 1.0.7

package/skills/style/SKILL.md

@@ -0,0 +1,193 @@
+---
+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."
+argument-hint: "[ComponentName]"
+user-invocable: true
+---
+
+# get-design-done: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.
+
+Output artifact naming: `.design/DESIGN-STYLE-[ComponentName].md` — Title-cased component name, one file per invocation.
+
+---
+
+## Scope
+
+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 does not modify any pipeline artifact.
+- It does not invoke the pipeline router.
+- 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.
+
+---
+
+## 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.
+
+The `.design/` directory is gitignored (developer tooling only — not shipped with the plugin).
+
+---
+
+## Constraints
+
+This command MUST NOT:
+
+- 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
+
+---
+
+## 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 list to user:
+  ```
+  Available components:
+    Button
+    CardHeader
+    Input
+    Modal
+    Toast
+  Specify: /get-design-done style [ComponentName]
+  ```
+- Exits without generating any file.

package/skills/synthesize/SKILL.md

@@ -0,0 +1,93 @@
+---
+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
+---
+
+@reference/shared-preamble.md
+
+# synthesize
+
+## 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.
+
+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.
+
+## When to use
+
+**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.
+
+**Do NOT use synthesize when:**
+- A single-agent flow produced the output (nothing to merge).
+- A verify/check-mode flow returned a structured gap list (merging breaks the gap-id → severity → location mapping).
+- A downstream consumer needs every byte verbatim for grep (e.g., decision-wiring checker that matches exact D-XX anchors).
+
+## Input Contract
+
+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"`.
+
+## Implementation
+
+Single Haiku 4.5 call with this exact merge-prompt template:
+
+```
+You have received {N} outputs from parallel agents. Each output is labeled with its source.
+
+Directive: {directive}
+
+Outputs:
+{each labeled with === from <agent-name> === and its full content}
+
+Produce the merged result in the format specified by the directive.
+Preserve every distinct signal — do NOT drop content. Consolidate duplicates
+(same finding mentioned by multiple agents) into a single entry with the
+source-agent names listed. Keep section headers intact when the directive
+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.
+
+## Output Contract
+
+- **Markdown shape (`output_shape: "markdown"`)** → emit the merged markdown inline, then `## SYNTHESIS COMPLETE` on its own final line. No code fence wrapping the merged output.
+- **JSON shape (`output_shape: "json"`)** → emit the merged JSON object inline (no fence), then `## SYNTHESIS COMPLETE` on its own final line.
+
+The orchestrator is responsible for:
+- Stripping the `## SYNTHESIS COMPLETE` marker before writing to the target file.
+- Persisting the merged artifact to disk (e.g., `.design/DESIGN-PATTERNS.md`).
+- Keeping per-agent files on disk as drill-down evidence.
+
+## 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).
+
+## 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 `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.
+
+## Non-Goals
+
+- 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** re-rank or re-score the inputs. Preservation is the contract.
+
+## Completion Marker
+
+```
+## SYNTHESIS COMPLETE
+```

package/skills/todo/SKILL.md

@@ -0,0 +1,54 @@
+---
+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
+---
+
+# /gdd:todo
+
+**Role:** Design todo list. Three subcommands: `add`, `list`, `pick`. Backing store: `.design/TODO.md`.
+
+## File format
+
+```markdown
+# Design Todos
+
+## P0 — Blocking
+- [ ] [2026-04-18] Fix contrast ratio on card headers
+
+## P1 — High
+- [ ] [2026-04-18] Align Button focus ring with tokens
+
+## P2 — Normal
+
+## P3 — Nice to have
+```
+
+Priority is encoded by section, not inline. Status markers: `[ ]` unchecked, `[x]` done, `[-]` `[in-progress]`, `[p]` `[promoted]`.
+
+## Subcommands
+
+### add [text]
+If text omitted, use `AskUserQuestion`: "What todo item? (include priority P0-P3 if known)". Parse leading `P[0-3]` token from text; default P2. Append under the right section as:
+```
+- [ ] [YYYY-MM-DD] <text without priority token>
+```
+Create TODO.md from the template above if missing.
+
+### list
+Read `.design/TODO.md`. Print all `- [ ]` and `- [-]` items grouped by priority section, with index numbers.
+
+### pick
+Read `.design/TODO.md`. Collect unchecked items. Use `AskUserQuestion` to let the user pick one. Rewrite the chosen line as:
+```
+- [-] [YYYY-MM-DD] [in-progress] <original text>
+```
+Print "Picked: <item>".
+
+## Constraints
+
+- Do not modify files outside `.design/`.
+- Preserve existing sections and ordering on write.
+
+## TODO COMPLETE

package/skills/undo/SKILL.md

@@ -0,0 +1,30 @@
+---
+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
+---
+
+# /gdd:undo
+
+Safe rollback for design-related commits. Uses git history plus file-overlap dependency checks before reverting.
+
+## Steps
+
+1. **List candidates**: Run `git log --oneline -n 20 --grep="design\|feat\|fix"` via Bash. Filter for commits whose scope matches phase prefixes (`design(`, `feat(07`, etc.) or touch files under `src/` related to design changes.
+2. **Present choice**: If no SHA was passed as argument, print the last 10 design-related commits and ask (AskUserQuestion): "Which commit to undo? (or enter commit SHA)"
+3. **Dependency scan**: For the chosen SHA, run `git show --name-only <sha>` to get touched files. Then run `git log <sha>..HEAD --name-only` to find later commits that modified any of those same files. These are potential dependencies.
+4. **Dependency decision**:
+   - If none found: proceed to step 5.
+   - If found: print "Reverting this commit may break: <later commits>. Proceed anyway? (yes/no)" and abort on "no".
+5. **Stage the revert**: Run `git revert <sha> --no-commit`. Show the resulting diff via `git diff --cached`.
+6. **Confirm**: Ask (AskUserQuestion): "Apply this revert? (yes/no)"
+7. **Commit or abort**: On yes, `git commit -m "revert: <original subject>"`. On no, `git reset` to unstage.
+
+## Do Not
+
+- Do not force-push.
+- Do not revert commits on `main` without the user confirming branch context.
+- Do not silently skip dependency warnings.
+
+## UNDO COMPLETE

package/skills/update/SKILL.md

@@ -0,0 +1,36 @@
+---
+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
+---
+
+# gdd-update
+
+Updates the `get-design-done` plugin to the latest release (or a specific tag), preserving user-local state.
+
+## 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.
+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.
+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.
+
+8. Print the new version and the changelog URL (`https://github.com/hegemonart/get-design-done/releases`).
+
+## Output
+
+End every invocation with:
+
+```
+## UPDATE COMPLETE
+```
+
+## Implementation note
+
+The actual update mechanism is the standard `claude plugin install` re-install path. This skill only orchestrates the pre-/post-preservation steps around it.