Gather phase context through adaptive questioning before planning. Use --auto to skip interactive questions (Claude picks recommended defaults).
<cursor_skill_adapter>
gsd-discuss-phase or describes a task matching this skill.{{GSD_ARGS}}.{{GSD_ARGS}} as empty.When the workflow needs user input, prompt the user conversationally:
Use these Cursor tools when executing GSD workflows:
Shell for running commands (terminal operations)StrReplace for editing existing filesRead, Write, Glob, Grep, , , , as neededTaskWebSearchWebFetchTodoWriteWhen the workflow needs to spawn a subagent:
Task(subagent_type="generalPurpose", ...)model parameter maps to Cursor's model options (e.g., "fast")
</cursor_skill_adapter>How it works:
Output: {phase_num}-CONTEXT.md — decisions clear enough that downstream agents can act without asking the user again
</objective>
<execution_context> @/home/jmochel/pers/viracocha/.cursor/get-shit-done/workflows/discuss-phase.md @/home/jmochel/pers/viracocha/.cursor/get-shit-done/workflows/discuss-phase-assumptions.md @/home/jmochel/pers/viracocha/.cursor/get-shit-done/templates/context.md </execution_context>
Context files are resolved in-workflow using init phase-op and roadmap/state tool calls.
</context>
If DISCUSS_MODE is "assumptions": Read and execute @/home/jmochel/pers/viracocha/.cursor/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/jmochel/pers/viracocha/.cursor/get-shit-done/workflows/discuss-phase.md end-to-end.
MANDATORY: The execution_context files listed above ARE the instructions. Read the 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. </process>
<success_criteria>