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

fix: auto-diagnose issues instead of offering choice

Browse Source 
Diagnosis always produces better fixes and runs in parallel anyway.
Removing the prompt reduces cognitive load.

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Lex Christopherson
2026-01-14 10:19:22 -06:00
parent be9ff0c365
commit 1f358c55b8
1 changed files with 9 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files

39
get-shit-done/workflows/verify-work.md
View File

@@ -294,7 +294,7 @@ Present summary:
[List from Issues section]
```
**If issues > 0:** Proceed to `offer_diagnosis`
**If issues > 0:** Proceed to `diagnose_issues`
**If issues == 0:**
```
@@ -305,45 +305,34 @@ All tests passed. Ready to continue.
```
</step>
<step name="offer_diagnosis">
**Offer to diagnose root causes before planning fixes:**
<step name="diagnose_issues">
**Diagnose root causes before planning fixes:**
```
---
{N} issues found. Before planning fixes, diagnose root causes?
{N} issues found. Diagnosing root causes...
Diagnosis spawns parallel debug agents to investigate each issue.
Each agent finds the root cause, making fix planning more accurate.
Diagnose now? (yes/no)
Spawning parallel debug agents to investigate each issue.
```
Wait for user response.
**If yes/y/diagnose:**
- Load diagnose-issues workflow
- Follow @~/.claude/get-shit-done/workflows/diagnose-issues.md
- Spawn parallel debug agents for each issue
- Collect root causes
- Update UAT.md with root causes
- Return to `offer_plan_fix`
- Proceed to `offer_plan_fix`
**If no/skip/later:**
- Proceed to `offer_plan_fix` without diagnosis
- Plan-fix will work without root causes (less precise but still functional)
Diagnosis runs automatically - no user prompt. Parallel agents investigate simultaneously, so overhead is minimal and fixes are more accurate.
</step>
<step name="offer_plan_fix">
**Offer next steps after testing (and optional diagnosis):**
**Offer next steps after diagnosis:**
Check if UAT.md has root causes (status: "diagnosed" or root_cause fields populated).
**If diagnosed:**
```
---
Root causes identified. Ready to plan fixes.
## Diagnosis Complete
| Issue | Root Cause |
|-------|------------|
@@ -355,16 +344,6 @@ Next steps:
- `/gsd:plan-fix {phase}` — Create fix plan with root causes
- `/gsd:verify-work {phase}` — Re-test after fixes
```
**If not diagnosed:**
```
---
Next steps:
- `/gsd:plan-fix {phase}` — Create fix plan for issues
- `/gsd:verify-work {phase}` — Re-test after fixes
- Continue to next phase (issues logged for later)
```
</step>
</process>