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>
4.0 KiB
4.0 KiB
Continuation Format
Standard format for presenting next steps after completing a command or workflow.
Core Structure
---
## ▶ Next Up
**{identifier}: {name}** — {one-line description}
`/clear` then:
`{command to copy-paste}`
---
**Also available:**
- `{alternative option 1}` — description
- `{alternative option 2}` — description
---
Format Rules
- Always show what it is — name + description, never just a command path
- Pull context from source — ROADMAP.md for phases, PLAN.md
<objective>for plans - Command in inline code — backticks, easy to copy-paste, renders as clickable link
/clearfirst — always show/clearbefore the command so users run it in the correct order- "Also available" not "Other options" — sounds more app-like
- Visual separators —
---above and below to make it stand out
Variants
Execute Next Plan
---
## ▶ Next Up
**02-03: Refresh Token Rotation** — Add /api/auth/refresh with sliding expiry
`/clear` then:
`/gsd-execute-phase 2`
---
**Also available:**
- Review plan before executing
- `/gsd-list-phase-assumptions 2` — check assumptions
---
Execute Final Plan in Phase
Add note that this is the last plan and what comes after:
---
## ▶ Next Up
**02-03: Refresh Token Rotation** — Add /api/auth/refresh with sliding expiry
<sub>Final plan in Phase 2</sub>
`/clear` then:
`/gsd-execute-phase 2`
---
**After this completes:**
- Phase 2 → Phase 3 transition
- Next: **Phase 3: Core Features** — User dashboard and settings
---
Plan a Phase
---
## ▶ Next Up
**Phase 2: Authentication** — JWT login flow with refresh tokens
`/clear` then:
`/gsd-plan-phase 2`
---
**Also available:**
- `/gsd-discuss-phase 2` — gather context first
- `/gsd-research-phase 2` — investigate unknowns
- Review roadmap
---
Phase Complete, Ready for Next
Show completion status before next action:
---
## ✓ Phase 2 Complete
3/3 plans executed
## ▶ Next Up
**Phase 3: Core Features** — User dashboard, settings, and data export
`/clear` then:
`/gsd-plan-phase 3`
---
**Also available:**
- `/gsd-discuss-phase 3` — gather context first
- `/gsd-research-phase 3` — investigate unknowns
- Review what Phase 2 built
---
Multiple Equal Options
When there's no clear primary action:
---
## ▶ Next Up
**Phase 3: Core Features** — User dashboard, settings, and data export
`/clear` then one of:
**To plan directly:** `/gsd-plan-phase 3`
**To discuss context first:** `/gsd-discuss-phase 3`
**To research unknowns:** `/gsd-research-phase 3`
---
Milestone Complete
---
## 🎉 Milestone v1.0 Complete
All 4 phases shipped
## ▶ Next Up
**Start v1.1** — questioning → research → requirements → roadmap
`/clear` then:
`/gsd-new-milestone`
---
Pulling Context
For phases (from ROADMAP.md):
### Phase 2: Authentication
**Goal**: JWT login flow with refresh tokens
Extract: **Phase 2: Authentication** — JWT login flow with refresh tokens
For plans (from ROADMAP.md):
Plans:
- [ ] 02-03: Add refresh token rotation
Or from PLAN.md <objective>:
<objective>
Add refresh token rotation with sliding expiry window.
Purpose: Extend session lifetime without compromising security.
</objective>
Extract: **02-03: Refresh Token Rotation** — Add /api/auth/refresh with sliding expiry
Anti-Patterns
Don't: Command-only (no context)
## To Continue
Run `/clear`, then paste:
/gsd-execute-phase 2
User has no idea what 02-03 is about.
Don't: Missing /clear explanation
`/gsd-plan-phase 3`
Run /clear first.
Doesn't explain why. User might skip it.
Don't: "Other options" language
Other options:
- Review roadmap
Sounds like an afterthought. Use "Also available:" instead.
Don't: Fenced code blocks for commands
/gsd-plan-phase 3
Fenced blocks inside templates create nesting ambiguity. Use inline backticks instead.