msd-core/.changeset/archived/issue-driven-orchestration.md at 837991d5a298695ee8c69b10d1fdb1d8e6b41084

Files

Tom Boucher 8616839cab chore: archive 463 shipped changeset fragments before wiring render (#714 )

CHANGELOG promotion was a manual operator step that was never run, so 463
fragments for work already shipped in <=1.3.1 accumulated in .changeset/.
Their notes were already hand-curated into the dated [1.2.0]/[1.3.0]/[1.3.1]
CHANGELOG sections (#690 backfill, PR #694). Rendering them now would
duplicate and mis-attribute shipped work.

Move them to .changeset/archived/ (read non-recursively by all changeset
tooling, so never rendered), keeping only the 3 genuinely-unreleased
fragments at the top level. Prep for wiring `render` into the release
finalize job (#690 follow-up).

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-05 14:53:17 -04:00

510 B

Raw Blame History

type, pr

type	pr
Added	2840

docs/issue-driven-orchestration.md — recipe for driving GSD from a tracker issue — new guide that maps Symphony-style orchestration concepts (workflow, isolated agent workspace, proof-of-work, human review gate, follow-up capture) onto existing GSD primitives (/gsd-new-workspace, /gsd-manager, /gsd-autonomous, /gsd-verify-work, /gsd-review, /gsd-ship, STATE.md, phase artifacts). Documentation only — no new commands, no daemon, no tracker integration.

510 B Raw Blame History

510 B

Raw Blame History