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.
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Multi-agent orchestration in GSD Core
|
||||
# Multi-agent orchestration in MSD Core
|
||||
|
||||
> **Explanation** — This document describes *why* GSD Core is designed around
|
||||
> **Explanation** — This document describes *why* MSD Core is designed around
|
||||
> multi-agent orchestration and *how the pieces fit together*. It is not a
|
||||
> step-by-step guide. For configuration, see
|
||||
> [Configure model profiles](../how-to/configure-model-profiles.md) and the
|
||||
@@ -18,7 +18,7 @@ agent writes the fifth file in a complex task, it may have already forgotten
|
||||
the constraint stated in the first message. This is sometimes called *context
|
||||
rot*.
|
||||
|
||||
GSD Core's multi-agent design is a direct response to that problem. Instead of
|
||||
MSD Core's multi-agent design is a direct response to that problem. Instead of
|
||||
one long-running agent carrying the whole session, a thin orchestrator spawns
|
||||
short-lived specialised agents, each with a **fresh 200 K-token context window**
|
||||
and *only the artifacts it needs* to do its specific job. The orchestrator
|
||||
@@ -29,17 +29,17 @@ collects the result, and updates shared state in `.planning/`.
|
||||
|
||||
## The orchestrator → agent pattern
|
||||
|
||||
Every workflow in `gsd-core/workflows/` follows the same shape:
|
||||
Every workflow in `msd-core/workflows/` follows the same shape:
|
||||
|
||||
```text
|
||||
Orchestrator (workflow .md file)
|
||||
│
|
||||
├── Load context
|
||||
│ gsd-tools.cjs init <workflow> <phase>
|
||||
│ msd-tools.cjs init <workflow> <phase>
|
||||
│ → JSON: project info, config, state, phase details
|
||||
│
|
||||
├── Resolve model
|
||||
│ gsd-tools.cjs resolve-model <agent-name>
|
||||
│ msd-tools.cjs resolve-model <agent-name>
|
||||
│ → opus | sonnet | haiku | inherit
|
||||
│
|
||||
├── Spawn specialised agent (Task/SubAgent call)
|
||||
@@ -51,7 +51,7 @@ Orchestrator (workflow .md file)
|
||||
├── Collect result
|
||||
│
|
||||
└── Update state
|
||||
gsd-tools.cjs state update / state patch / state advance-plan
|
||||
msd-tools.cjs state update / state patch / state advance-plan
|
||||
```
|
||||
|
||||
The orchestrator is deliberately thin. It does not reason about the domain,
|
||||
@@ -61,19 +61,19 @@ the orchestrator's context from accumulating domain noise.
|
||||
|
||||
### The agent roster
|
||||
|
||||
GSD Core's agents fall into functional categories that map onto the
|
||||
MSD Core's agents fall into functional categories that map onto the
|
||||
research → plan → execute → verify pipeline:
|
||||
|
||||
| Category | Agents | Typical parallelism |
|
||||
|---|---|---|
|
||||
| Researchers | `gsd-project-researcher`, `gsd-phase-researcher`, `gsd-ui-researcher`, `gsd-advisor-researcher` | 4 parallel (stack, features, architecture, pitfalls) |
|
||||
| Synthesisers | `gsd-research-synthesizer` | Sequential, after researchers complete |
|
||||
| Planners | `gsd-planner`, `gsd-roadmapper` | Sequential |
|
||||
| Checkers | `gsd-plan-checker`, `gsd-integration-checker`, `gsd-ui-checker`, `gsd-nyquist-auditor` | Sequential, up to 3 revision iterations |
|
||||
| Executors | `gsd-executor` | Parallel within a wave, sequential across waves |
|
||||
| Verifiers | `gsd-verifier` | Sequential, after all executors complete |
|
||||
| Mappers | `gsd-codebase-mapper` | 4 parallel sub-probes |
|
||||
| Auditors | `gsd-ui-auditor`, `gsd-security-auditor` | Sequential |
|
||||
| Researchers | `msd-project-researcher`, `msd-phase-researcher`, `msd-ui-researcher`, `msd-advisor-researcher` | 4 parallel (stack, features, architecture, pitfalls) |
|
||||
| Synthesisers | `msd-research-synthesizer` | Sequential, after researchers complete |
|
||||
| Planners | `msd-planner`, `msd-roadmapper` | Sequential |
|
||||
| Checkers | `msd-plan-checker`, `msd-integration-checker`, `msd-ui-checker`, `msd-nyquist-auditor` | Sequential, up to 3 revision iterations |
|
||||
| Executors | `msd-executor` | Parallel within a wave, sequential across waves |
|
||||
| Verifiers | `msd-verifier` | Sequential, after all executors complete |
|
||||
| Mappers | `msd-codebase-mapper` | 4 parallel sub-probes |
|
||||
| Auditors | `msd-ui-auditor`, `msd-security-auditor` | Sequential |
|
||||
|
||||
Each agent definition (in `agents/*.md`) declares its allowed tool access,
|
||||
purpose, and colour for terminal output. An agent that only needs to read files
|
||||
@@ -87,7 +87,7 @@ For the complete agent roster, see [Inventory](../INVENTORY.md#agents).
|
||||
|
||||
## Wave-based parallel execution
|
||||
|
||||
The most visible expression of multi-agent design is how `/gsd-execute-phase`
|
||||
The most visible expression of multi-agent design is how `/msd-execute-phase`
|
||||
handles a set of plans that may depend on one another.
|
||||
|
||||
Before spawning any executor, the orchestrator performs a **wave analysis**:
|
||||
@@ -173,7 +173,7 @@ than diluted by noise from other pipeline stages.
|
||||
|
||||
**Context hygiene across sessions.** Because all state lives in
|
||||
`.planning/` as human-readable Markdown and JSON (not in any agent's context
|
||||
window), GSD workflows survive context resets (`/clear`), tab switches, and
|
||||
window), MSD workflows survive context resets (`/clear`), tab switches, and
|
||||
multi-day breaks. The next agent always starts from persisted, verified
|
||||
artifacts rather than from a reconstructed memory of a long conversation.
|
||||
|
||||
@@ -186,7 +186,7 @@ Multi-agent orchestration is not free.
|
||||
**Coordination overhead.** Each agent spawn is a round-trip: the orchestrator
|
||||
must format a prompt, hand off context, wait for the subagent to complete
|
||||
(typically 1–5 minutes), and then parse the result. A single capable agent
|
||||
working in one context would finish faster for simple tasks. GSD mitigates
|
||||
working in one context would finish faster for simple tasks. MSD mitigates
|
||||
this by making parallelism the default wherever dependencies permit — the
|
||||
four researchers in a `plan-phase` run simultaneously, not sequentially.
|
||||
|
||||
@@ -199,7 +199,7 @@ expectations.
|
||||
|
||||
**Context stitching cost.** Packaging the right artifacts for each agent
|
||||
requires the orchestrator to spend tokens assembling and transmitting context
|
||||
payloads. This is the cost of isolation. The `gsd-tools.cjs init` handler
|
||||
payloads. This is the cost of isolation. The `msd-tools.cjs init` handler
|
||||
produces a JSON payload that balances completeness with token budget, applying
|
||||
cache-friendly ordering so that the stable parts of the payload (project
|
||||
definition, config) hit the cache on repeat invocations.
|
||||
|
||||
Reference in New Issue
Block a user