Files
msd-core/docs/features/socratic-exploration.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

959 B

id, title, group
id title group
94 Socratic Exploration v1.34.0 Features

Command: /msd-explore [topic]

Purpose: Guide a developer through exploring an idea via Socratic probing questions before committing to a plan. Routes outputs to the appropriate MSD artifact: notes, todos, seeds, research questions, requirements updates, or a new phase.

Requirements:

  • REQ-EXPLORE-01: Exploration MUST use Socratic probing — ask questions before proposing solutions
  • REQ-EXPLORE-02: Session MUST offer to route outputs to the appropriate MSD artifact
  • REQ-EXPLORE-03: An optional topic argument MUST prime the first question
  • REQ-EXPLORE-04: Exploration MUST optionally spawn a research agent for technical feasibility
  • REQ-EXPLORE-05: A research pass MUST disposition each surfaced claim (admit / refute / abstain) and route every abstention to a visible Unresolved Ledger — never smoothing an ungrounded claim into the narrative as confident prose