Gdd Sketch Wrap Up

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. See ./reference/cycle-handoff-preamble.md for the cycle-handoff framing this decision-archive feeds into.

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 {{command_prefix}}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 in sequence:

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):

markdownCopy code
# Design <Area> Conventions (Project-Local)

Auto-loaded in gdd sessions. Captures decisions codified from `{{command_prefix}}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 with: # Winner: variant-N, then bold-prefixed fields Slug, Area, Rationale, Captured (YYYY-MM-DD), Project skill written to (path from Step 5).

Step 7 - Append D-XX + <prototyping> outcome to STATE.md

Two coupled writes - both must succeed so the sketch resolution surfaces in both <decisions> (all downstream stages) and <prototyping> (planner-specific context via decision-injector). Compute D-XX as max existing D-NN + 1 (scan <decisions> for D-\d+:, zero-pad to 2 digits).

• Write 1 (<decisions>): D-XX: sketch/<slug> — winner: variant-N — <rationale> (locked)\n Source: .design/sketches/<slug>/WINNER.md
• Write 2 (<prototyping>): <sketch slug="<slug>" cycle="<cycle>" decision="D-XX" status="resolved"/>. <cycle> from STATE.md frontmatter; empty string valid for single-cycle Wave A projects. If <prototyping> block does not exist, materialize between <must_haves> and <connections> per STATE template; append the <sketch …/> as first child.

Prefer MCP gdd_state typed mutators (byte-identical output): mcp__gdd_state__add_decision({id, text, status}) + mcp__gdd_state__add_prototyping({type:"sketch", slug, cycle, decision, status}). Without MCP, edit .design/STATE.md directly via Read + Write.

Step 8 - Update sketches SUMMARY.md

Append to .design/sketches/SUMMARY.md (create if missing):

Copy code
- <slug> (YYYY-MM-DD) — winner: variant-N — area: <area> — D-XX — <one-line rationale>

After writing

Copy code
━━━ Sketch wrapped ━━━
Slug: <slug>
Winner: variant-N
Area: <area>
Decision recorded: D-XX
Prototyping entry: <sketch slug="<slug>" cycle="<cycle>" decision="D-XX" status="resolved"/>
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