npm - @hegemonart/get-design-done - Versions diffs - 1.0.7 - Mend

@hegemonart/get-design-done 1.0.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (144) hide show

package/.claude-plugin/marketplace.json +63 -0
package/.claude-plugin/plugin.json +54 -0
package/CHANGELOG.md +221 -0
package/LICENSE +21 -0
package/README.md +724 -0
package/SKILL.md +232 -0
package/agents/README.md +226 -0
package/agents/a11y-mapper.md +118 -0
package/agents/component-taxonomy-mapper.md +88 -0
package/agents/design-advisor.md +139 -0
package/agents/design-assumptions-analyzer.md +171 -0
package/agents/design-auditor.md +383 -0
package/agents/design-context-builder.md +544 -0
package/agents/design-context-checker-gate.md +90 -0
package/agents/design-context-checker.md +260 -0
package/agents/design-discussant.md +98 -0
package/agents/design-doc-writer.md +229 -0
package/agents/design-executor.md +452 -0
package/agents/design-figma-writer.md +302 -0
package/agents/design-fixer.md +180 -0
package/agents/design-integration-checker-gate.md +93 -0
package/agents/design-integration-checker.md +326 -0
package/agents/design-pattern-mapper.md +206 -0
package/agents/design-phase-researcher.md +229 -0
package/agents/design-plan-checker.md +164 -0
package/agents/design-planner.md +352 -0
package/agents/design-reflector.md +175 -0
package/agents/design-research-synthesizer.md +127 -0
package/agents/design-verifier-gate.md +97 -0
package/agents/design-verifier.md +605 -0
package/agents/gdd-graphify-sync.md +100 -0
package/agents/gdd-intel-updater.md +88 -0
package/agents/gdd-learnings-extractor.md +85 -0
package/agents/motion-mapper.md +103 -0
package/agents/token-mapper.md +103 -0
package/agents/visual-hierarchy-mapper.md +95 -0
package/connections/chromatic.md +247 -0
package/connections/claude-design.md +190 -0
package/connections/connections.md +218 -0
package/connections/figma-writer.md +139 -0
package/connections/figma.md +146 -0
package/connections/graphify.md +197 -0
package/connections/pinterest.md +153 -0
package/connections/preview.md +173 -0
package/connections/refero.md +189 -0
package/connections/storybook.md +280 -0
package/hooks/budget-enforcer.js +318 -0
package/hooks/context-exhaustion.js +127 -0
package/hooks/gdd-read-injection-scanner.js +44 -0
package/hooks/hooks.json +44 -0
package/package.json +60 -0
package/reference/BRANCH-PROTECTION.md +65 -0
package/reference/DEPRECATIONS.md +41 -0
package/reference/STATE-TEMPLATE.md +200 -0
package/reference/accessibility.md +190 -0
package/reference/anti-patterns.md +336 -0
package/reference/audit-scoring.md +205 -0
package/reference/checklists.md +137 -0
package/reference/config-schema.md +319 -0
package/reference/debugger-philosophy.md +32 -0
package/reference/heuristics.md +201 -0
package/reference/intel-schema.md +266 -0
package/reference/model-prices.md +37 -0
package/reference/model-tiers.md +118 -0
package/reference/motion.md +285 -0
package/reference/parallelism-rules.md +108 -0
package/reference/priority-matrix.md +31 -0
package/reference/project-skills-guide.md +42 -0
package/reference/review-format.md +107 -0
package/reference/schemas/config.schema.json +41 -0
package/reference/schemas/hooks.schema.json +55 -0
package/reference/schemas/intel.schema.json +191 -0
package/reference/schemas/marketplace.schema.json +72 -0
package/reference/schemas/plugin.schema.json +59 -0
package/reference/shared-preamble.md +82 -0
package/reference/typography.md +229 -0
package/scripts/aggregate-agent-metrics.js +144 -0
package/scripts/apply-branch-protection.sh +75 -0
package/scripts/bootstrap-manifest.txt +3 -0
package/scripts/bootstrap.sh +80 -0
package/scripts/build-intel.cjs +458 -0
package/scripts/detect-stale-refs.cjs +101 -0
package/scripts/extract-changelog-section.cjs +57 -0
package/scripts/release-smoke-test.cjs +169 -0
package/scripts/rollback-release.sh +42 -0
package/scripts/run-injection-scanner-ci.cjs +92 -0
package/scripts/validate-frontmatter.cjs +68 -0
package/scripts/validate-schemas.cjs +225 -0
package/scripts/verify-version-sync.cjs +30 -0
package/skills/add-backlog/SKILL.md +47 -0
package/skills/analyze-dependencies/SKILL.md +184 -0
package/skills/apply-reflections/SKILL.md +112 -0
package/skills/audit/SKILL.md +54 -0
package/skills/brief/SKILL.md +75 -0
package/skills/cache-manager/SKILL.md +120 -0
package/skills/compare/SKILL.md +322 -0
package/skills/complete-cycle/SKILL.md +33 -0
package/skills/darkmode/SKILL.md +331 -0
package/skills/debug/SKILL.md +38 -0
package/skills/design/SKILL.md +281 -0
package/skills/discover/SKILL.md +172 -0
package/skills/discuss/SKILL.md +67 -0
package/skills/do/SKILL.md +45 -0
package/skills/explore/SKILL.md +109 -0
package/skills/extract-learnings/SKILL.md +98 -0
package/skills/fast/SKILL.md +44 -0
package/skills/figma-write/SKILL.md +40 -0
package/skills/graphify/SKILL.md +48 -0
package/skills/health/SKILL.md +48 -0
package/skills/help/SKILL.md +76 -0
package/skills/list-assumptions/SKILL.md +60 -0
package/skills/map/SKILL.md +112 -0
package/skills/new-cycle/SKILL.md +35 -0
package/skills/new-project/SKILL.md +53 -0
package/skills/next/SKILL.md +42 -0
package/skills/note/SKILL.md +47 -0
package/skills/optimize/SKILL.md +120 -0
package/skills/pause/SKILL.md +41 -0
package/skills/plan/SKILL.md +251 -0
package/skills/plant-seed/SKILL.md +47 -0
package/skills/pr-branch/SKILL.md +31 -0
package/skills/progress/SKILL.md +60 -0
package/skills/quick/SKILL.md +43 -0
package/skills/reapply-patches/SKILL.md +31 -0
package/skills/reflect/SKILL.md +73 -0
package/skills/resume/SKILL.md +37 -0
package/skills/review-backlog/SKILL.md +45 -0
package/skills/router/SKILL.md +67 -0
package/skills/scan/SKILL.md +721 -0
package/skills/settings/SKILL.md +78 -0
package/skills/ship/SKILL.md +31 -0
package/skills/sketch/SKILL.md +78 -0
package/skills/sketch-wrap-up/SKILL.md +88 -0
package/skills/skill-manifest/SKILL.md +79 -0
package/skills/spike/SKILL.md +67 -0
package/skills/spike-wrap-up/SKILL.md +81 -0
package/skills/stats/SKILL.md +50 -0
package/skills/style/SKILL.md +193 -0
package/skills/synthesize/SKILL.md +93 -0
package/skills/todo/SKILL.md +54 -0
package/skills/undo/SKILL.md +30 -0
package/skills/update/SKILL.md +36 -0
package/skills/verify/SKILL.md +452 -0
package/skills/warm-cache/SKILL.md +113 -0

