golem15/msd-core
4
0
Fork 0
Code Issues 1 Pull Requests Actions 2 Packages Projects Releases Wiki Activity

fix(claude): restore namespaced /gsd:<command> references (#3452)

Browse Source 
* fix(claude): restore namespaced /gsd:<command> references

* test(claude): align slash-command expectations to /gsd: form

* test(claude): align generated command references to /gsd:

* test(claude): finish /gsd: namespace expectation updates
This commit is contained in:
Tom Boucher
2026-05-12 21:53:24 -04:00
committed by GitHub
parent 740d718941
commit a60e05c714
187 changed files with 1089 additions and 1142 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
agents/gsd-debug-session-manager.md
View File

@@ -1,6 +1,6 @@
---
name: gsd-debug-session-manager
description: Manages multi-cycle /gsd-debug checkpoint and continuation loop in isolated context. Spawns gsd-debugger agents, handles checkpoints via AskUserQuestion, dispatches specialist skills, applies fixes. Returns compact summary to main context. Spawned by /gsd-debug command.
description: Manages multi-cycle /gsd:debug checkpoint and continuation loop in isolated context. Spawns gsd-debugger agents, handles checkpoints via AskUserQuestion, dispatches specialist skills, applies fixes. Returns compact summary to main context. Spawned by /gsd:debug command.
tools: Read, Write, Bash, Grep, Glob, Agent, AskUserQuestion
color: orange
# hooks:
@@ -12,7 +12,7 @@ color: orange
---
<role>
You are the GSD debug session manager. You run the full debug loop in isolation so the main `/gsd-debug` orchestrator context stays lean.
You are the GSD debug session manager. You run the full debug loop in isolation so the main `/gsd:debug` orchestrator context stays lean.
**CRITICAL: Mandatory Initial Read**
Your first action MUST be to read the debug file at `debug_file_path`. This is your primary context.
@@ -55,7 +55,7 @@ Print:
## Step 2: Spawn gsd-debugger Agent
Fill and spawn the investigator with the same security-hardened prompt format used by `/gsd-debug`:
Fill and spawn the investigator with the same security-hardened prompt format used by `/gsd:debug`:
```markdown
<security_context>
@@ -158,7 +158,7 @@ Root cause identified:
How would you like to proceed?
1. Fix now — apply fix immediately
2. Plan fix — use /gsd-plan-phase --gaps
2. Plan fix — use /gsd:plan-phase --gaps
3. Manual fix — I'll handle it myself
```
@@ -297,7 +297,7 @@ If the session was abandoned by user choice, return:
**Cycles:** {N}
**TDD:** {yes/no}
**Specialist review:** {specialist_hint used, or "none"}
**Status:** ABANDONED — session saved for `/gsd-debug continue {slug}`
**Status:** ABANDONED — session saved for `/gsd:debug continue {slug}`
```
</process>