Files
msd-core/docs/features/phase-discussion.md
Jakub Zych a9a7a328e6 refactor: hard-fork GSD -> MSD (Make Software Done)
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.
2026-10-06 01:47:40 +02:00

1.7 KiB

id, title, group
id title group
2 Phase Discussion Core Features

Command: /msd-discuss-phase [N] [--auto] [--batch]

Purpose: Capture user's implementation preferences and decisions before research and planning begin. Eliminates the gray areas that cause AI to guess.

Requirements:

  • REQ-DISC-01: System MUST analyze the phase scope and identify decision areas (gray areas)
  • REQ-DISC-02: System MUST categorize gray areas by type (visual, API, content, organization, etc.)
  • REQ-DISC-03: System MUST ask only questions not already answered in prior CONTEXT.md files
  • REQ-DISC-04: System MUST persist decisions in {phase}-CONTEXT.md with canonical references
  • REQ-DISC-05: System MUST support --auto flag to auto-select recommended defaults
  • REQ-DISC-06: System MUST support --batch flag for grouped question intake
  • REQ-DISC-07: System MUST scout relevant source files before identifying gray areas (code-aware discussion)
  • REQ-DISC-08: System MUST adapt gray area language to product-outcome terms when USER-PROFILE.md indicates a non-technical owner (learning_style: guided, jargon in frustration_triggers, or high-level explanation depth)
  • REQ-DISC-09: When REQ-DISC-08 applies, advisor_research rationale paragraphs MUST be rewritten in plain language — same decisions, translated framing

Produces: {padded_phase}-CONTEXT.md — User preferences that feed into research and planning

Gray Area Categories:

Category Example Decisions
Visual features Layout, density, interactions, empty states
APIs/CLIs Response format, flags, error handling, verbosity
Content systems Structure, tone, depth, flow
Organization Grouping criteria, naming, duplicates, exceptions