package/skills/settings/SKILL.md ADDED Viewed

@@ -0,0 +1,78 @@
+---
+name: gdd-settings
+description: "Manage .design/config.json settings. Subcommands: profile, parallelism, cleanup, show."
+argument-hint: "<profile <name>|parallelism <key> <value>|cleanup|show>"
+tools: Read, Write, AskUserQuestion, Bash
+---
+# gdd-settings
+Manages `.design/config.json` — the per-project config for model profile and parallelism. See `reference/config-schema.md` for the full schema.
+## Subcommands
+### `show`
+Print the current `.design/config.json` contents, nicely formatted. If the file is missing, print the defaults with a note that no config exists yet.
+### `profile <name>`
+Set `model_profile` to one of `quality`, `balanced`, `budget`. Validate the value; reject anything else with the list of allowed values. Read current config, merge the change, write back. Confirm with the new value.
+### `parallelism <key> <value>`
+Set one field under `parallelism`. Supported keys and value types:
+| Key | Type |
+|---|---|
+| `enabled` | bool (`true`/`false`) |
+| `max_parallel_agents` | int |
+| `min_tasks_to_parallelize` | int |
+| `min_estimated_savings_seconds` | int |
+| `require_disjoint_touches` | bool |
+| `worktree_isolation` | bool |
+Validate type; reject otherwise. Read current config, merge, write back. Confirm.
+### `cleanup`
+Use `AskUserQuestion` to pick one or more cleanup actions, then confirm each before executing:
+1. Delete `.design/*.md` artifacts (excludes `config.json`, `STATE.md`, `backlog/`).
+2. Reset `.design/STATE.md` to the template at `reference/STATE-TEMPLATE.md`.
+3. Clear `.design/backlog/` directory contents.
+## Config Read/Write Pattern
+Always:
+1. Read current `.design/config.json` (use defaults below if missing).
+2. Merge the single field being changed — never overwrite unrelated fields.
+3. Write back as pretty JSON (2-space indent, trailing newline).
+## Default Config
+If `.design/config.json` does not exist, create it with:
+```json
+{
+  "model_profile": "balanced",
+  "parallelism": {
+    "enabled": true,
+    "max_parallel_agents": 5,
+    "min_tasks_to_parallelize": 2,
+    "min_estimated_savings_seconds": 30,
+    "require_disjoint_touches": true,
+    "worktree_isolation": false,
+    "per_stage_override": {}
+  }
+}
+```
+## Output
+End every invocation with:
+```
+## SETTINGS COMPLETE
+```

