* feat(gsd-tools): add compound init commands for workflow setup Adds 8 compound commands that return all context a workflow needs in one JSON blob, replacing 5-10 atomic calls per workflow: - init execute-phase: models, config, phase info, plan inventory - init plan-phase: models, workflow flags, existing artifacts - init new-project: models, brownfield detection, state checks - init new-milestone: models, milestone info - init quick: models, next task number, timestamps - init resume: file existence, interrupted agent - init verify-work: models, phase info - init phase-op: generic phase context Updated 8 workflows to use compound commands: - execute-phase, plan-phase, new-project, quick - resume-project, verify-work, discuss-phase Token savings: ~200 lines of bash setup replaced with single init calls. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat(gsd-tools): add 4 new init commands and update files to use compound commands Add new compound init commands: - init todos - context for todo workflows - init milestone-op - context for milestone operations - init map-codebase - context for codebase mapping - init progress - context for progress workflow Update 24 files to use compound init commands instead of atomic calls: - 4 phase operation workflows (add-phase, insert-phase, remove-phase, verify-phase) - 5 todo/milestone workflows (add-todo, check-todos, audit-milestone, complete-milestone, new-milestone) - 6 misc workflows (execute-plan, map-codebase, pause-work, progress, set-profile, settings) - 6 agent files (gsd-executor, gsd-planner, gsd-phase-researcher, gsd-plan-checker, gsd-debugger, gsd-research-synthesizer) - 2 command files (debug, research-phase) - 1 reference file (planning-config) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix(gsd-tools): add init to help output Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix(verify-phase): correct expected init fields The workflow was referencing plans/summaries from init phase-op, but those fields come from ls command. Updated to reference has_plans and plan_count which are actually in phase-op output. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
163 lines
3.5 KiB
Markdown
163 lines
3.5 KiB
Markdown
---
|
|
name: gsd:debug
|
|
description: Systematic debugging with persistent state across context resets
|
|
argument-hint: [issue description]
|
|
allowed-tools:
|
|
- Read
|
|
- Bash
|
|
- Task
|
|
- AskUserQuestion
|
|
---
|
|
|
|
<objective>
|
|
Debug issues using scientific method with subagent isolation.
|
|
|
|
**Orchestrator role:** Gather symptoms, spawn gsd-debugger agent, handle checkpoints, spawn continuations.
|
|
|
|
**Why subagent:** Investigation burns context fast (reading files, forming hypotheses, testing). Fresh 200k context per investigation. Main context stays lean for user interaction.
|
|
</objective>
|
|
|
|
<context>
|
|
User's issue: $ARGUMENTS
|
|
|
|
Check for active sessions:
|
|
```bash
|
|
ls .planning/debug/*.md 2>/dev/null | grep -v resolved | head -5
|
|
```
|
|
</context>
|
|
|
|
<process>
|
|
|
|
## 0. Initialize Context
|
|
|
|
```bash
|
|
INIT=$(node ~/.claude/get-shit-done/bin/gsd-tools.js state load)
|
|
```
|
|
|
|
Extract `commit_docs` from init JSON. Resolve debugger model:
|
|
```bash
|
|
DEBUGGER_MODEL=$(node ~/.claude/get-shit-done/bin/gsd-tools.js resolve-model gsd-debugger --raw)
|
|
```
|
|
|
|
## 1. Check Active Sessions
|
|
|
|
If active sessions exist AND no $ARGUMENTS:
|
|
- List sessions with status, hypothesis, next action
|
|
- User picks number to resume OR describes new issue
|
|
|
|
If $ARGUMENTS provided OR user describes new issue:
|
|
- Continue to symptom gathering
|
|
|
|
## 2. Gather Symptoms (if new issue)
|
|
|
|
Use AskUserQuestion for each:
|
|
|
|
1. **Expected behavior** - What should happen?
|
|
2. **Actual behavior** - What happens instead?
|
|
3. **Error messages** - Any errors? (paste or describe)
|
|
4. **Timeline** - When did this start? Ever worked?
|
|
5. **Reproduction** - How do you trigger it?
|
|
|
|
After all gathered, confirm ready to investigate.
|
|
|
|
## 3. Spawn gsd-debugger Agent
|
|
|
|
Fill prompt and spawn:
|
|
|
|
```markdown
|
|
<objective>
|
|
Investigate issue: {slug}
|
|
|
|
**Summary:** {trigger}
|
|
</objective>
|
|
|
|
<symptoms>
|
|
expected: {expected}
|
|
actual: {actual}
|
|
errors: {errors}
|
|
reproduction: {reproduction}
|
|
timeline: {timeline}
|
|
</symptoms>
|
|
|
|
<mode>
|
|
symptoms_prefilled: true
|
|
goal: find_and_fix
|
|
</mode>
|
|
|
|
<debug_file>
|
|
Create: .planning/debug/{slug}.md
|
|
</debug_file>
|
|
```
|
|
|
|
```
|
|
Task(
|
|
prompt=filled_prompt,
|
|
subagent_type="gsd-debugger",
|
|
model="{debugger_model}",
|
|
description="Debug {slug}"
|
|
)
|
|
```
|
|
|
|
## 4. Handle Agent Return
|
|
|
|
**If `## ROOT CAUSE FOUND`:**
|
|
- Display root cause and evidence summary
|
|
- Offer options:
|
|
- "Fix now" - spawn fix subagent
|
|
- "Plan fix" - suggest /gsd:plan-phase --gaps
|
|
- "Manual fix" - done
|
|
|
|
**If `## CHECKPOINT REACHED`:**
|
|
- Present checkpoint details to user
|
|
- Get user response
|
|
- Spawn continuation agent (see step 5)
|
|
|
|
**If `## INVESTIGATION INCONCLUSIVE`:**
|
|
- Show what was checked and eliminated
|
|
- Offer options:
|
|
- "Continue investigating" - spawn new agent with additional context
|
|
- "Manual investigation" - done
|
|
- "Add more context" - gather more symptoms, spawn again
|
|
|
|
## 5. Spawn Continuation Agent (After Checkpoint)
|
|
|
|
When user responds to checkpoint, spawn fresh agent:
|
|
|
|
```markdown
|
|
<objective>
|
|
Continue debugging {slug}. Evidence is in the debug file.
|
|
</objective>
|
|
|
|
<prior_state>
|
|
Debug file: @.planning/debug/{slug}.md
|
|
</prior_state>
|
|
|
|
<checkpoint_response>
|
|
**Type:** {checkpoint_type}
|
|
**Response:** {user_response}
|
|
</checkpoint_response>
|
|
|
|
<mode>
|
|
goal: find_and_fix
|
|
</mode>
|
|
```
|
|
|
|
```
|
|
Task(
|
|
prompt=continuation_prompt,
|
|
subagent_type="gsd-debugger",
|
|
model="{debugger_model}",
|
|
description="Continue debug {slug}"
|
|
)
|
|
```
|
|
|
|
</process>
|
|
|
|
<success_criteria>
|
|
- [ ] Active sessions checked
|
|
- [ ] Symptoms gathered (if new)
|
|
- [ ] gsd-debugger spawned with context
|
|
- [ ] Checkpoints handled correctly
|
|
- [ ] Root cause confirmed before fixing
|
|
</success_criteria>
|