session
/session
Cross-session continuity and backlog/process rules — how project state, outstanding work, and documentation survive between sessions. Covers the session handoff, PROGRESS.json as the single backlog source, the GitHub Issues/Projects mirror, documentation maintenance, and the next-phase prompt. Use at the start and end of every session, and whenever tracking or handing off work.
- Author
- autocss-com ↗
- Repository
- ai ↗
- Licence
- MIT
- Last repository change
- 04.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 4
No signals detected. Repository changed on 04.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Cross-session continuity and backlog/process rules — how project state, outstanding work, and documentation survive between sessions. Covers the session handoff, PROGRESS.json as the single backlog source, the GitHub Issues/Projects mirror, documentation maintenance, and the next-phase prompt. Use at the start and end of every session, and whenever tracking or handing off work.
Original author description
Cross-session continuity and backlog/process rules — how project state, outstanding work, and documentation survive between sessions. Covers the session handoff, PROGRESS.json as the single backlog source, the GitHub Issues/Projects mirror, documentation maintenance, and the next-phase prompt. Use at the start and end of every session, and whenever tracking or handing off work.
How it works
- Start of every session
- Single source of truth for outstanding work
- The GitHub mirror is one-way
- End of every session (the ritual)
- Documentation maintenance (periodic, cost-driven)
- Standards consultation
- What session-handling never does
- Baseline & support
- Reference
SKILL.md preview
---
name: session
description: Cross-session continuity and backlog/process rules — how project state, outstanding work, and documentation survive between sessions. Covers the session handoff, PROGRESS.json as the single backlog source, the GitHub Issues/Projects mirror, documentation maintenance, and the next-phase prompt. Use at the start and end of every session, and whenever tracking or handing off work.
license: MIT
metadata:
version: "1.0.0"
---
# Session
Work spans many sessions and many AI vendors. Continuity is a discipline, not an accident. State lives in files, not in memory; the backlog has one source of truth; the mirror is one-way.
## Start of every session
1. Read `.agents/SESSION-HANDOFF.md` **before making any implementation decision**.
2. Re-assert the handoff's **Constraint Lock** before coding.
3. If the handoff conflicts with a skill, the `architecture` skill, or the canonical laws, **stop and ask** — never resolve silently (conflict priority: `Autocss-com/ai` AGENTS.md > repo AGENTS.md > `SESSION-HANDOFF.md`).
Skipping handoff review "to save time" is prohibited — it is the single largest cause of lost context and repeated mistakes.
## Single source of truth for outstanding work
`PROGRESS.json` (its `meta.future_goals` + `cursor.open_q`) is the **one** authoritative list of outstanding work. Keep structured state as data in `PROGRESS.json`; keep principles/rationale as concise prose in the skills/docs (JSON usually costs more tokens for prose).
Nothing competes with `PROGRESS.json`. Chat memory, scratch notes, and the issue tracker are all downstream of it.
## The GitHub mirror is one-way
GitHub **Issues** + the **Projects board** are a human-visible **mirror** of the backlog, never a competing tracker:
- Open an Issue for each new backlog / open-question item; **close** it when done.
- Title mirrors the item; body carries detail + a pointer to the `PROGRESS.json` / prompt entry; apply the `backlog` label.
- **Board columns are label-driven and status labels are mutually exclusive — never stack them.** Backlog column = `backlog` label only; In Progress = `in-progress` only (you must remove `backlog` when moving to In Progress); Done = the Issue **closed** (no status label). To move a card, **swap** the status label, never add a second. Grouping tags (e.g. `demo`) are orthogonal — keep them.
- Issues are effectively append-only (GitHub closes, never deletes) — create deliberately, avoid duplicates.
- If the board/toolset is unavailable in a session, **skip silently** — `PROGRESS.json` stays authoritative and the mirror catches up later.
## End of every session (the ritual)
Commit → update `PROGRESS.json` → append a session shard → update `SESSION-HANDOFF.md` → reconcile the GitHub mirror. Then write the **next-phase prompt**: a super-detailed brief for what the next session must do, holding all three contexts (immediate task, overall project intent, next-phase needs) so no context is dropped.
## Documentation maintenance (periodic, cost-driven)
Periodically optimize the docs **for AI accessibility/usability, not human reading**, to cut token cost — without dropping any detail, intention, plan, or context. Reduce redundancy; restate more concisely; prefer a short whitelist ("only X permitted; all else forbidden") over long blacklists when clearer for AI processing. Never duplicate a rule already stated — strengthen the existing wording instead (see the DRY principle).
## Standards consultation
Consult the standing references — `modern-web-guidance` and MDN Web Docs (search / doc / compat) — and periodically reconcile them against the app's current features. Their content is **advisory and subordinate**: on any conflict, the AutoCSS rules win. But the requirement to consult, to reconcile, and to *suggest* improvements is canonical. Identify ≠ apply — never silently change anything; confirm with the user first.
## What session-handling never does
- Never starts implementing before reading `SESSION-HANDOFF.md`
- Never treats chat memory or the issue tracker as the backlog source — `PROGRESS.json` is
- Never stacks `backlog` + `in-progress` labels, or invents new status labels
- Never resolves a documented-rule conflict silently — surface it to the user
- Never ends a working session without updating state + writing the next-phase prompt
## Baseline & support
_Checked against MDN as of 2026-07-16._
- No version-sensitive web-platform features are referenced here — everything used is **Baseline Widely available**.
**Canonical rules:** https://github.com/Autocss-com/ai/blob/main/AGENTS.md
## Reference
- AutoCSS Architecture + Response Integrity Charter (canonical): https://github.com/Autocss-com/ai/blob/main/AGENTS.md
- Agent Skills open standard: https://agentskills.io
- GitHub Projects (board automation): https://docs.github.com/issues/planning-and-tracking-with-projects
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · autocss-com/ai | 90 | MIT |
| glassflow/tares | 100 | MIT |
| r3dlex/oh-my-auggie | 100 | Apache-2.0 |
| lex0tan/backlog-resume | 100 | MIT |
| rdennler/yat | 100 | Apache-2.0 |
| rdennler/thinkpad | 100 | Apache-2.0 |
| maxwell2732/claudecode-research-harness-workflow | 100 | MIT |
| dotroza/hermes-comfy-recipe | 96 | MIT |
| guillaume-piron-dev/you-decide | 90 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 2e7f8c1c0885 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 84save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to… - 100backlog-sync
Run or add a one-way sync profile between two Backlog spaces with backlog-bridge sync — mirror mode (create internal mirror issues from planned customer tasks) and progress mode (push internal progress onto the customer's existing issues). Use when the user says "sync the… - 100backlog-sync
Run or add a one-way sync profile between two Backlog spaces with backlog-bridge sync — mirror mode (create internal mirror issues from planned customer tasks) and progress mode (push internal progress onto the customer's existing issues). Use when the user says "sync the… - 100github-flow
Runs a repository with GitHub Issues, Projects and Milestones through gh. Use when the user says "setup", "capture", "start #N", "ship" or "release vX.Y.Z", or asks to note an idea in the backlog, start work on an issue, open the PR for the current work, or publish a version. - 100bunqueue-working-sessions
Runs the bunqueue agent-harness session lifecycle. Use when starting, resuming or ending a bunqueue coding session, when handing off work, when ./init.sh fails, when claiming, adding or editing a work item in feature_list.json or progress.md, when asked what evidence marks an… - 90Backlog Management
This skill should be used when the user asks to 'add to backlog', 'update backlog', 'check backlog', 'list backlog items', 'prioritize backlog'. Provides conventions for managing the project backlog in .s2s/BACKLOG.md.