Gsd Spike

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

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.

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.