package/skills/ship/SKILL.md ADDED Viewed

@@ -0,0 +1,31 @@
+---
+name: gdd-ship
+description: "Post-verify PR flow — creates a clean PR branch, invokes code review check, and prepares the PR for merge."
+argument-hint: "[--title <PR title>] [--draft]"
+tools: Read, Write, Bash, AskUserQuestion, Task
+---
+# /gdd:ship
+Closes the verify → merge gap: runs `/gdd:pr-branch` for a clean branch, assembles a PR body from design artifacts, and creates the PR via `gh`.
+## Steps
+1. **Pre-flight verify check**: Check that `.design/DESIGN-VERIFICATION.md` exists and shows a pass. If missing or failing, ask: "Verify has not completed / failed. Ship anyway? (yes/no)"
+2. **Clean branch**: Invoke `/gdd:pr-branch` to produce a branch with only `src/` commits (no `.design/` or `.planning/` noise). Use the resulting branch for the PR.
+3. **PR title**: Use `--title` argument if given, otherwise ask (AskUserQuestion): "PR title?"
+4. **PR body**: Auto-generate from:
+   - Goals section of `.design/DESIGN-PLAN.md`
+   - Summary of `.design/DESIGN-VERIFICATION.md` (per-task pass/fail)
+   - Top-line audit score from `.design/DESIGN-AUDIT.md` if present
+   Format as Markdown with `## Goals`, `## Verification`, `## Audit` sections.
+5. **Create PR**: Run `gh pr create --title "<title>" --body "<body>" [--draft]` via Bash. If `gh` is not installed, print the full body and instruct the user to create the PR manually.
+6. **Print PR URL** on success.
+## Do Not
+- Do not push to `main`/`master` directly.
+- Do not include `.design/` or `.planning/` files in the PR branch — that is `/gdd:pr-branch`'s job.
+- Do not skip the verify pre-flight silently — always surface a failure and ask.
+## SHIP COMPLETE

