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>
118 lines
2.6 KiB
Markdown
118 lines
2.6 KiB
Markdown
# Planner Subagent Prompt Template
|
|
|
|
Template for spawning gsd-planner agent. The agent contains all planning expertise - this template provides planning context only.
|
|
|
|
---
|
|
|
|
## Template
|
|
|
|
```markdown
|
|
<planning_context>
|
|
|
|
**Phase:** {phase_number}
|
|
**Mode:** {standard | gap_closure}
|
|
|
|
**Project State:**
|
|
@.planning/STATE.md
|
|
|
|
**Roadmap:**
|
|
@.planning/ROADMAP.md
|
|
|
|
**Requirements (if exists):**
|
|
@.planning/REQUIREMENTS.md
|
|
|
|
**Phase Context (if exists):**
|
|
@.planning/phases/{phase_dir}/{phase_num}-CONTEXT.md
|
|
|
|
**Research (if exists):**
|
|
@.planning/phases/{phase_dir}/{phase_num}-RESEARCH.md
|
|
|
|
**Gap Closure (if --gaps mode):**
|
|
@.planning/phases/{phase_dir}/{phase_num}-VERIFICATION.md
|
|
@.planning/phases/{phase_dir}/{phase_num}-UAT.md
|
|
|
|
</planning_context>
|
|
|
|
<downstream_consumer>
|
|
Output consumed by /gsd-execute-phase
|
|
Plans must be executable prompts with:
|
|
- Frontmatter (wave, depends_on, files_modified, autonomous)
|
|
- Tasks in XML format
|
|
- Verification criteria
|
|
- must_haves for goal-backward verification
|
|
</downstream_consumer>
|
|
|
|
<quality_gate>
|
|
Before returning PLANNING COMPLETE:
|
|
- [ ] PLAN.md files created in phase directory
|
|
- [ ] Each plan has valid frontmatter
|
|
- [ ] Tasks are specific and actionable
|
|
- [ ] Dependencies correctly identified
|
|
- [ ] Waves assigned for parallel execution
|
|
- [ ] must_haves derived from phase goal
|
|
</quality_gate>
|
|
```
|
|
|
|
---
|
|
|
|
## Placeholders
|
|
|
|
| Placeholder | Source | Example |
|
|
|-------------|--------|---------|
|
|
| `{phase_number}` | From roadmap/arguments | `5` or `2.1` |
|
|
| `{phase_dir}` | Phase directory name | `05-user-profiles` |
|
|
| `{phase}` | Phase prefix | `05` |
|
|
| `{standard \| gap_closure}` | Mode flag | `standard` |
|
|
|
|
---
|
|
|
|
## Usage
|
|
|
|
**From /gsd-plan-phase (standard mode):**
|
|
```python
|
|
Task(
|
|
prompt=filled_template,
|
|
subagent_type="gsd-planner",
|
|
description="Plan Phase {phase}"
|
|
)
|
|
```
|
|
|
|
**From /gsd-plan-phase --gaps (gap closure mode):**
|
|
```python
|
|
Task(
|
|
prompt=filled_template, # with mode: gap_closure
|
|
subagent_type="gsd-planner",
|
|
description="Plan gaps for Phase {phase}"
|
|
)
|
|
```
|
|
|
|
---
|
|
|
|
## Continuation
|
|
|
|
For checkpoints, spawn fresh agent with:
|
|
|
|
```markdown
|
|
<objective>
|
|
Continue planning for Phase {phase_number}: {phase_name}
|
|
</objective>
|
|
|
|
<prior_state>
|
|
Phase directory: @.planning/phases/{phase_dir}/
|
|
Existing plans: @.planning/phases/{phase_dir}/*-PLAN.md
|
|
</prior_state>
|
|
|
|
<checkpoint_response>
|
|
**Type:** {checkpoint_type}
|
|
**Response:** {user_response}
|
|
</checkpoint_response>
|
|
|
|
<mode>
|
|
Continue: {standard | gap_closure}
|
|
</mode>
|
|
```
|
|
|
|
---
|
|
|
|
**Note:** Planning methodology, task breakdown, dependency analysis, wave assignment, TDD detection, and goal-backward derivation are baked into the gsd-planner agent. This template only passes context.
|