Continuity Context

Goal

One file + one habit so the next session (human or agent) starts in <30 seconds — without syncing Jira, Notion, and the IDE separately.

Artifacts

CONTEXT.md (repo root)

Keep ≤40 lines. Session-end update takes <30 seconds.

# Context

**Active goal:** One line — what "done" looks like this week.

**Active work:** WI/ticket name or branch (link if exists).

**Open decisions (max 3):**
- [ ] Decision — options A/B

**Touched today:** (paths, newest first, max 8)
- src/...

**Next action:** One imperative verb — "Ship X-3 IPC tests" / "Fix Track drag".

**Last session note:** One sentence — where you stopped.

Rotate Touched today — drop paths older than 3 days unless still hot.

If CONTEXT.md contradicts git/branch state, trust git and fix CONTEXT in the same edit.

User rule snippet (optional)

Offer this for Cursor Rules (≤10 lines):

At task start: read CONTEXT.md if present; restate Active goal + Next action in one line.
At meaningful checkpoints (task done, PR opened, context switch): batch-append changed paths to Touched today (max 8).
Before ending a session: update Last session note + Next action only.
Do not ask the user to maintain a separate PRD unless they request it.

Workflow

1. If CONTEXT.md missing and project has >1 day of work → create from git log + open files.
2. At session start → read it; don't re-scan whole repo unless user asks.
3. At session end → update Last session note + Next action only (minimal diff).
4. At checkpoints (task complete, PR ready, deliberate pause) → batch-update Touched today; do not append on every edit or keystroke.
5. Do not duplicate full architecture in CONTEXT — link the blueprint layer:
   • Continuum: .continuum/blueprint/ or BlueprintPanel (not ARCHITECTURE.md)
   • Other repos: ARCHITECTURE.md if the architecture-blueprint skill exists

Constraints

• Not a replacement for tickets/docs — it's the pointer layer
• No automated append on every keystroke — batch at meaningful checkpoints only
• No MCP catalog, Slack sync, or multi-tool dashboards
• If Continuum project open: checkpoint mental notes may live in graph — CONTEXT.md is for cross-IDE portability only

Adversarial self-check

• New teammate could orient from CONTEXT.md alone in 30s?
• File still ≤40 lines?
• Next action is one verb, not a paragraph?
• Session-end edit touched only Last session note + Next action (not a full rewrite)?
• Avoided duplicating blueprint/architecture content?