How do I install the Gsd Discuss Phase skill?

Run npx skillmds@latest add vs4vijay/gsd-discuss-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.

What does the Gsd Discuss Phase skill do?

Gather phase context through adaptive questioning before planning. It is listed under Coding & Dev Tools on SkillMD.

Is Gsd Discuss Phase safe to use?

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

Which AI agents work with Gsd Discuss 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 Gsd Discuss Phase free to use?

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

Who published Gsd Discuss Phase?

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

Gsd Discuss Phase by vs4vijay — Agent Skill

Name: Gsd Discuss Phase
Author: vs4vijay

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 --assumptions is in $ARGUMENTS: Read and execute /Volumes/Main/GitHub/vibecoding/skills/.opencode/gsd-core/workflows/list-phase-assumptions.md end-to-end. Stop here.

Otherwise, if DISCUSS_MODE is "assumptions": Read and execute /Volumes/Main/GitHub/vibecoding/skills/.opencode/gsd-core/workflows/discuss-phase-assumptions.md end-to-end.

Otherwise ("discuss" / unset / any other value): Read and execute /Volumes/Main/GitHub/vibecoding/skills/.opencode/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.

---name: gsd-discuss-phasedescription: Gather phase context through adaptive questioning before planning.---<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>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 `question`. 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:**```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}"; if [ -f "$GSD_TOOLS" ]; then gsd_run() { node "$GSD_TOOLS" "$@"; }; elif [ -f "${_GSD_RUNTIME_ROOT}/.claude/gsd-core/bin/${_GSD_SHIM_NAME}" ]; then GSD_TOOLS="${_GSD_RUNTIME_ROOT}/.claude/gsd-core/bin/${_GSD_SHIM_NAME}"; gsd_run() { node "$GSD_TOOLS" "$@"; }; elif command -v gsd-tools >/dev/null 2>&1; then GSD_TOOLS="$(command -v gsd-tools)"; gsd_run() { "$GSD_TOOLS" "$@"; }; elif [ -f "/Volumes/Main/GitHub/vibecoding/skills/.opencode/gsd-core/bin/${_GSD_SHIM_NAME}" ]; then GSD_TOOLS="/Volumes/Main/GitHub/vibecoding/skills/.opencode/gsd-core/bin/${_GSD_SHIM_NAME}"; gsd_run() { node "$GSD_TOOLS" "$@"; }; else echo "ERROR: gsd-tools.cjs not found at $GSD_TOOLS and gsd-tools is not on PATH. Run: npx -y @opengsd/gsd-core@latest --claude --local" >&2; exit 1; fiDISCUSS_MODE=$(gsd_run query config-get workflow.discuss_mode 2>/dev/null || echo "discuss")```If `--assumptions` is in $ARGUMENTS:Read and execute `/Volumes/Main/GitHub/vibecoding/skills/.opencode/gsd-core/workflows/list-phase-assumptions.md` end-to-end.Stop here.Otherwise, if `DISCUSS_MODE` is `"assumptions"`:Read and execute `/Volumes/Main/GitHub/vibecoding/skills/.opencode/gsd-core/workflows/discuss-phase-assumptions.md` end-to-end.Otherwise (`"discuss"` / unset / any other value):Read and execute `/Volumes/Main/GitHub/vibecoding/skills/.opencode/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>

Frequently asked questions

Gsd Discuss Phase