docs: update release notes and command reference for v1.37.0 (#2382)
* fix(tests): clear CLAUDECODE env var in read-guard test runner The hook skips its advisory on two env vars: CLAUDE_SESSION_ID and CLAUDECODE. runHook() cleared CLAUDE_SESSION_ID but inherited CLAUDECODE from process.env, so tests run inside a Claude Code session silently no-oped and produced no stdout, causing JSON.parse to throw. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(ci): update ARCHITECTURE.md counts and add TEXT_MODE fallback to sketch workflow Four new spike/sketch files were added in 1.37.0 but two housekeeping items were missed: ARCHITECTURE.md component counts (75→79 commands, 72→76 workflows) and the required TEXT_MODE fallback in sketch.md for non-Claude runtimes (#2012). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(ci): update directory-tree slash command count in ARCHITECTURE.md Missed the second count in the directory tree (# 75 slash commands → 79). The prose "Total commands" was updated but the tree annotation was not, causing command-count-sync.test.cjs to fail. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * docs: update release notes and command reference for v1.37.0 Covers spike/sketch commands, agent size-budget enforcement, and shared boilerplate extraction across README, COMMANDS, FEATURES, and USER-GUIDE. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Tom Boucher
@@ -8,6 +8,7 @@ A detailed reference for workflows, troubleshooting, and configuration. For quic
|
||||
|
||||
- [Workflow Diagrams](#workflow-diagrams)
|
||||
- [UI Design Contract](#ui-design-contract)
|
||||
- [Spiking & Sketching](#spiking--sketching)
|
||||
- [Backlog & Threads](#backlog--threads)
|
||||
- [Workstreams](#workstreams)
|
||||
- [Security](#security)
|
||||
@@ -259,6 +260,59 @@ Controlled by `workflow.ui_safety_gate` config toggle.
|
||||
|
||||
---
|
||||
|
||||
## Spiking & Sketching
|
||||
|
||||
Use `/gsd-spike` to validate technical feasibility before planning, and `/gsd-sketch` to explore visual direction before designing. Both store artifacts in `.planning/` and integrate with the project-skills system via their wrap-up companions.
|
||||
|
||||
### When to Spike
|
||||
|
||||
Spike when you're uncertain whether a technical approach is feasible or want to compare two implementations before committing a phase to one of them.
|
||||
|
||||
```
|
||||
/gsd-spike # Interactive intake — describes the question, you confirm
|
||||
/gsd-spike "can we stream LLM tokens through SSE"
|
||||
/gsd-spike --quick "websocket vs SSE latency"
|
||||
```
|
||||
|
||||
Each spike runs 2–5 experiments. Every experiment has:
|
||||
- A **Given / When / Then** hypothesis written before any code
|
||||
- **Working code** (not pseudocode)
|
||||
- A **VALIDATED / INVALIDATED / PARTIAL** verdict with evidence
|
||||
|
||||
Results land in `.planning/spikes/NNN-name/README.md` and are indexed in `.planning/spikes/MANIFEST.md`.
|
||||
|
||||
Once you have signal, run `/gsd-spike-wrap-up` to package the findings into `.claude/skills/spike-findings-[project]/` — future sessions will load them automatically via project-skills discovery.
|
||||
|
||||
### When to Sketch
|
||||
|
||||
Sketch when you need to compare layout structures, interaction models, or visual treatments before writing any real component code.
|
||||
|
||||
```
|
||||
/gsd-sketch # Mood intake — explores feel, references, core action
|
||||
/gsd-sketch "dashboard layout"
|
||||
/gsd-sketch --quick "sidebar navigation"
|
||||
/gsd-sketch --text "onboarding flow" # For non-Claude runtimes (Codex, Gemini, etc.)
|
||||
```
|
||||
|
||||
Each sketch answers **one design question** with 2–3 variants in a single `index.html` you open directly in a browser — no build step. Variants use tab navigation and shared CSS variables from `themes/default.css`. All interactive elements (hover, click, transitions) are functional.
|
||||
|
||||
After picking a winner, run `/gsd-sketch-wrap-up` to capture the visual decisions into `.claude/skills/sketch-findings-[project]/`.
|
||||
|
||||
### Spike → Sketch → Phase Flow
|
||||
|
||||
```
|
||||
/gsd-spike "SSE vs WebSocket" # Validate the approach
|
||||
/gsd-spike-wrap-up # Package learnings
|
||||
|
||||
/gsd-sketch "real-time feed UI" # Explore the design
|
||||
/gsd-sketch-wrap-up # Package decisions
|
||||
|
||||
/gsd-discuss-phase N # Lock in preferences (now informed by spike + sketch)
|
||||
/gsd-plan-phase N # Plan with confidence
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Backlog & Threads
|
||||
|
||||
### Backlog Parking Lot
|
||||
@@ -1108,6 +1162,14 @@ For reference, here is what GSD creates in your project:
|
||||
done/ # Completed todos
|
||||
debug/ # Active debug sessions
|
||||
resolved/ # Archived debug sessions
|
||||
spikes/ # Feasibility experiments (from /gsd-spike)
|
||||
NNN-name/ # Experiment code + README with verdict
|
||||
MANIFEST.md # Index of all spikes
|
||||
sketches/ # HTML mockups (from /gsd-sketch)
|
||||
NNN-name/ # index.html (2-3 variants) + README
|
||||
themes/
|
||||
default.css # Shared CSS variables for all sketches
|
||||
MANIFEST.md # Index of all sketches with winners
|
||||
codebase/ # Brownfield codebase mapping (from /gsd-map-codebase)
|
||||
phases/
|
||||
XX-phase-name/
|
||||
|
||||
Reference in New Issue
Block a user