Skip to main content
Generaldavepoon

gsd:discuss-phase

Gather phase context through adaptive questioning before planning. Use --all to skip area selection and discuss all gray areas interactively. Use --auto to skip interactive questions (Claude 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).

Stars
2,987
Source
davepoon/buildwithclaude
Updated
2026-05-26
Slug
davepoon--buildwithclaude--discuss-phase
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/davepoon/buildwithclaude/HEAD/plugins/gsd/skills/discuss-phase/SKILL.md -o .claude/skills/discuss-phase.md

Drops the SKILL.md into .claude/skills/discuss-phase.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

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

@${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 **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. Phase number: $ARGUMENTS (required)

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

**Mode routing:** ```bash 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.

- 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