jnuyens/gsd:discuss-phase
skills/discuss-phase/SKILL.md
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).
$ install --global
skillsauthnpx skillsauth add jnuyens/gsd-plugin gsd:discuss-phaseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 13, 2026, 2:15 AM27.1s1 file scanned
SKILL.md
- name:
- gsd:discuss-phase
- description:
- 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).
- argument-hint:
- <phase> [--all] [--auto] [--chain] [--batch] [--analyze] [--text] [--power]
<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 files are resolved in-workflow using init phase-op and roadmap/state tool calls.
</context>
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: Read the routed workflow file BEFORE taking any action — it is the complete process. The objective and success_criteria sections here are summaries; do not improvise from them. </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>
Related Skills
jnuyens/gsd:new-ddd
tools
VerifiedTrustedCommunity
Initialize a new project using Documentation-Driven Development. Research, then write user-facing docs (SPEC.md) as the spec, then user validates docs, then phases derive from doc sections. Best for CLIs, libraries, SDKs, APIs, plugin systems, anything with a well-defined user-facing surface.
71SKILL.mdUpdated May 25, 2026
jnuyens/gsd:resume-at
tools
VerifiedTrustedCommunity
Schedule a future resume of work - e.g. '/gsd:resume-at 09:00', '/gsd:resume-at +2h', or '/gsd:resume-at 04:00 --cmd /gsd:execute-phase 9'
71SKILL.mdUpdated Apr 28, 2026
jnuyens/gsd:workstreams
tools
VerifiedTrustedCommunity
Manage parallel workstreams — list, create, switch, status, progress, complete, and resume
71SKILL.mdUpdated Apr 26, 2026
jnuyens/gsd:thread
tools
VerifiedTrustedCommunity
Manage persistent context threads for cross-session work
71SKILL.mdUpdated Apr 26, 2026