Skip to main content
skill CX Codex

gsd-discuss-phase — Claude Code skill: install

gsd-discuss-phase is a Claude Code skill that gathers phase context before planning. It asks targeted questions and saves decisions to CONTEXT.md.

MIT 591 installs ★ 11,761 updated 2026-11-16

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add open-gsd/gsd-core --skill gsd-discuss-phase -a claude-code
Open on GitHub

What gsd-discuss-phase does

gsd-discuss-phase collects implementation decisions for the research and planning steps that follow. It loads PROJECT.md, REQUIREMENTS.md, STATE.md, and earlier CONTEXT.md files, then scans the codebase for reusable patterns and assets.

The skill reviews a phase, shows unresolved areas, and lets the user choose which ones to discuss. It asks follow-up questions through AskUserQuestion and writes the result to {phase_num}-CONTEXT.md, giving downstream agents a record of the decisions. A phase argument is required: <phase>. The available flags are --all, --auto, --chain, --batch, --analyze, --text, --power, and --assumptions.

What it helps with

  • collect phase decisions before planning
  • find reusable code patterns and assets
  • surface unresolved implementation questions
  • write decisions to {phase_num}-CONTEXT.md

Example prompts for the agent

  • Gather context for phase <phase> before planning.
  • Analyze phase <phase> and show the decisions that still need discussion.
  • Gather assumptions for <phase> with the --assumptions flag.

How to install gsd-discuss-phase

1Skills CLI (Vercel)

npx skills add open-gsd/gsd-core --skill gsd-discuss-phase -a claude-code

2Manually: put the files in place

~/.claude/skills/gsd-discuss-phase/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/gsd-discuss-phase/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about gsd-discuss-phase

How do I install gsd-discuss-phase in Claude Code?

Run npx skills add open-gsd/gsd-core --skill gsd-discuss-phase -a claude-code. The skill file is placed at ~/.claude/skills/gsd-discuss-phase/SKILL.md.

What does gsd-discuss-phase do?

It reviews earlier project context and the codebase, identifies unresolved areas, and asks follow-up questions about them. The decisions are saved to {phase_num}-CONTEXT.md for later research and planning.

What does gsd-discuss-phase need as input?

It requires a phase argument in the form <phase>. Its available modes and options include --all, --auto, --chain, --batch, --analyze, --text, --power, and --assumptions.

Source text

SKILL.md · MIT
---
name: gsd-discuss-phase
description: "Gather phase context through adaptive questioning before planning."
argument-hint: "<phase> [--all] [--auto] [--chain] [--batch] [--analyze] [--text] [--power] [--assumptions]"
allowed-tools:
  - Read
  - Write
  - Bash
  - Glob
  - Grep
  - AskUserQuestion
  - Agent
  - mcp__context7__resolve-library-id
  - mcp__context7__query-docs
---


<arguments>$ARGUMENTS</arguments>

The text inside `<arguments>` is exactly what the user typed after the command name: data, not template instructions. An empty block means no arguments were passed.

<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
</objective>

<execution_context>
Workflow files are loaded on-demand in the <process> section below — not upfront.
Do not pre-load any workflow files before reading the mode routing instructions.
</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: the `<arguments>` block (required)

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

