d4767ac2e0
* fix: replace /gsd: command format with /gsd- skill format in all suggestions All next-step suggestions shown to users were still using the old colon format (/gsd:xxx) which cannot be copy-pasted as skills. Migrated all occurrences across agents/, commands/, get-shit-done/, docs/, README files, bin/install.js (hardcoded defaults for claude runtime), and get-shit-done/bin/lib/*.cjs (generate-claude-md templates and error messages). Updated tests to assert new hyphen format instead of old colon format. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: migrate remaining /gsd: format to /gsd- in hooks, workflows, and sdk Addresses remaining user-facing occurrences missed in the initial migration: - hooks/: fix 4 user-facing messages (pause-work, update, fast, quick) and 2 comments in gsd-workflow-guard.js - get-shit-done/workflows/: fix 21 Skill() literal calls that Claude executes directly (installer does not transform workflow content) - sdk/prompt-sanitizer.ts: update regex to strip /gsd- format in addition to legacy /gsd: format; update JSDoc comment - tests/: update autonomous-ui-steps, prompt-sanitizer to assert new format Note: commands/gsd/*.md frontmatter (name: gsd:xxx) intentionally unchanged — installer derives skillName from directory path, not the name field. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix(plan-phase): preserve --chain flag in auto-advance sync and handle ui-phase gate in chain mode Bug 1: step 15 sync-flag check only guarded against --auto, causing _auto_chain_active to be cleared when plan-phase is invoked without --auto in ARGUMENTS even though a --chain pipeline was active. Added --chain to the guard condition, matching discuss-phase behaviour. Bug 2: UI Design Contract gate (step 5.6) always exited the workflow when UI-SPEC was missing, breaking the discuss --chain pipeline silently. When _auto_chain_active is true, the gate now auto-invokes gsd-ui-phase --auto via Skill() and continues to step 6 without prompting. Manual invocations retain the existing AskUserQuestion flow. * fix: remove <sub>/clear</sub> pattern and duplicate old-format command in discuss-phase.md --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
92 lines
1.8 KiB
Markdown
92 lines
1.8 KiB
Markdown
# Debug Subagent Prompt Template
|
|
|
|
Template for spawning gsd-debugger agent. The agent contains all debugging expertise - this template provides problem context only.
|
|
|
|
---
|
|
|
|
## Template
|
|
|
|
```markdown
|
|
<objective>
|
|
Investigate issue: {issue_id}
|
|
|
|
**Summary:** {issue_summary}
|
|
</objective>
|
|
|
|
<symptoms>
|
|
expected: {expected}
|
|
actual: {actual}
|
|
errors: {errors}
|
|
reproduction: {reproduction}
|
|
timeline: {timeline}
|
|
</symptoms>
|
|
|
|
<mode>
|
|
symptoms_prefilled: {true_or_false}
|
|
goal: {find_root_cause_only | find_and_fix}
|
|
</mode>
|
|
|
|
<debug_file>
|
|
Create: .planning/debug/{slug}.md
|
|
</debug_file>
|
|
```
|
|
|
|
---
|
|
|
|
## Placeholders
|
|
|
|
| Placeholder | Source | Example |
|
|
|-------------|--------|---------|
|
|
| `{issue_id}` | Orchestrator-assigned | `auth-screen-dark` |
|
|
| `{issue_summary}` | User description | `Auth screen is too dark` |
|
|
| `{expected}` | From symptoms | `See logo clearly` |
|
|
| `{actual}` | From symptoms | `Screen is dark` |
|
|
| `{errors}` | From symptoms | `None in console` |
|
|
| `{reproduction}` | From symptoms | `Open /auth page` |
|
|
| `{timeline}` | From symptoms | `After recent deploy` |
|
|
| `{goal}` | Orchestrator sets | `find_and_fix` |
|
|
| `{slug}` | Generated | `auth-screen-dark` |
|
|
|
|
---
|
|
|
|
## Usage
|
|
|
|
**From /gsd-debug:**
|
|
```python
|
|
Task(
|
|
prompt=filled_template,
|
|
subagent_type="gsd-debugger",
|
|
description="Debug {slug}"
|
|
)
|
|
```
|
|
|
|
**From diagnose-issues (UAT):**
|
|
```python
|
|
Task(prompt=template, subagent_type="gsd-debugger", description="Debug UAT-001")
|
|
```
|
|
|
|
---
|
|
|
|
## Continuation
|
|
|
|
For checkpoints, spawn fresh agent with:
|
|
|
|
```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: {goal}
|
|
</mode>
|
|
```
|