gsd-spike

name	gsd-spike
description	Spike an idea through experiential exploration, or propose what to spike next (frontier mode)

<augment_skill_adapter>

A. Skill Invocation

• This skill is invoked when the user mentions gsd-spike or describes a task matching this skill.
• Treat all user text after the skill mention as {{GSD_ARGS}}.
• If no arguments are present, treat {{GSD_ARGS}} as empty.

B. User Prompting

When the workflow needs user input, prompt the user conversationally:

• Present options as a numbered list in your response text
• Ask the user to reply with their choice
• For multi-select, ask for comma-separated numbers

C. Tool Usage

Use these Augment tools when executing GSD workflows:

• launch-process for running commands (terminal operations)
• str-replace-editor for editing existing files
• view for reading files and listing directories
• save-file for creating new files
• grep for searching code (or use MCP servers for advanced search)
• web-search, web-fetch for web queries
• add_tasks, view_tasklist, update_tasks for task management

D. Subagent Spawning

When the workflow needs to spawn a subagent:

• Use the built-in subagent spawning capability
• Define agent prompts in .augment/agents/ directory </augment_skill_adapter>

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.

<execution_context> @/home/delorenj/code/bhappy/.augment/get-shit-done/workflows/spike.md @/home/delorenj/code/bhappy/.augment/get-shit-done/references/ui-brand.md </execution_context>

<runtime_note> Copilot (VS Code): Use vscode_askquestions wherever this workflow calls conversational prompting. </runtime_note>

Idea: {{GSD_ARGS}}

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 conversational prompting (for non-Claude runtimes).
• --wrap-up — Package spike findings into a persistent project skill for future build conversations. Runs the spike-wrap-up workflow.

Execute the spike workflow from @/home/delorenj/code/bhappy/.augment/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).