c86ca1b3eb
Spike workflow: - Add frontier mode (no-arg or "frontier" proposes integration + frontier spikes) - Add depth-over-speed principle — follow surprising findings, test edge cases, document investigation trail not just verdict - Add CONVENTIONS.md awareness — follow established patterns, update after session - Add Requirements section in MANIFEST — track design decisions as they emerge - Add re-ground step before each spike to prevent drift in long sessions - Add Investigation Trail section to README template - Restructured prior context loading with priority ordering - Research step now runs per-spike with briefing and approach comparison table Sketch workflow: - Add frontier mode (no-arg or "frontier" proposes consistency + frontier sketches) - Add spike context loading — ground mockups in real data shapes, requirements, and conventions from spike findings Spike wrap-up workflow: - Add CONVENTIONS.md generation step (recurring stack/structure/pattern choices) - Reference files now use implementation blueprint format (Requirements, How to Build It, What to Avoid, Constraints) - SKILL.md now includes requirements section from MANIFEST - Next-steps route to /gsd-spike frontier mode instead of inline analysis Sketch wrap-up workflow: - Next-steps route to /gsd-sketch frontier mode Commands updated with frontier mode in descriptions and argument hints. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
52 lines
1.8 KiB
Markdown
52 lines
1.8 KiB
Markdown
---
|
|
name: gsd:spike
|
|
description: Spike an idea through experiential exploration, or propose what to spike next (frontier mode)
|
|
argument-hint: "[idea to validate] [--quick] [--text] or [frontier]"
|
|
allowed-tools:
|
|
- Read
|
|
- Write
|
|
- Edit
|
|
- Bash
|
|
- Grep
|
|
- Glob
|
|
- AskUserQuestion
|
|
- WebSearch
|
|
- WebFetch
|
|
- mcp__context7__resolve-library-id
|
|
- mcp__context7__query-docs
|
|
---
|
|
<objective>
|
|
Spike an idea through experiential exploration — build focused experiments to feel the pieces
|
|
of a future app, validate feasibility, and produce verified knowledge for the real build.
|
|
Spikes live in `.planning/spikes/` and integrate with GSD commit patterns, state tracking,
|
|
and handoff workflows.
|
|
|
|
Two modes:
|
|
- **Idea mode** (default) — describe an idea to spike
|
|
- **Frontier mode** (no argument or "frontier") — analyzes existing spike landscape and proposes integration and frontier spikes
|
|
|
|
Does not require `/gsd-new-project` — auto-creates `.planning/spikes/` if needed.
|
|
</objective>
|
|
|
|
<execution_context>
|
|
@~/.claude/get-shit-done/workflows/spike.md
|
|
@~/.claude/get-shit-done/references/ui-brand.md
|
|
</execution_context>
|
|
|
|
<runtime_note>
|
|
**Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `AskUserQuestion`.
|
|
</runtime_note>
|
|
|
|
<context>
|
|
Idea: $ARGUMENTS
|
|
|
|
**Available flags:**
|
|
- `--quick` — Skip decomposition/alignment, jump straight to building. Use when you already know what to spike.
|
|
- `--text` — Use plain-text numbered lists instead of AskUserQuestion (for non-Claude runtimes).
|
|
</context>
|
|
|
|
<process>
|
|
Execute the spike workflow from @~/.claude/get-shit-done/workflows/spike.md end-to-end.
|
|
Preserve all workflow gates (prior spike check, decomposition, research, risk ordering, observability assessment, verification, MANIFEST updates, commit patterns).
|
|
</process>
|