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-processfor running commands (terminal operations)str-replace-editorfor editing existing filesviewfor reading files and listing directoriessave-filefor creating new filesgrepfor searching code (or use MCP servers for advanced search)web-search,web-fetchfor web queriesadd_tasks,view_tasklist,update_tasksfor 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
Mode routing:
- default (no flag): Add a new integer phase to the end of the current milestone → add-phase workflow
- --insert: Insert urgent work as a decimal phase (e.g., 72.1) between existing phases → insert-phase workflow
- --remove: Remove a future phase and renumber subsequent phases → remove-phase workflow
- --edit: Edit any field of an existing phase in place → edit-phase workflow
| Flag | Action | Workflow |
|---|---|---|
| (none) | Add new integer phase at end of milestone | add-phase |
| --insert | Insert decimal phase (e.g., 72.1) after specified phase | insert-phase |
| --remove | Remove future phase, renumber subsequent | remove-phase |
| --edit | Edit fields of existing phase in place | edit-phase |
Parse the first token of {{GSD_ARGS}}:
- If it is
--insert: strip the flag, pass remainder (format: ) to insert-phase workflow - If it is
--remove: strip the flag, pass remainder (phase number) to remove-phase workflow - If it is
--edit: strip the flag, pass remainder (phase-number [--force]) to edit-phase workflow - Otherwise: pass all of {{GSD_ARGS}} (phase description) to add-phase workflow
Roadmap and state are resolved in-workflow via init phase-op and targeted reads.