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
How it works:
- Load prior context (PROJECT.md, REQUIREMENTS.md, STATE.md, prior CONTEXT.md files)
- Scout codebase for reusable assets and patterns
- Analyze phase — skip gray areas already decided in prior phases
- Present remaining gray areas — user selects which to discuss
- Deep-dive each selected area until satisfied
- Create CONTEXT.md with decisions that guide research and planning
Output: {phase_num}-CONTEXT.md — decisions clear enough that downstream agents can act without asking the user again
Context files are resolved in-workflow using init phase-op and roadmap/state tool calls.
If DISCUSS_MODE is "assumptions":
Read and execute /home/delorenj/code/bhappy/.augment/get-shit-done/workflows/discuss-phase-assumptions.md end-to-end.
If DISCUSS_MODE is "discuss" (or unset, or any other value):
Read and execute /home/delorenj/code/bhappy/.augment/get-shit-done/workflows/discuss-phase.md end-to-end.
MANDATORY: Read the appropriate workflow file BEFORE taking any action. The objective and success_criteria sections in this command file are summaries — the workflow file contains the complete step-by-step process with all required behaviors, config checks, and interaction patterns. Do not improvise from the summary.
Lazy loading: templates/context.md is loaded inside the write_context step of the active workflow. discuss-phase-power.md is loaded inside discuss-phase.md when --power is detected. Do not load either here.