@hegemonart/get-design-done 1.57.2 → 1.57.3

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

@@ -1,222 +0,0 @@
----
-name: discover-procedure
-type: meta-rules
-version: 1.0.0
-phase: 28.5
-tags: [discover, procedure, extracted, pipeline-stage, connection-probe, design-context-builder]
-last_updated: 2026-05-18
----
-
-Source: extracted from `skills/discover/SKILL.md` (Phase 28.5 rework - D-10 extract-then-link).
-The skill's essential workflow stays in `../skills/discover/SKILL.md`; this file holds the
-detail the agent reaches for when executing a specific step (state integration, three
-connection probes, design-context-builder + design-context-checker agent prompts, lazy gate
-prompt, auto-mode CSS detection).
-
-# Discover Procedure
-
-Detailed procedure for the get-design-done `discover` Stage 1.5 orchestrator. Companion to
-`../skills/discover/SKILL.md`. Read this file when executing a specific discover step.
-
----
-
-## State Integration
-
-1. Read `.design/STATE.md`.
-   - If missing: create minimal skeleton from `reference/STATE-TEMPLATE.md` with stage=discover, status=in_progress, task_progress=0/1, and log warning: "STATE.md not found - created fresh. If this is a resumed session, run /get-design-done:scan first."
-   - If present and stage==discover and status==in_progress: RESUME - continue existing interview; do not reset.
-   - Otherwise: normal transition - set frontmatter stage=discover, <position> stage=discover, status=in_progress, task_progress=0/1.
-2. **Probe connection availability** - ToolSearch runs FIRST because MCP tools may be in the deferred tool set. This is the canonical probe pattern (spec lives in `connections/connections.md`; copied inline because SKILL.md has no include mechanism - if the probe pattern changes, update all stages that copied it). See §Connection Probes below.
-3. Update last_checkpoint. Write STATE.md.
-
----
-
-## Connection Probes
-
-### A - Figma probe (variant-agnostic)
-
-```
-A1. ToolSearch({ query: "figma get_metadata use_figma", max_results: 10 })
-A2. Parse tool names matching /^mcp__([^_]*figma[^_]*)__(get_metadata|use_figma)$/i
-    into read-capable and write-capable prefix sets.
-A3. Empty read set -> figma: not_configured (skip all Figma paths)
-    One or more matches -> pick prefix via tiebreaker:
-      (1) both-sets > reads-only,
-      (2) `figma` > others,
-      (3) non-`figma-desktop` > desktop,
-      (4) alphabetical.
-A4. Call {prefix}get_metadata:
-      Success -> figma: available (prefix=mcp__<prefix>__, writes=<true|false>)
-      Error   -> figma: unavailable
-```
-
-### B - Refero probe (ToolSearch presence is sufficient - no tool call needed)
-
-```
-B1. ToolSearch({ query: "refero", max_results: 5 })
-B2. Empty result  -> refero: not_configured
-    Non-empty     -> refero: available
-```
-
-### C - Pinterest probe (ToolSearch-only, same pattern as Refero)
-
-```
-C1. ToolSearch({ query: "mcp-pinterest", max_results: 5 })
-C2. Empty result  -> pinterest: not_configured
-    Non-empty     -> pinterest: available
-```
-
-No live `pinterest_search` call at probe time - ToolSearch presence is sufficient. The synthesizer makes the actual search calls.
-
-### D - Lazyweb probe (ToolSearch-only - free, discover Tier 1 per D-01)
-
-```
-D1. ToolSearch({ query: "lazyweb", max_results: 5 })
-D2. Empty result  -> lazyweb: not_configured
-    Non-empty     -> lazyweb: available
-```
-
-### E - Mobbin probe (ToolSearch-only - paid, discover Tier 2 per D-01)
-
-```
-E1. ToolSearch({ query: "mobbin", max_results: 5 })
-E2. Empty result  -> mobbin: not_configured
-    Non-empty     -> mobbin: available
-```
-
-**Reference-source tier order (cost-aware, D-01):** Lazyweb (free, tried first) → Mobbin / Refero (paid, whichever is bound + subscribed) → Pinterest → awesome-design-md → WebFetch.
-
-After all probes (A, B, C, D, E), update `.design/STATE.md` `<connections>` with the results and continue. Downstream stages (design-context-builder) read `<connections>` from STATE.md rather than re-probing.
-
----
-
-## Auto Mode
-
-Auto Mode CSS detection (when `auto_mode: true` is passed to the builder):
-
-  1. If tailwind.config.{js,cjs,mjs,ts} exists -> Tailwind-only project
-     - Skip CSS file grep
-     - Parse tailwind.config for color palette, spacing scale, font families
-     - Use tailwind.config values as the baseline style signal
-  2. Else -> fall through to existing CSS file grep logic
-
----
-
-## Step 1 - Spawn design-context-builder
-
-```
-Task("design-context-builder", """
-<required_reading>
-@.design/STATE.md
-@reference/audit-scoring.md
-@reference/anti-patterns.md
-</required_reading>
-
-You are the design-context-builder agent. Auto-detect existing design system
-state via grep/glob before asking questions. Interview the user ONLY for areas
-where auto-detect returned no confident answer. Write .design/DESIGN-CONTEXT.md.
-
-Baseline audit directory detection (ordered fallback chain):
-  1. If src/ exists -> use src/
-  2. Elif app/ exists -> use app/ (Next.js App Router)
-  3. Elif pages/ exists -> use pages/ (Next.js Pages Router)
-  4. Elif lib/ exists -> use lib/ (library-only projects)
-  5. Else -> flag "layout unknown", skip baseline, note in DESIGN-CONTEXT.md
-
-Common gray areas to probe during discovery (Area 7):
-  1. font-change risk — switching type families when existing UI has body copy in a specific family. Ask: "Is the current body font intentional or inherited? OK to change?"
-  2. token-layer introduction risk — adding CSS custom properties to a codebase that uses direct values. Ask: "Do you want design tokens (--primary, --surface) or inline values (hex, rgb)?"
-  3. Component rebuild vs restyle — when to keep existing component, when to rebuild from scratch. Ask: "For <component>, restyle in place or rebuild?"
-
-Context:
-  auto_mode: <true|false>
-
-Output file: .design/DESIGN-CONTEXT.md
-Emit `## CONTEXT COMPLETE` when done.
-""")
-```
-
-Wait for `## CONTEXT COMPLETE`. Update STATE.md task_progress = 0.5.
-
----
-
-## Step 1.75 - Lazy gate: should design-context-checker run? (Plan 10.1-04, D-21)
-
-Spawn the cheap Haiku gate before the full context-checker:
-
-    Task("design-context-checker-gate", """
-    <required_reading>
-    @.design/STATE.md
-    </required_reading>
-
-    You are the design-context-checker-gate.
-
-    Context:
-      diff_files: <git diff `--name-only` HEAD~1..HEAD>
-      diff_body: (not needed - single-file heuristic)
-      baseline_sha: <HEAD~1>
-
-    Apply the heuristic (DESIGN-CONTEXT.md in diff_files?). Emit JSON + `## GATE COMPLETE`.
-    """)
-
-Wait for `## GATE COMPLETE`. Parse JSON:
-
-- `spawn: false` -> append `lazy_skipped: true` telemetry row for `design-context-checker`, skip Step 2, set STATE.md `<position>` as if checker passed (rationale: DESIGN-CONTEXT.md didn't change, last validation still holds), emit `design-context-checker skipped — <rationale>`.
-- `spawn: true` -> proceed to Step 2 as currently written.
-
-**Note:** On first-run discover, the builder just wrote DESIGN-CONTEXT.md so the gate returns `spawn: true`. The gate meaningfully short-circuits only on re-runs where the builder made no changes.
-
-**Parallel synthesizer note:** discover does not spawn parallel researchers in v1, so `skills/synthesize/` is not wired here. If future variants spawn N parallel interviewers/auto-detectors, wire synthesize between dispatch and collate as in `skills/map/` Step 3.5.
-
----
-
-## Step 2 - Spawn design-context-checker
-
-```
-Task("design-context-checker", """
-<required_reading>
-@.design/STATE.md
-@.design/DESIGN-CONTEXT.md
-</required_reading>
-
-You are the design-context-checker agent. Validate DESIGN-CONTEXT.md across
-6 dimensions. Return APPROVED or BLOCKED with per-dimension verdicts.
-
-Emit `## CONTEXT CHECK COMPLETE` when done.
-""")
-```
-
-Wait for `## CONTEXT CHECK COMPLETE`.
-
----
-
-## Step 3 - Handle checker verdict
-
-If APPROVED: proceed to state update.
-If BLOCKED: present dimensions that BLOCKED to user, offer fix-and-retry loop (re-spawn builder with specific fix instructions). Do not proceed to planning.
-
----
-
-## State Update (exit)
-
-1. Set <position> status=completed, task_progress=1/1.
-2. Set <timestamps> discover_completed_at=<ISO 8601 now>.
-3. Update last_checkpoint. Write STATE.md.
-
----
-
-## After Writing
-
-```
-=== Discovery complete ===
-Saved: .design/DESIGN-CONTEXT.md
-
-Baseline score: [N]/100 ([grade])
-Key issues: [top issue 1], [top issue 2], [top issue 3]
-
-Next: /get-design-done:plan
-  -> Decomposes your context into executable design tasks.
-==========================
-```
-
-Do not proceed to planning automatically unless `--auto` was passed.

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

@@ -1,96 +0,0 @@
----
-name: gdd-discuss
-description: "Adaptive design interview command that spawns design-discussant in normal / --all / --spec mode to gather decisions via one-question-at-a-time AskUserQuestion, writing D-XX entries to STATE.md <decisions>. Use when locking design decisions outside the main pipeline or backfilling missing context."
-argument-hint: "[topic] [--all] [--spec] [--cycle <name>]"
-tools: Read, Write, Task
----
-
-# /gdd:discuss
-
-**Role:** You are the `/gdd:discuss` command. You spawn the `design-discussant` agent with the right mode and context.
-
-## Step 1 - Read state
-
-Read `.design/STATE.md`. Note:
-- Current `cycle:` frontmatter value
-- Highest existing `D-XX` number under `<decisions>`
-
-If `.design/STATE.md` does not exist, tell the user to run `/gdd:brief` first and stop.
-
-## Step 2 - Parse arguments
-
-Inspect `$ARGUMENTS`:
-- Free-text before flags → `<topic>`
-- `--all` → batch gray-areas mode
-- `--spec` → Socratic ambiguity scoring mode
-- `--cycle <name>` → scope decisions to that cycle
-
-## Step 3 - Spawn design-discussant
-
-```
-Task("design-discussant", """
-<required_reading>
-@.design/STATE.md
-@.design/BRIEF.md
-@.design/DESIGN-CONTEXT.md
-@./.claude/skills
-</required_reading>
-
-<mode>{normal|--all|--spec}</mode>
-<topic>{topic or omit}</topic>
-<cycle>{cycle-name or omit}</cycle>
-
-Run an adaptive design interview. Append D-XX decisions to STATE.md <decisions> block.
-Emit `## DISCUSS COMPLETE` when done.
-""")
-```
-
-Use only the modes the user actually passed. Missing flags → `<mode>normal</mode>`.
-
-## Step 4 - Inline glossary maintenance (CONTEXT.md)
-
-When a fuzzy phrase is resolved into a sharper term, or a new domain concept is named
-during the interview: write to `./CONTEXT.md` IMMEDIATELY (do NOT batch). Use the schema
-in `./../../reference/context-md-format.md` - H2 heading per term, body paragraph,
-optional `**Aliases:**` line for term-merging. Multi-context repos use `CONTEXT-MAP.md`
-plus per-area `<area>/CONTEXT.md`. CONTEXT.md is lazy-created on the first term write.
-
-## Step 5 - Session wrap: ADR-offer scan
-
-For each decision recorded this session, check ALL three criteria from
-`./../../reference/adr-format.md`: (a) **hard-to-reverse**, (b) **surprising-without-context**,
-(c) **real-tradeoff**. If ALL three hold, offer to author `docs/adr/NNNN-<slug>.md`. If
-ANY criterion fails, the decision stays in STATE.md `<decisions>`. Routine choices are
-NEVER auto-promoted.
-
-## Step 6 - Report
-
-Wait for `## DISCUSS COMPLETE`. Re-read STATE.md. Count new D-XX entries since Step 1. Print:
-
-```
-━━━ Discuss complete ━━━
-New decisions: N (D-XX through D-YY)
-Mode: normal | --all | --spec
-Cycle: <name or "default">
-━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-## Constraints
-
-- Do not run the interview yourself - always spawn the agent.
-- Do not touch files outside `.design/`.
-
-## Rationalizations - Thought to Reality
-
-The shortcuts an agent takes during a discuss session, and what each one costs the decision record:
-
-| Thought | Reality |
-|---------|---------|
-| "I'll ask all eight questions at once to save time." | Batched questions overwhelm the user; one-at-a-time keeps each decision clean and prevents coupled answers. |
-| "I can run the interview inline instead of spawning the discussant." | The skill's contract is to always spawn the agent - running it yourself skips the discussant's mode handling and D-XX numbering. |
-| "This answer is good enough, I'll record it as a decision without follow-up." | A vague answer ("modern", "clean") recorded as a D-XX locks in an undecided premise; reject and re-ask once. |
-| "I'll batch all the new D-XX entries into STATE.md at the end." | Decisions written atomically per answer survive an interrupted session; batching loses everything if the session drops. |
-| "The glossary term can wait until I write the summary." | CONTEXT.md is written immediately per term - a deferred glossary entry is a naming inconsistency the next cycle inherits. |
-| "Every decision this session is worth an ADR." | ADRs require all three criteria (hard-to-reverse, surprising, real-tradeoff); auto-promoting routine choices buries the genuinely essential ones. |
-
-## DISCUSS COMMAND COMPLETE

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

@@ -1,45 +0,0 @@
----
-name: gdd-do
-description: "Natural-language design task router. Parses your intent, maps to the right gdd command(s), confirms before executing. Activates for requests involving a natural-language design request, routing intent to the right command, or not knowing which skill to use."
-argument-hint: "<natural language description>"
-tools: Read, Write, AskUserQuestion
----
-
-# /gdd:do
-
-Takes a free-form description, maps it to a `/gdd:*` command, confirms with the user, then routes.
-
-## Intent parsing table
-
-| Intent signals | Maps to |
-|---|---|
-| "explore", "scan", "what design patterns", "what components" | `/gdd:explore` |
-| "discuss", "decide", "what should we use for", "help me decide" | `/gdd:discuss` |
-| "plan", "create tasks", "what tasks do we need" | `@get-design-done plan` |
-| "design", "implement", "build", "execute" | `@get-design-done design` |
-| "verify", "check", "audit", "review" | `/gdd:audit` |
-| "sketch", "explore directions", "try designs", "variant" | `/gdd:sketch` |
-| "spike", "experiment", "feasibility", "test if" | `/gdd:spike` |
-| "fix [specific thing]" | `/gdd:fast` |
-| "pause", "stop", "save my place" | `/gdd:pause` |
-| "resume", "pick back up", "continue where I left off" | `/gdd:resume` |
-| "ship", "PR", "submit", "merge" | `/gdd:ship` |
-| "undo", "revert", "roll back" | `/gdd:undo` |
-
-## Steps
-
-1. Parse the argument text. Match it against the intent signals table. Choose the best fit.
-2. If two intents tie, ask (AskUserQuestion): "Did you mean <option A> or <option B>?"
-3. Print the routing decision in this exact shape:
-   ```
-   I'll run `/gdd:<command>` — "<one-line rationale>". Confirm? (yes/no)
-   ```
-4. On confirmation: invoke the target skill with any parameters extracted from the input (e.g., topic for `discuss`, symptom for `debug`).
-5. On rejection: ask "What did you mean instead?" and retry once, then abort gracefully.
-
-## Do Not
-
-- Do not execute the target command without confirmation.
-- Do not invent new commands - if no intent matches, say so and list the closest options.
-
-## DO COMPLETE

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

@@ -1,118 +0,0 @@
----
-name: gdd-explore
-description: "Stage 2 of 5 - unified exploration merging inventory grep + design interview. Probes 6 connections, scans the codebase, conducts the AskUserQuestion interview, and writes .design/DESIGN.md + DESIGN-DEBT.md + DESIGN-CONTEXT.md. Use after /gdd:brief to map the existing system and lock decisions before planning. Activates for requests involving researching design direction, gathering references, or exploring visual options."
-argument-hint: "[--skip-interview] [--skip-scan] [--incremental] [--full]"
-tools: Read, Write, Bash, Grep, Glob, Task, AskUserQuestion, mcp__gdd_state__get, mcp__gdd_state__transition_stage, mcp__gdd_state__probe_connections, mcp__gdd_state__update_progress, mcp__gdd_state__set_status, mcp__gdd_state__add_blocker, mcp__gdd_state__checkpoint, mcp__gdd_state__add_decision
----
-
-# Get Design Done - Explore
-
-**Role:** You are the Explore stage. Stage 2 of 5 in the get-design-done pipeline.
-
-**Purpose:** Unified exploration merging the former `scan` (inventory grep) and `discover` (context interview) stages. Produces `.design/DESIGN.md`, `.design/DESIGN-DEBT.md`, and `.design/DESIGN-CONTEXT.md`.
-
-Full procedure detail: `./explore-procedure.md`.
-
----
-
-## Stage entry
-
-All STATE.md persistence goes through `gdd-state` MCP tools - no direct edits. Plain design docs (DESIGN.md / DESIGN-DEBT.md / DESIGN-CONTEXT.md) use `Write`.
-
-1. `mcp__gdd_state__transition_stage` with `to: "explore"`. On gate failure: print blockers from `error.context.blockers` verbatim, do not advance.
-2. `mcp__gdd_state__get` (no args) -> snapshot `state` for downstream steps.
-
----
-
-## Step 1 - Connection probe
-
-Probe six connections, then batch-write results via ONE `mcp__gdd_state__probe_connections` call (unspecified connections keep their existing value):
-
-- **A - Figma** (variant-agnostic): ToolSearch + regex parse of `get_metadata` / `use_figma` prefixes -> tiebreaker selection (`both-sets > reads-only`, `figma > others`, `non-figma-desktop`, alphabetical) -> live `{prefix}get_metadata` call -> `available` / `unavailable` / `not_configured` (with `prefix=` + `writes=`).
-- **B - Refero**: ToolSearch presence sufficient.
-- **C - 21st.dev**: ToolSearch `mcp__21st` presence.
-- **D - Magic Patterns**: ToolSearch `mcp__magic_patterns` presence.
-- **E - paper.design**: ToolSearch `mcp__paper` + live `get_selection` call.
-- **F - pencil.dev**: `find . -name "*.pen"` file-presence.
-
-Full probe specs + commit-results JSON shape: `./explore-procedure.md` §Step 1.
-
-## Step 1.5 - 21st.dev Prior-Art Check (when `21st-dev: available`)
-
-For each greenfield component in scope: `21st_magic_component_search(component_name, limit: 3)`. Fit >= 80% -> add `<prior-art>` block to DESIGN.md recommending adoption; fit < 80% -> note as reference, build custom. If `svgl_get_brand_logo` available and brand assets are in scope, call per logo and save SVGs to `.design/assets/`. Skip entirely if no greenfield components in scope. Detail: `./explore-procedure.md` §Step 1.5.
-
----
-
-## Step 2 - Inventory scan (unless `--skip-scan`)
-
-**Map pre-check**: if `.design/map/` exists with all 5 files (`tokens.md`, `components.md`, `visual-hierarchy.md`, `a11y.md`, `motion.md`) fresher than `src/`, consume them and skip the grep pass. Otherwise grep and, after Step 4, suggest `/gdd:map` for the next cycle.
-
-**Parallelism decision**: read `.design/config.json` + `reference/parallelism-rules.md`. Record verdict via `mcp__gdd_state__set_status` (`"explore_parallel"` / `"explore_serial"`). Parallel -> multiple `Task()` in one response; serial -> sequential.
-
-**Incremental batching (Phase 53, default)**: `--incremental` (default; `--full` opts out) runs the change classifier first via the fingerprint store, groups the DesignContext graph into Louvain community batches, and dispatches mappers per the verdict (SKIP=0, PARTIAL=affected batches only, FULL=all). Engine: `scripts/lib/explore-parallel-runner` + `scripts/lib/mappers/incremental-discover.cjs`; dispatch concurrency comes from `concurrency-tuner.cjs`. Detail: `./explore-procedure.md` §Incremental Batching.
-
-Run the canonical scan grep/glob inventory (POSIX ERE, preserving PLAT-01/02): component detection (Glob `**/*.{tsx,jsx,vue,svelte}`), color extraction (hex / rgb / hsl / Tailwind arbitrary), typography scan (font-family / Tailwind `font-*` / `text-*`), motion scan (`transition` / `animate-` / `@keyframes` / `framer-motion`), token detection (tailwind.config / CSS custom properties / token JSON), layout detection (ordered fallback `src/` -> `app/` -> `pages/` -> `lib/` -> unknown). Write `.design/DESIGN.md` + `.design/DESIGN-DEBT.md`. Then `mcp__gdd_state__update_progress` for scan progress. Detail: `./explore-procedure.md` §Step 2.
-
-**Step 2.x - i18n readiness probe (informational, per D-04)**: check `package.json` deps against `{react-intl, next-intl, i18next, vue-i18n, formatjs, lingui}` -> `framework-managed`; else grep `Intl.(DateTimeFormat|NumberFormat|...)` in `src/` -> `partial`; else `none`. Emit single line `Localization readiness: <state>` in the report. NO gate, NO blocking - surface signal only (D-07). Detail: `./explore-procedure.md` §Step 2.x.
-
-## Step 2.5 - Detect prior sketches and project-local conventions
-
-- **Sketches**: list `.design/sketches/*` slugs, group by `WINNER.md` present (completed) vs absent (pending). Record via `mcp__gdd_state__set_status: "explore_sketches_present"`. Include in DESIGN.md "Prior Explorations" section.
-- **Project-local skills**: read `./.claude/skills/design-*-conventions.md` -> include in DESIGN-CONTEXT.md `<project_conventions>` (these override defaults).
-- **Global skills**: `~/.claude/gdd/global-skills/*.md` (other than README) -> prepend to `<project_conventions>` under `<global_conventions>` sub-block. Project-local D-XX wins on conflict.
-
-## Step 2.6 - Graph review (gate then reviewer)
-
-Runs only when Step 2's mapper batch + synthesizer produced `.design/context-graph.json`. Skip the whole step if the file is absent (pre-Phase-52 project, or `--skip-scan`).
-
-1. **Gate first (cheap Haiku check).** Spawn `design-context-reviewer-gate` via `Task()` with the classifier signal from Step 2's incremental batching pass: `change_pct` (fingerprint classifier `pct`), `classifier_action` (`SKIP` / `PARTIAL_UPDATE` / `ARCHITECTURE_UPDATE` / `FULL_UPDATE`), and `graph_path: ".design/context-graph.json"`. Gate emits a single-line `{spawn, rationale}` JSON decision then `## GATE COMPLETE`.
-2. **If `spawn: false`**: record `mcp__gdd_state__set_status: "explore_graph_review_skipped"`, log the gate `rationale` (e.g., "project change 3% < 5% threshold"), set telemetry `lazy_skipped: true`. Done - proceed to Step 3.
-3. **If `spawn: true`**: spawn `design-context-reviewer` via `Task()` with `<required_reading>` pointing at `.design/STATE.md`, `.design/context-graph.json`, `reference/design-context-schema.md`, `reference/design-context-tag-vocab.md`. The reviewer runs `scripts/validate-design-context.cjs --json` as the deterministic floor (checks 1/2/3/5) then layers the semantic checks (4/6/7/8/9) and returns the 9-check verdict inline (`APPROVED` or `REJECT`).
-4. **Capture verdict (read-only contract).** The reviewer does NOT write `.design/DESIGN-CONTEXT-REVIEW.md` - it is `reads-only: true, writes: []`. WARN findings surface through `scripts/lib/health-mirror#getHealthChecks` as `status: 'warn'`; a hard-reject maps to `status: 'fail'`. Record the overall verdict via `mcp__gdd_state__set_status: "explore_graph_review_approved"` (or `"_rejected"`).
-5. **On REJECT**: record `mcp__gdd_state__add_blocker` with the reviewer's blocking-issues list verbatim. Do not advance to Step 3 until the synthesizer or the implicated mapper is re-run. On `APPROVED` (with or without WARNs): proceed.
-
----
-
-## Step 3 - Design interview (unless `--skip-interview`)
-
-**Run inline - NEVER spawn `design-discussant` as a subagent.** `AskUserQuestion` only renders the native picker from the top-level skill context; spawning degrades to plain markdown (broken in Claude Desktop).
-
-- **3.a Pre-load context**: state.decisions snapshot -> BRIEF.md -> DESIGN.md -> DESIGN-CONTEXT.md `<gray_areas>` -> project conventions. If `figma: available`, call `{prefix}get_variable_defs` and draft tentative D-XX entries.
-- **3.b Identify question set**: skip areas already covered by D-XX or project convention. Default coverage: cycle goal, audience, brand direction (if no tokens), color/typography/spacing primitives (if undetected), motion preferences, gray areas from DESIGN-CONTEXT.md.
-- **3.c Ask one at a time**: `AskUserQuestion` with 4 concrete options + "Other" / "Skip". Reject generic answers ("modern", "clean") with one follow-up.
-- **3.d Record after each answer**: `mcp__gdd_state__add_decision` (atomic, auto-assigns D-NN); append a quality-classified JSON line to `.design/learnings/question-quality.jsonl`.
-- **3.e Produce DESIGN-CONTEXT.md**: summarize locked decisions, remaining gray areas, Figma tentatives. Frontmatter `status: complete`.
-
-Full interview protocol + JSON line schema: `./explore-procedure.md` §Step 3.
-
----
-
-## Step 4 - Close out explore
-
-- If the synthesizer / mapper batch ran in Step 2: `mcp__gdd_state__update_progress` with `task_progress: "<done>/<total>"`, `status: "explore_mappers_done"`.
-- If Step 2.6 ran the graph review: ensure the verdict status is recorded (`explore_graph_review_approved` / `_rejected` / `_skipped`); on `_rejected` do NOT checkpoint until re-run.
-- `mcp__gdd_state__checkpoint` - bumps `last_checkpoint`.
-- Stage advance to `plan` happens at the next stage's entry (plan owns its own `transition_stage`); do not edit frontmatter directly.
-
-## After Writing
-
-Print: "=== Explore complete ===\nSaved: .design/DESIGN.md, .design/DESIGN-DEBT.md, .design/DESIGN-CONTEXT.md\nNext: @get-design-done plan".
-
-<HARD-GATE>
-Do NOT transition to plan (or invoke `/gdd:plan`) until BOTH `.design/DESIGN.md` AND `.design/DESIGN-CONTEXT.md` are committed AND the user has approved them. If this project uses a custom `.design` location, read the artifact paths from `.design/STATE.md` rather than assuming the default.
-</HARD-GATE>
-
-## Rationalizations - Thought to Reality
-
-The shortcut excuses an agent reaches for during explore, and the drift each one introduces:
-
-| Thought | Reality |
-|---------|---------|
-| "I already know this codebase, I can skip the inventory scan." | An unscanned codebase hides the tokens/components you'll duplicate - the grep pass exists to stop you reinventing what's there. |
-| "The six connection probes are noise, I'll assume Figma is off." | A skipped probe means a wrong connection assumption silently breaks the design stage's tool dispatch. |
-| "`--skip-interview` is fine, the brief covered it." | The interview locks the gray areas the brief left fuzzy; skipping it ships undecided D-XX into planning. |
-| "I'll batch all the interview questions to save round-trips." | Batched questions overwhelm the user and smuggle in coupled assumptions - one-at-a-time keeps each decision clean. |
-| "DESIGN-DEBT.md is optional, the scan was clean enough." | Unrecorded debt resurfaces as an unexplained constraint three stages later with no provenance. |
-| "Prior sketches and project conventions don't apply this cycle." | Ignored conventions get overridden by defaults, producing inconsistency the audit will flag against the rest of the system. |
-
-## EXPLORE COMPLETE