a9a7a328e6
Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD across contents and paths, upstream package/repo coordinates -> @golem15/msd-core and golem15com/msd-core. Deep links into upstream history, sibling upstream packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is. Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line, package/plugin identity, regenerated lockfile, install-tree fixtures, derived registries and benchmark baseline; migration checksum baseline re-locked (MSD keeps its own install state, so no install had applied the old sums); sort-order and regex-escaped expectations in tests adjusted.
3.6 KiB
Discuss Mode: Assumptions vs Interview
MSD Core's discuss-phase offers two modes for gathering implementation context before planning begins. Understanding when to use each helps you move from question-answering to a confirmed CONTEXT.md with less back-and-forth.
For step-by-step instructions on running either mode, see the Discuss a phase how-to.
Modes
discuss (default)
The original interview-style flow. Claude identifies grey areas in the phase, presents them for selection, then asks approximately four questions per area. Good for:
- Early phases where the codebase is new
- Phases where the user has strong opinions they want to express proactively
- Users who prefer guided, conversational context gathering
assumptions
A codebase-first flow. Claude deeply analyses the codebase via a subagent (reading 5–15 relevant files), forms assumptions with evidence, and presents them for confirmation or correction. Good for:
- Established codebases with clear patterns
- Users who find the interview questions obvious
- Faster context gathering (~2–4 interactions vs ~15–20)
Configuration
# Enable assumptions mode
node msd-tools.cjs config-set workflow.discuss_mode assumptions
# Switch back to interview mode
node msd-tools.cjs config-set workflow.discuss_mode discuss
The setting is per-project (stored in .planning/config.json). See the CONTEXT.md schema for the full structure of the file both modes produce.
How Assumptions Mode Works
- Init — Same as discuss mode (load prior context, scout codebase, check todos)
- Deep analysis — Explore subagent reads 5–15 codebase files related to the phase
- Surface assumptions — Each assumption includes:
- What Claude would do and why (citing file paths)
- What goes wrong if the assumption is incorrect
- Confidence level (Confident / Likely / Unclear)
- Confirm or correct — User reviews assumptions, selects any that need changing
- Write CONTEXT.md — Identical output format to discuss mode
Flag Compatibility
| Flag | discuss mode |
assumptions mode |
|---|---|---|
--auto |
Auto-selects recommended answers | Skips confirm gate, auto-resolves Unclear items |
--batch |
Groups questions in batches | N/A (corrections already batched) |
--text |
Plain-text questions (remote sessions) | Plain-text questions (remote sessions) |
--analyze |
Shows trade-off tables per question | N/A (assumptions include evidence) |
Output
Both modes produce an identical CONTEXT.md with the same six sections:
<domain>— Phase boundary<decisions>— Locked implementation decisions<canonical_refs>— Specs/docs downstream agents must read<code_context>— Reusable assets, patterns, integration points<specifics>— User references and preferences<deferred>— Ideas noted for future phases
Downstream agents (researcher, planner, checker) consume this file identically regardless of which mode produced it. See the CONTEXT.md schema for the full field reference.
Related
- Discuss a phase — step-by-step how-to for running
/msd-discuss-phasein either mode. - CONTEXT.md schema — full field reference for the file both modes produce.
- The phase loop — how discuss fits into the broader discuss → plan → execute → verify → ship cycle.
- docs index — full table of contents for MSD Core documentation.