Skill
gsd-discuss-phase
Gather phase context through adaptive questioning before planning. Use --auto to skip interactive questions (Codex picks recommended defaults). Use --chain for interactive discuss followed by automatic plan+execute. Use --power for bulk question generation into a file-based UI (answer at your own pace).
Trigger Phrases
No trigger phrases were parsed from this skill.
Structured Sections
Context
Phase number: $ARGUMENTS (required) Context files are resolved in-workflow using `init phase-op` and roadmap/state tool calls.
Process
**Mode routing:** ```bash DISCUSS_MODE=$(node "$HOME/.Codex/get-shit-done/bin/gsd-tools.cjs" config-get workflow.discuss_mode 2>/dev/null || echo "discuss") ``` If `DISCUSS_MODE` is `"assumptions"`: Read and execute @$HOME/.Codex/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/.Codex/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.
Objective
Extract implementation decisions that downstream agents need — researcher and planner will use CONTEXT.md to know what to investigate and what choices are locked. **How it works:** 1. Load prior context (PROJECT.md, REQUIREMENTS.md, STATE.md, prior CONTEXT.md files) 2. Scout codebase for reusable assets and patterns 3. Analyze phase — skip gray areas already decided in prior phases 4. Present remaining gray areas — user selects which to discuss 5. Deep-dive each selected area until satisfied 6. 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