package/skills/sketch/SKILL.md ADDED Viewed

@@ -0,0 +1,78 @@
+---
+name: gdd-sketch
+description: "Multi-variant HTML design exploration. Creates .design/sketches/<slug>/ with N standalone variants. Browser-openable directly — no build step."
+argument-hint: "[topic] [--variants N] [--quick]"
+tools: Read, Write, AskUserQuestion, Bash
+---
+# Get Design Done — Sketch
+**Role:** Multi-variant HTML exploration. Answers "what could this look like?" by generating N standalone HTML variants from a topic prompt. Variants are browser-openable directly — no build step — and can be screenshot by Phase 8 Preview/Playwright tooling later.
+Unlike `/gdd:spike` (which tests feasibility), `/gdd:sketch` explores visual/directional variants.
+## Flag parsing
+Parse `$ARGUMENTS`:
+- `[topic]` → kebab-case slug (e.g., "hero-redesign")
+- `--variants N` → number of variants (default: 3)
+- `--quick` → skip intake, use DESIGN-CONTEXT.md tokens + sensible defaults
+## Step 1 — Intake (unless `--quick`)
+AskUserQuestion, one at a time:
+1. "What are you sketching? (component, layout, page)"
+2. "What directions should the variants explore? (minimal/maximal, dense/spacious, flat/layered, playful/restrained, etc.)"
+3. "Which design tokens apply? (pick from DESIGN-CONTEXT.md, or use defaults)"
+If `--quick`: derive directions from topic + pull tokens from `.design/DESIGN-CONTEXT.md` if present, else defaults.
+## Step 2 — Create sketch directory
+- Derive `<slug>` from the topic (kebab-case).
+- `mkdir -p .design/sketches/<slug>/` via Bash.
+## Step 3 — Write INTAKE.md
+Write `.design/sketches/<slug>/INTAKE.md` with:
+- Topic
+- Directions (one bullet per variant)
+- Token references (link to DESIGN-CONTEXT.md or inline list)
+- Timestamp
+## Step 4 — Generate N standalone HTML variants
+For each of N variants (default 3), write `variant-<n>.html` as a **complete standalone HTML file**:
+- `<!DOCTYPE html>` + `<html>` + `<head>` + `<body>`
+- `<style>` block inline with CSS custom properties for tokens (`--color-*`, `--space-*`, `--font-*`)
+- Semantic HTML5 (`<header>`, `<main>`, `<nav>`, `<section>`, etc.)
+- No imports, no bundler, no JS framework — opens in a browser directly via `file://`
+- Each variant explores a different direction from intake
+## Step 5 — Write README.md
+Write `.design/sketches/<slug>/README.md` with:
+- Topic + one-line summary
+- List of variants: `variant-1.html` — direction label — one-line description
+- How to view: "Open each `variant-*.html` in a browser."
+- Next step: "Run `/gdd:sketch-wrap-up <slug>` when ready to pick a winner."
+## After writing
+```
+━━━ Sketches created ━━━
+Slug: <slug>
+Directory: .design/sketches/<slug>/
+Variants: N standalone HTML files
+Open variant-*.html in a browser.
+Next: /gdd:sketch-wrap-up <slug>
+━━━━━━━━━━━━━━━━━━━━━━━━
+```
+## Do Not
+- Do not write to `src/` — sketches live in `.design/sketches/` only.
+- Do not use build-step syntax (JSX, TS, imports). Standalone HTML only.
+- Do not overwrite an existing sketch slug without asking.
+## SKETCH COMPLETE

package/skills/sketch-wrap-up/SKILL.md ADDED Viewed

