How do I install the Gsddiscuss Phase skill?

Run npx skillmds@latest add davepoon/gsddiscuss-phase in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gsddiscuss Phase safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gsddiscuss Phase?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gsddiscuss Phase free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gsddiscuss Phase?

davepoon (@davepoon) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gsddiscuss Phase by davepoon — Agent Skill

Name: Gsddiscuss Phase
Rating: 4.2 (5 reviews)
Author: davepoon

Gsddiscuss 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).

davepoon Updated Sep 8, 2026

File contents

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

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

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.

Source: davepoon/buildwithclaude → plugins/gsd/skills/discuss-phase/SKILL.md

---name: gsddiscuss-phasedescription: 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).---<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 patterns3. Analyze phase — skip gray areas already decided in prior phases4. Present remaining gray areas — user selects which to discuss5. Deep-dive each selected area until satisfied6. 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:**```bashDISCUSS_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>---**Source:** [`davepoon/buildwithclaude`](https://github.com/davepoon/buildwithclaude) → `plugins/gsd/skills/discuss-phase/SKILL.md`

Frequently asked questions