msd-core/commands/gsd/discuss-phase.md at dced50d8876cb7dbe60c09dfc8dbeeb89bb11d48

Files

Tom Boucher 3d2c7ba39c feat(discuss): add --power flag for file-based bulk question answering (#1513 ) (#1611 )

- Add --power flag to discuss-phase command (argument-hint + description)
- Add power_user_mode routing section to discuss-phase.md workflow
- Create discuss-phase-power.md with full step-by-step workflow:
  analyze -> generate JSON -> generate HTML -> notify -> wait loop -> finalize
- QUESTIONS.json has phase/stats/sections/questions with id/title/options/answer/status
- QUESTIONS.html is self-contained with stats bar, collapsible sections, 3-col grid
- Refresh, finalize, explain, and exit-power-mode commands documented
- Add tests/discuss-phase-power.test.cjs (13 tests, node:test + node:assert)

Closes #1513

2026-04-03 13:16:06 -04:00

3.1 KiB

Raw Blame History

name, description, argument-hint, allowed-tools

name

description

argument-hint

allowed-tools

gsd:discuss-phase

Gather phase context through adaptive questioning before planning. 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).

<phase> [--auto] [--chain] [--batch] [--analyze] [--text] [--power]

Read

Write

Bash

Glob

Grep

AskUserQuestion

Task

mcp__context7__resolve-library-id

mcp__context7__query-docs

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

<execution_context> @~~/.claude/get-shit-done/workflows/discuss-phase.md @~~/.claude/get-shit-done/workflows/discuss-phase-assumptions.md @~~/.claude/get-shit-done/workflows/discuss-phase-power.md @~~/.claude/get-shit-done/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>

Phase number: $ARGUMENTS (required)

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

**Mode routing:** ```bash DISCUSS_MODE=$(node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" config-get workflow.discuss_mode 2>/dev/null || echo "discuss") ```

If DISCUSS_MODE is "assumptions": Read and execute @~/.claude/get-shit-done/workflows/discuss-phase-assumptions.md end-to-end.

If DISCUSS_MODE is "discuss" (or unset, or any other value): Read and execute @~/.claude/get-shit-done/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.

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

3.1 KiB Raw Blame History

3.1 KiB

Raw Blame History