@@ -0,0 +1,88 @@
+---
+name: gdd-sketch-wrap-up
+description: "Walk through sketches, pick winner + rationale, group by design area, write project skills to ./.claude/skills/design-<area>-conventions.md."
+argument-hint: "[slug]"
+tools: Read, Write, Glob, AskUserQuestion
+---
+# Get Design Done — Sketch Wrap-Up
+**Role:** Close an open sketch — elicit the winner + rationale from the user, group the decision by design area, and codify it as a project-local skill at `./.claude/skills/design-<area>-conventions.md` so future gdd sessions auto-load the decision.
+## Step 1 — Find sketches
+- Glob `.design/sketches/*/`.
+- If `[slug]` provided → use it directly.
+- If multiple pending (no `WINNER.md`) → AskUserQuestion: "Which sketch are you wrapping up?"
+- If none → print: "No open sketches. Run `/gdd:sketch` first." and exit.
+## Step 2 — Walk variants
+Read the sketch's `README.md`. For each `variant-N.html`:
+- Show the variant's one-line description from README.
+- AskUserQuestion: "Is variant-N a keeper, maybe, or rejected?"
+## Step 3 — Elicit winner rationale
+AskUserQuestion:
+1. "Which variant is the winner?"
+2. "What makes variant-N the winning direction? (grounds the decision for future sessions)"
+3. "Any token implications? (e.g., spacing scale clamp, color adjustment, font-weight shift)"
+## Step 4 — Group by design area
+AskUserQuestion: "Which design area does this winner inform?"
+Options: typography / color / layout / motion / component / interaction
+## Step 5 — Write project skill
+Append to `./.claude/skills/design-<area>-conventions.md` (create if missing):
+```markdown
+# Design <Area> Conventions (Project-Local)
+Auto-loaded in gdd sessions. Captures decisions codified from `/gdd:sketch-wrap-up`.
+## Decision from sketch: <slug> (YYYY-MM-DD)
+**Winner**: variant-N (<direction label>)
+**Rationale**: <user rationale>
+**Token implications**: <implications, or "none">
+```
+## Step 6 — Write WINNER.md
+Write `.design/sketches/<slug>/WINNER.md`:
+```markdown
+# Winner: variant-N
+**Slug**: <slug>
+**Area**: <area>
+**Rationale**: <user rationale>
+**Captured**: YYYY-MM-DD
+**Project skill written to**: ./.claude/skills/design-<area>-conventions.md
+```
+## Step 7 — Update sketches SUMMARY.md
+Append entry to `.design/sketches/SUMMARY.md` (create if missing):
+```markdown
+- <slug> (YYYY-MM-DD) — winner: variant-N — area: <area> — <one-line rationale>
+```
+## After writing
+```
+━━━ Sketch wrapped ━━━
+Slug: <slug>
+Winner: variant-N
+Area: <area>
+Project skill: ./.claude/skills/design-<area>-conventions.md
+━━━━━━━━━━━━━━━━━━━━━
+```
+## Do Not
+- Do not modify other sketch variants or rejected directions.
+- Do not write to `src/` — conventions are design-layer only.
+## SKETCH-WRAP-UP COMPLETE

package/skills/skill-manifest/SKILL.md ADDED Viewed

