get-shit-done/references/continuation-format.md
Standard format for presenting next steps after completing a command or workflow.
---
## ▶ Next Up — [${PROJECT_CODE}] ${PROJECT_TITLE}
**{identifier}: {name}** — {one-line description}
`/clear` then:
`{command to copy-paste}`
---
**Also available:**
- `{alternative option 1}` — description
- `{alternative option 2}` — description
---
If
project_codeis not set in the init context, omit the project identity suffix:## ▶ Next Up(no— [CODE] Title).
<objective> for plans/clear first — always show /clear before the command so users run it in the correct order--- above and below to make it stand out[PROJECT_CODE] PROJECT_TITLE from init context so handoffs are self-identifying across sessions. If project_code is not set, omit the suffix entirely (just ## ▶ Next Up)---
## ▶ Next Up — [${PROJECT_CODE}] ${PROJECT_TITLE}
**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
---
Add note that this is the last plan and what comes after:
---
## ▶ Next Up — [${PROJECT_CODE}] ${PROJECT_TITLE}
**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
---
---
## ▶ Next Up — [${PROJECT_CODE}] ${PROJECT_TITLE}
**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-plan-phase --research-phase 2` — investigate unknowns
- Review roadmap
---
Show completion status before next action:
---
## ✓ Phase 2 Complete
3/3 plans executed
## ▶ Next Up — [${PROJECT_CODE}] ${PROJECT_TITLE}
**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-plan-phase --research-phase 3` — investigate unknowns
- Review what Phase 2 built
---
When there's no clear primary action:
---
## ▶ Next Up — [${PROJECT_CODE}] ${PROJECT_TITLE}
**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-plan-phase --research-phase 3`
---
---
## 🎉 Milestone v1.0 Complete
All 4 phases shipped
## ▶ Next Up — [${PROJECT_CODE}] ${PROJECT_TITLE}
**Start v1.1** — questioning → research → requirements → roadmap
`/clear` then:
`/gsd-new-milestone`
---
### Phase 2: Authentication
**Goal**: JWT login flow with refresh tokens
Extract: **Phase 2: Authentication** — JWT login flow with refresh tokens
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
## To Continue
Run `/clear`, then paste:
/gsd-execute-phase 2
User has no idea what 02-03 is about.
`/gsd-plan-phase 3`
Run /clear first.
Doesn't explain why. User might skip it.
Other options:
- Review roadmap
Sounds like an afterthought. Use "Also available:" instead.
/gsd-plan-phase 3
Fenced blocks inside templates create nesting ambiguity. Use inline backticks instead.