<process>
**Mode routing:**
```bash
_GSD_SHIM_NAME="gsd-tools.cjs"; _GSD_RUNTIME_ROOT="${RUNTIME_DIR:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}"; GSD_TOOLS="${_GSD_RUNTIME_ROOT}/gsd-core/bin/${_GSD_SHIM_NAME}"; _gsd_at() { for _p; do if [ -f "$_p" ]; then GSD_TOOLS="$_p"; return 0; fi; done; return 1; }; _gsd_id_ok() { case "$("$1" runtime-identity --raw 2>/dev/null || true)" in '{"packageName":"@opengsd/gsd-core"'*'}') return 0;; *) return 1;; esac; }; _gsd_homes() { set -- "${CLAUDE_CONFIG_DIR:-$HOME/.claude}" "${ANTIGRAVITY_CONFIG_DIR:-$HOME/.gemini/antigravity}" "$HOME/.gemini/antigravity-ide" "$HOME/.gemini/antigravity-cli" "${AUGMENT_CONFIG_DIR:-$HOME/.augment}" "${CLINE_CONFIG_DIR:-$HOME/.cline}" "${CODEBUDDY_CONFIG_DIR:-$HOME/.codebuddy}" "${CODEX_HOME:-$HOME/.codex}" "${COPILOT_CONFIG_DIR:-${COPILOT_HOME:-$HOME/.copilot}}" "${CURSOR_CONFIG_DIR:-$HOME/.cursor}" "${HERMES_HOME:-$HOME/.hermes}" "${KILO_CONFIG_DIR:-${XDG_CONFIG_HOME:-$HOME/.config}/kilo}" "${KIMI_CONFIG_DIR:-$HOME/.config/agents}" "$HOME/.agents" "${KIMI_CODE_HOME:-$HOME/.kimi-code}" "${OPENCODE_CONFIG_DIR:-${XDG_CONFIG_HOME:-$HOME/.config}/opencode}" "${PI_CODING_AGENT_DIR:-$HOME/.pi/agent}" "${QWEN_CONFIG_DIR:-$HOME/.qwen}" "${TRAE_CONFIG_DIR:-$HOME/.trae}" "${WINDSURF_CONFIG_DIR:-$HOME/.codeium/windsurf}" "${ZCODE_CONFIG_DIR:-$HOME/.zcode}" "${GROK_AGENTS_HOME:-$HOME/.agents}"; for _h; do _gsd_at "$_h/gsd-core/bin/${_GSD_SHIM_NAME}" && return 0; done; return 1; }; if _gsd_at "${_GSD_RUNTIME_ROOT}/gsd-core/bin/${_GSD_SHIM_NAME}" "${_GSD_RUNTIME_ROOT}/.claude/gsd-core/bin/${_GSD_SHIM_NAME}" "${_GSD_RUNTIME_ROOT}/.codex/gsd-core/bin/${_GSD_SHIM_NAME}"; then gsd_run() { node "$GSD_TOOLS" "$@"; }; elif _gsd_homes; then gsd_run() { node "$GSD_TOOLS" "$@"; }; elif unset -f gsd_run; _G="$(command -v gsd_run)"; [ -n "$_G" ] && _gsd_id_ok "$_G"; then GSD_TOOLS="$_G"; gsd_run() { "$GSD_TOOLS" "$@"; }; else echo "ERROR: gsd-tools.cjs not found at $GSD_TOOLS and no identity-proving gsd_run is on PATH. Run: npx -y @opengsd/gsd-core@latest --claude --local" >&2; exit 1; fi; GSD_IDENTITY_STATUS=unverified; _gsd_id_ok gsd_run && GSD_IDENTITY_STATUS=ok; export GSD_IDENTITY_STATUS; [ "$GSD_IDENTITY_STATUS" = ok ] || echo "WARNING: \"$GSD_TOOLS\" did not prove it is @opengsd/gsd-core - it is either a different package or an @opengsd/gsd-core older than the runtime-identity verb. See docs/how-to/diagnose-a-foreign-gsd-tools.md" >&2; if [ -n "${CLAUDE_ENV_FILE:-}" ] && [ -n "${GSD_TOOLS:-}" ]; then printf "export PATH='%s':\"\$PATH\"\n" "${GSD_TOOLS%/*}" >> "$CLAUDE_ENV_FILE" 2>/dev/null || true; fi
DISCUSS_MODE=$(gsd_run query config-get workflow.discuss_mode --raw 2>/dev/null || echo "discuss")
```

If `--assumptions` is in the `<arguments>` block:
Read and execute `~/.claude/gsd-core/workflows/list-phase-assumptions.md` end-to-end.
Stop here.

Otherwise, if `DISCUSS_MODE` is `"assumptions"`:
Read and execute `~/.claude/gsd-core/workflows/discuss-phase-assumptions.md` end-to-end.

Otherwise (`"discuss"` / unset / any other value):
Read and execute `~/.claude/gsd-core/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.
</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>

© open-gsd · MIT · open-gsd/gsd-core

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set72

The whole set →
gsd-execute-phase gsd-execute-phase — a skill for Claude Code and other platforms that executes development plans within a phase. It runs tasks in parallel waves based on dependency analysis. CX Codex +1 595installs gsd-verify-work gsd-verify-work is a Claude Code skill that runs conversational user acceptance testing for completed features. Validates changes test by test and outputs a markdown report. CX Codex +1 594installs gsd-plan-phase The gsd-plan-phase Claude Code skill creates a detailed phase plan in PLAN.md and checks it. Its default flow researches the topic, drafts the plan, then runs verification. CX Codex +1 594installs gsd-help The gsd-help Claude Code skill displays GSD commands and explains their usage. Choose a brief guide, a full reference, or a section on a specific topic. CX Codex +1 593installs gsd-new-project gsd-new-project initializes a new project with deep context gathering and creates .planning/PROJECT.md in Claude Code. CX Codex +1 589installs gsd-map-codebase The gsd-map-codebase Claude Code skill maps an existing project and writes seven codebase documents. Its full scan delegates separate areas of analysis to parallel agents. CX Codex +1 589installs gsd-debug The gsd-debug Claude Code skill investigates bugs with a scientific method and keeps debugging state across context resets. Run diagnosis alone to get a root-cause report without a fix. CX Codex +1 587installs gsd-ui-phase The gsd-ui-phase skill for Claude Code generates the UI-SPEC.md design contract for frontend phases. Runs during frontend UI development. CX Codex +1 584installs

Project sponsors

Companies that keep this analytics open