@@ -0,0 +1,79 @@
+---
+name: gdd-skill-manifest
+description: "Lists all registered GDD skills and agents, with descriptions, from the intel store. Falls back to directory scan if intel store not present."
+tools: Bash, Read, Glob
+---
+# /gdd:skill-manifest
+**Role:** Print a manifest of all registered skills (commands) and agents available in this plugin installation.
+## Pre-flight check
+```bash
+ls .design/intel/exports.json 2>/dev/null && echo "ready" || echo "missing"
+```
+## Mode 1 — Intel store available
+Read `.design/intel/exports.json`. Group entries by `kind` (skill vs agent). Print:
+```
+━━━ Skill Manifest ━━━
+Generated from intel store: .design/intel/exports.json
+SKILLS (Commands)
+─────────────────
+/gdd:scan               gdd-scan
+/gdd:discover           gdd-discover
+/gdd:plan               gdd-plan
+/gdd:design             gdd-design
+/gdd:verify             gdd-verify
+/gdd:style              gdd-style
+/gdd:darkmode           gdd-darkmode
+/gdd:compare            gdd-compare
+... (all skills)
+AGENTS
+──────
+design-advisor          Design advisor agent
+design-auditor          Design auditor agent
+design-context-builder  Builds DESIGN-CONTEXT.md from codebase scan
+... (all agents)
+Total: <N> skills, <M> agents
+━━━━━━━━━━━━━━━━━━━━━
+```
+To get the description for each skill/agent: read `exports.json` entry and look up the matching file in `files.json`, then read its frontmatter `description` field from `exports.json` (if stored) or from the file directly.
+## Mode 2 — Intel store missing (fallback)
+If `.design/intel/exports.json` is not present, fall back to directory scan:
+```bash
+ls skills/
+ls agents/*.md
+```
+Print a simplified manifest without descriptions:
+```
+━━━ Skill Manifest (no intel store — run build-intel.cjs for descriptions) ━━━
+SKILLS: scan, discover, plan, design, verify, style, darkmode, compare, ...
+AGENTS: design-advisor.md, design-auditor.md, ...
+━━━━━━━━━━━━━━━━━━━━━
+```
+## Filter mode
+`/gdd:skill-manifest agents` — show agents only
+`/gdd:skill-manifest skills` — show skills only
+`/gdd:skill-manifest <keyword>` — filter by keyword in name or description
+## Required reading (conditional)
+@.design/intel/exports.json (if present)
+## SKILL-MANIFEST COMPLETE

package/skills/spike/SKILL.md ADDED Viewed

@@ -0,0 +1,67 @@
+---
+name: gdd-spike
+description: "Timeboxed feasibility experiment. Answers 'can this work?' questions. Creates .design/spikes/<slug>/ with hypothesis, timebox, scratch code, findings."
+argument-hint: "[hypothesis] [--timebox <minutes>]"
+tools: Read, Write, Bash, AskUserQuestion
+---
+# Get Design Done — Spike
+**Role:** Timeboxed feasibility experiment. Answers "can this work?" — e.g., "can we use view transitions for this flow?", "does this animation perform on mobile?". Unlike `/gdd:sketch` (visual variants), `/gdd:spike` tests a hypothesis.
+## Flag parsing
+Parse `$ARGUMENTS`:
+- `[hypothesis]` → summary phrase, derives the slug
+- `--timebox <minutes>` → default 60
+## Step 1 — Intake
+AskUserQuestion:
+1. "What's the hypothesis? (e.g., 'view transitions can replace our current route animations')"
+2. "What's the timebox? (default 60 minutes)"
+3. "What would prove it works? (success criteria)"
+4. "What would prove it doesn't? (failure criteria)"
+## Step 2 — Create spike directory
+- Derive `<slug>` from the hypothesis (kebab-case, short).
+- `mkdir -p .design/spikes/<slug>/scratch/` via Bash.
+## Step 3 — Write HYPOTHESIS.md
+Write `.design/spikes/<slug>/HYPOTHESIS.md`:
+```markdown
+# Spike: <slug>
+**Hypothesis**: <statement>
+**Timebox**: <N> minutes
+**Started**: YYYY-MM-DD HH:MM
+## Success criteria
+- <criterion>
+## Failure criteria
+- <criterion>
+## Scratch area
+Experimental code in `./scratch/` — not committed to src/.
+```
+## Step 4 — Announce
+```
+━━━ Spike started ━━━
+Slug: <slug>
+Timebox: <N> minutes
+Work in: .design/spikes/<slug>/scratch/
+When done: /gdd:spike-wrap-up <slug>
+━━━━━━━━━━━━━━━━━━━━━
+```
+## Do Not
+- Do not write experimental code to `src/` — use `.design/spikes/<slug>/scratch/`.
+- Do not exceed the timebox without explicit user approval; wrap up and reassess first.
+## SPIKE COMPLETE

package/skills/spike-wrap-up/SKILL.md ADDED Viewed

