Gsd:discuss Phase Skill for Claude

<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:

• 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

</objective>

<execution_context>

@${CLAUDE_PLUGIN_ROOT}/workflows/discuss-phase.md

@${CLAUDE_PLUGIN_ROOT}/workflows/discuss-phase-assumptions.md

@${CLAUDE_PLUGIN_ROOT}/workflows/discuss-phase-power.md

@${CLAUDE_PLUGIN_ROOT}/templates/context.md

</execution_context>

<runtime_note>

Copilot (VS Code): Use vscode_askquestions wherever this workflow calls AskUserQuestion. They are equivalent — vscode_askquestions is the VS Code Copilot implementation of the same interactive question API.

</runtime_note>

<context>

Phase number: $ARGUMENTS (required)

Context files are resolved in-workflow using init phase-op and roadmap/state tool calls.

</context>

<process>

Mode routing:

DISCUSS_MODE=$(gsd-sdk query config-get workflow.discuss_mode 2>/dev/null || echo "discuss")

If DISCUSS_MODE is "assumptions": Read and execute @${CLAUDE_PLUGIN_ROOT}/workflows/discuss-phase-assumptions.md end-to-end.

If DISCUSS_MODE is "discuss" (or unset, or any other value): Read and execute @${CLAUDE_PLUGIN_ROOT}/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>

• Prior context loaded and applied (no re-asking decided questions)
• Gray areas identified through intelligent analysis
• User chose which areas to discuss
• Each selected area explored until satisfied
• Scope creep redirected to deferred ideas
• CONTEXT.md captures decisions, not vague vision
• User knows next steps

</success_criteria>