f983925eca
First-class GSD commands for rapid feasibility spiking and UI design sketching, ported from personal skills into the framework with full GSD integration: - Spikes save to .planning/spikes/, sketches to .planning/sketches/ - GSD banners, checkpoint boxes, Next Up blocks, gsd-sdk query commits - --quick flag skips intake/decomposition for both commands - Wrap-up commands package findings into project-local .claude/skills/ and write WRAP-UP-SUMMARY.md to .planning/ for project history - Neither requires /gsd-new-project — auto-creates .planning/ subdirs Pipeline integration: - new-project.md detects prior spike/sketch work on init - discuss-phase.md loads spike/sketch findings into prior context - plan-phase.md includes findings in planner <files_to_read> - do.md routes spike/sketch intent to new commands - explore.md offers spike/sketch as output routes - next.md surfaces pending spike/sketch work as notices - pause-work.md detects active sketch context for handoff - help.md documents all 4 commands with usage examples - artifact-types.md registers spike/sketch artifact taxonomy Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
5.5 KiB
<required_reading> Read all files referenced by the invoking prompt's execution_context before starting. </required_reading>
**Check for input.**Text mode (workflow.text_mode: true in config or --text flag): Set TEXT_MODE=true if --text is present in $ARGUMENTS OR text_mode from init JSON is true. When TEXT_MODE is active, replace every AskUserQuestion call with a plain-text numbered list and ask the user to type their choice number. This is required for non-Claude runtimes (OpenAI Codex, Gemini CLI, etc.) where AskUserQuestion is not available.
If $ARGUMENTS is empty, ask via AskUserQuestion:
What would you like to do? Describe the task, bug, or idea and I'll route it to the right GSD command.
Wait for response before continuing.
**Check if project exists.**INIT=$(gsd-sdk query state.load 2>/dev/null)
Track whether .planning/ exists — some routes require it, others don't.
Evaluate $ARGUMENTS against these routing rules. Apply the first matching rule:
| If the text describes... | Route to | Why |
|---|---|---|
| Starting a new project, "set up", "initialize" | /gsd-new-project |
Needs full project initialization |
| Mapping or analyzing an existing codebase | /gsd-map-codebase |
Codebase discovery |
| A bug, error, crash, failure, or something broken | /gsd-debug |
Needs systematic investigation |
| Spiking, "test if", "will this work", "experiment", "prove this out", validate feasibility | /gsd-spike |
Throwaway experiment to validate feasibility |
| Sketching, "mockup", "what would this look like", "prototype the UI", "design this", explore visual direction | /gsd-sketch |
Throwaway HTML mockups to explore design |
| Wrapping up spikes, "package the spikes", "consolidate spike findings" | /gsd-spike-wrap-up |
Package spike findings into reusable skill |
| Wrapping up sketches, "package the designs", "consolidate sketch findings" | /gsd-sketch-wrap-up |
Package sketch findings into reusable skill |
| Exploring, researching, comparing, or "how does X work" | /gsd-research-phase |
Domain research before planning |
| Discussing vision, "how should X look", brainstorming | /gsd-discuss-phase |
Needs context gathering |
| A complex task: refactoring, migration, multi-file architecture, system redesign | /gsd-add-phase |
Needs a full phase with plan/build cycle |
| Planning a specific phase or "plan phase N" | /gsd-plan-phase |
Direct planning request |
| Executing a phase or "build phase N", "run phase N" | /gsd-execute-phase |
Direct execution request |
| Running all remaining phases automatically | /gsd-autonomous |
Full autonomous execution |
| A review or quality concern about existing work | /gsd-verify-work |
Needs verification |
| Checking progress, status, "where am I" | /gsd-progress |
Status check |
| Resuming work, "pick up where I left off" | /gsd-resume-work |
Session restoration |
| A note, idea, or "remember to..." | /gsd-add-todo |
Capture for later |
| Adding tests, "write tests", "test coverage" | /gsd-add-tests |
Test generation |
| Completing a milestone, shipping, releasing | /gsd-complete-milestone |
Milestone lifecycle |
| A specific, actionable, small task (add feature, fix typo, update config) | /gsd-quick |
Self-contained, single executor |
Requires .planning/ directory: All routes except /gsd-new-project, /gsd-map-codebase, /gsd-spike, /gsd-sketch, /gsd-help, and /gsd-join-discord. If the project doesn't exist and the route requires it, suggest /gsd-new-project first.
Ambiguity handling: If the text could reasonably match multiple routes, ask the user via AskUserQuestion with the top 2-3 options. For example:
"Refactor the authentication system" could be:
1. /gsd-add-phase — Full planning cycle (recommended for multi-file refactors)
2. /gsd-quick — Quick execution (if scope is small and clear)
Which approach fits better?
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
GSD ► ROUTING
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
**Input:** {first 80 chars of $ARGUMENTS}
**Routing to:** {chosen command}
**Reason:** {one-line explanation}
Run the selected /gsd-* command, passing $ARGUMENTS as args.
If the chosen command expects a phase number and one wasn't provided in the text, extract it from context or ask via AskUserQuestion.
After invoking the command, stop. The dispatched command handles everything from here.
<success_criteria>
- Input validated (not empty)
- Intent matched to exactly one GSD command
- Ambiguity resolved via user question (if needed)
- Project existence checked for routes that require it
- Routing decision displayed before dispatch
- Command invoked with appropriate arguments
- No work done directly — dispatcher only </success_criteria>