msd-core/commands/gsd/discuss-phase.md at 851cddcc03078747d9217d480cd7ee93ac5d67a9

Files

Tom Boucher 851cddcc03 fix(#3131 ): re-wire 4 orphaned workflows as flags on parent commands

- discuss-phase --assumptions  → list-phase-assumptions.md
- pause-work --report          → session-report.md
- manager --analyze-deps       → analyze-dependencies.md
- import --from-gsd2           → gsd-tools.cjs from-gsd2 CLI

TDD: 8 new assertions in enh-2790-skill-consolidation.test.cjs
(argument-hint presence + body dispatch reference per flag).
Confirmed RED before wiring, GREEN after. Full suite 6971/6971.

help.md updated with all four new flag forms to satisfy
bug-2954-help-md-slash-command-stubs parity test.

Closes #3131

2026-05-05 10:51:10 -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.

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

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> Workflow files are loaded on-demand in the 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 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=$(gsd-sdk query config-get workflow.discuss_mode 2>/dev/null || echo "discuss") ```

If --assumptions is in $ARGUMENTS: Read and execute ~/.claude/get-shit-done/workflows/list-phase-assumptions.md end-to-end.

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

<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