From f3d995112a42ed0b9abf853bb5f2df120d09530d Mon Sep 17 00:00:00 2001 From: Marcel Reschke Date: Thu, 12 Mar 2026 13:47:33 +0100 Subject: [PATCH] fix: replace broken read @GSD-WORKFLOW.md references with /gsd command (#88) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Line 5's 'When to read this' guidance updated to reflect the actual mechanism — the file is injected programmatically by /gsd, not read directly by the agent. Line 659's context-pressure resume instruction updated from: 'read @GSD-WORKFLOW.md - what\''s next?' to: 'run /gsd to pick up where you left off, or /gsd auto to resume in auto-execution mode.' The read @GSD-WORKFLOW.md instruction was broken — the file is not accessible via the read tool; it only enters context through dispatchWorkflow(). Users who followed the old instruction got nothing. Relates to #38 (same file, different problem). --- src/resources/GSD-WORKFLOW.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/resources/GSD-WORKFLOW.md b/src/resources/GSD-WORKFLOW.md index a08825abb..1afc58cb1 100644 --- a/src/resources/GSD-WORKFLOW.md +++ b/src/resources/GSD-WORKFLOW.md @@ -2,7 +2,7 @@ > This document teaches you how to operate the GSD planning methodology manually using files on disk. > -> **When to read this:** At the start of any session working on GSD-managed work, or when told `read @GSD-WORKFLOW.md`. +> **When to read this:** At the start of any session working on GSD-managed work, or when loaded by `/gsd`. > > **After reading this, always read `.gsd/state.md` to find out what's next.** > If the milestone has a `context.md`, read that too — it contains project-specific decisions, reference paths, and implementation guidance that this generic methodology doc does not. @@ -656,6 +656,6 @@ This methodology doc is generic. Project-specific guidance belongs in the milest If you sense context pressure (many files read, long execution, lots of tool output): -1. **If mid-task:** Write `continue.md` with exact resume state. Tell the user: "Context is getting full. I've saved progress to continue.md. Start a new session and say `read @GSD-WORKFLOW.md - what's next?`" +1. **If mid-task:** Write `continue.md` with exact resume state. Tell the user: "Context is getting full. I've saved progress to continue.md. Start a new session and run `/gsd` to pick up where you left off, or `/gsd auto` to resume in auto-execution mode." 2. **If between tasks:** Just update `state.md` with the next action. No continue file needed — the next session will read state.md and pick up the next task cleanly. 3. **Don't fight it.** The whole system is designed for this. A fresh session with the right files loaded is better than a stale session with degraded reasoning.