Gsd:discuss phase

Planlamadan önce uyarlanabilir sorgulama yoluyla aşama bağlamını toplayın. Alan seçimini atlamak ve tüm gri alanları etkileşimli olarak tartışmak için --all seçeneğini kullanın. Etkileşimli soruları atlamak için --auto kullanın (Claude önerilen varsayılanları seçer). Etkileşimli tartışma için --chain ve ardından otomatik plan+yürütme komutunu kullanın. Dosya tabanlı bir kullanıcı arayüzünde toplu soru oluşturmak için --power kullanın (kendi hızınızda yanıtlayın).

yazan kuscubasiece·8 Eylül 2026

Kaynak: davepoon/claude-code-subagents-collection · MIT

Kurulum

mkdir -p .claude/skills/gsd-discuss-phase && curl -sL https://www.antrophiclove.com/api/kaynak/gsd-discuss-phase/raw -o .claude/skills/gsd-discuss-phase/SKILL.md

Hedef dosya: .claude/skills/gsd-discuss-phase/SKILL.md

Önizleme Ham metin ⑂ Kendi sürümünü oluştur

---
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]"
allowed-tools:
  - Read
  - Write
  - Bash
  - Glob
  - Grep
  - AskUserQuestion
  - Task
  - mcp__context7__resolve-library-id
  - mcp__context7__query-docs
---

<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>
@${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:**
```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.
</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>