checkpointlisted

# /checkpoint — token/context hygiene (PROGRESS.md) This skill captures the **current state of work** into `PROGRESS.md` before the context is discarded (`/clear`) or compressed (`/compact`). The goal: **nothing is lost across the context boundary** — `PROGRESS.md` is the thread-carrier that hands the thread to the next session. The skill is **generic** — work with what you actually find in the repo, and assume nothing about the specific project. ## The control documents — keep them separate **Anti-duplication:** status → `PROGRESS.md` · rules → `CLAUDE.md` · why-it-exists → `BUSINESS.md` · why-we-chose-X-over-Y → `DECISIONS.md` · under-what-rules → `COMPLIANCE.md`. Write each fact in exactly one place. (full table: GUIDE PART 1) > Not every project has all five docs. This skill only maintains `PROGRESS.md`; treat the > others as sources of context if they exist. If you catch yourself writing a rule (language > version, commit style) or a business justification (who it is for, what pain it solves) > into `PROGRESS.md` — it belongs elsewhere, leave it out. A **durable "why we chose X over > Y"** is a `DECISIONS.md` entry, **not** a Notes bullet. ## What PROGRESS.md holds A short **thread-carrier**, not a diary. If the project's thread-carrier is **not** `PROGRESS.md` — the SessionStart declaration hook honours `ATTEST_THREAD_CARRIER`, and `CLAUDE.md` may name one (e.g. `TIMESHEET.md`) — maintain **that** file instead: same sections, same brevity. Keep these sections (if