Files
msd-core/docs/features/issue-driven-orchestration-guide.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

837 B

id, title, group
id title group
129 Issue-Driven Orchestration Guide v1.41.0 Features

Purpose: Document a recipe for driving the full MSD workflow from a GitHub / Linear / Jira issue, mapping tracker-centric concepts onto existing MSD primitives.

Document: docs/issue-driven-orchestration.md

Covered workflow:

  1. Create an isolated workspace per issue (/msd-workspace --new)
  2. Run the manager dashboard to get oriented (/msd-manager)
  3. Execute autonomously (/msd-autonomous)
  4. Verify and review (/msd-verify-work, /msd-review)
  5. Ship and close the issue (/msd-ship)

No new commands or daemon process — purely a documentation artifact that maps existing primitives onto a tracker-driven workflow.

Reference issue: #2840