@@ -0,0 +1,81 @@
+---
+name: gdd-spike-wrap-up
+description: "Close a spike — capture findings, write decision to STATE.md, update SUMMARY.md."
+argument-hint: "[slug]"
+tools: Read, Write, Glob, AskUserQuestion
+---
+# Get Design Done — Spike Wrap-Up
+**Role:** Close an open spike — capture the verdict, write findings, record a D-XX decision in STATE.md so `plan` sees it when creating tasks.
+## Step 1 — Find spike
+- Glob `.design/spikes/*/`.
+- If `[slug]` provided → use it directly.
+- If multiple pending (no `FINDINGS.md`) → AskUserQuestion: "Which spike are you wrapping up?"
+- If none → print: "No open spikes. Run `/gdd:spike` first." and exit.
+## Step 2 — Re-surface hypothesis
+Read `.design/spikes/<slug>/HYPOTHESIS.md`. Show the hypothesis + success/failure criteria to the user.
+## Step 3 — Elicit findings
+AskUserQuestion:
+1. "Did it meet success criteria? (yes / no / partial)"
+2. "What was learned? (1–3 sentences)"
+3. "Recommendation? (adopt / reject / needs more investigation)"
+## Step 4 — Write FINDINGS.md
+Write `.design/spikes/<slug>/FINDINGS.md`:
+```markdown
+# Findings: <slug>
+**Verdict**: yes / no / partial
+**Recommendation**: adopt / reject / needs more investigation
+**Completed**: YYYY-MM-DD HH:MM
+## What was learned
+<1–3 sentences>
+## Next steps
+<1–2 bullets>
+```
+## Step 5 — Record decision in STATE.md
+Append a `D-XX` entry under `<decisions>` in `.design/STATE.md`:
+```
+D-XX: spike/<slug> — <verdict> — <recommendation>
+  Rationale: <one line>
+  Source: .design/spikes/<slug>/FINDINGS.md
+```
+(Increment D-XX from the highest existing number.)
+## Step 6 — Update spikes SUMMARY.md
+Append entry to `.design/spikes/SUMMARY.md` (create if missing):
+```markdown
+- <slug> (YYYY-MM-DD) — verdict: <yes|no|partial> — recommendation: <adopt|reject|more> — D-XX
+```
+## After writing
+```
+━━━ Spike wrapped ━━━
+Slug: <slug>
+Verdict: <verdict>
+Decision recorded: D-XX
+FINDINGS.md written.
+━━━━━━━━━━━━━━━━━━━━
+```
+## Do Not
+- Do not delete the `scratch/` directory — it's a record of what was tried.
+- Do not promote scratch code to `src/` automatically — require a follow-up plan task.
+## SPIKE-WRAP-UP COMPLETE

package/skills/stats/SKILL.md ADDED Viewed

@@ -0,0 +1,50 @@
+---
+name: gdd-stats
+description: "Cycle stats — decisions made, tasks completed, commits, timeline, git metrics."
+tools: Read, Bash
+---
+# /gdd:stats
+**Role:** Print cycle metrics.
+## 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
+Let `<since>` = cycle start date (fallback to STATE.md `started_at`).
+```bash
+git log --oneline --since="<since>" | wc -l          # commits
+git diff --stat HEAD~N HEAD                          # files changed since cycle start
+```
+If git unavailable, print `git: unavailable` and skip git metrics.
+## Step 3 — Count todos
+Read `.design/TODO.md` if present:
+- pending: count `- [ ]`
+- in-progress: count `- [-]`
+- done: count `- [x]`
+- group pending by P0/P1/P2/P3 section
+## Step 4 — Output
+```
+━━━ Cycle stats ━━━
+Cycle: cycle-1   Started: 2026-04-18
+Decisions made: 12 (D-01..D-12)
+Tasks completed: 8 / 10
+Git commits:     23
+Files changed:   47
+Open todos:      3 (P0: 1, P1: 2, P2: 0, P3: 0)
+Agents spawned:  — (no task log)
+━━━━━━━━━━━━━━━━━━
+```
+## STATS COMPLETE