multilingual-absa / .opencode /gsd-core /references /continuation-format.md
Aryan Mishra
feat: initial commit - Multilingual ABSA project setup with 6 phases, 36 requirements
a6b96c2
|
Raw
History Blame Contribute Delete
4.78 kB

A newer version of the Gradio SDK is available: 6.26.0

Upgrade

Continuation Format

Standard format for presenting next steps after completing a command or workflow.

Core Structure

---

## β–Ά 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_code is not set in the init context, omit the project identity suffix: ## β–Ά Next Up (no β€” [CODE] Title).

Format Rules

  1. Always show what it is β€” name + description, never just a command path
  2. Pull context from source β€” ROADMAP.md for phases, PLAN.md <objective> for plans
  3. Command in inline code β€” backticks, easy to copy-paste, renders as clickable link
  4. /clear first β€” always show /clear before the command so users run it in the correct order
  5. "Also available" not "Other options" β€” sounds more app-like
  6. Visual separators β€” --- above and below to make it stand out
  7. Project identity in heading β€” include [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)

Variants

Execute Next Plan

---

## β–Ά 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-discuss-phase 2 --assumptions` β€” check assumptions

---

Execute Final Plan in Phase

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

---

Plan a Phase

---

## β–Ά 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

---

Phase Complete, Ready for Next

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

---

Multiple Equal Options

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 Complete

---

## πŸŽ‰ 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`

---

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.