From easy-cheese
Creates a durable handoff document from the current conversation so a fresh agent can resume work without context loss. Writes a resumable slug to `.cheese/notes/<slug>.md` with state, suggested skills, and redacted secrets.
How this skill is triggered — by the user, by Claude, or both
Slash command
/easy-cheese:wheypointThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A wheypoint is a waypoint on the cheese's journey: a marked spot you can navigate back to. Use this skill when the conversation holds work-in-progress that a different agent (or a future you, in a fresh context) needs to continue. `/wheypoint` captures just enough state for a cold reader to resume, and nothing they could already read elsewhere.
A wheypoint is a waypoint on the cheese's journey: a marked spot you can navigate back to. Use this skill when the conversation holds work-in-progress that a different agent (or a future you, in a fresh context) needs to continue. /wheypoint captures just enough state for a cold reader to resume, and nothing they could already read elsewhere.
Do not use it for no-write design dialogue (/culture) or as a substitute for a phase skill's own handoff slug. /cook, /press, /age, and /cure write their slugs at clean phase boundaries; /wheypoint is for the messy mid-task moment when none of those apply and context is about to be lost.
auth-retry-backoff). Reuse an existing slug if this session already owns one under .cheese/..cheese/ artifacts, specs, PRs, issues, commits, and diffs this session produced or touched. These get referenced, never re-summarised..cheese/notes/<slug>.md with the slug header (## Handoff slug) and body (## Document) below.## Redaction)./cheese --continue <slug> from the original repo, and include an absolute clickable path to the handoff note so the user can find it from any working directory.Prepend the standard resumable slug to the top of the file so /cheese --continue can route from it without reading the whole document:
status: ok | halt: <one-line reason>
next: mold | cook | press | age | cure | affinage | done
artifact: <path-to-richer-report, or PR ref (PR#<n> / URL) when next: affinage, else none>
<one-line orientation: where the session is and what is mid-flight>
next: names the skill the cold reader should run, which is the machine-readable form of the suggested-skills section below. Use done only when the work is genuinely finished and the handoff is a record, not a baton. /cheese --continue <slug> scans .cheese/notes/<slug>.md and dispatches next: directly; /cheese --continue <absolute-note-path> reads that handoff file directly when the user is outside the original repo. When next: affinage, record the PR reference (PR#<n> or its URL) in artifact: so the resume dispatches /affinage <pr> explicitly rather than relying on branch auto-detection.
After the slug, write a ## Document section. Open with the answer; keep every claim readable to someone who has not seen the conversation. Cover, in order, only the parts that carry signal:
`<certain>` / `<speculating>` / `<don't know>`) and a one-line why.## Do not duplicate.## Suggested skills for the state-to-skill mapping.Follow the house style in ../../shared/formatting.md: no em-dashes, complete sentences in prose, no throat-clearing, calibrated tags on the claim.
Pick the next move from where the session actually is, name it as an easy-cheese skill with its argument, and write the same target into the slug's next: field. Suggest the single best next step, plus the step after it when the path is obvious. The map:
| Where the session is | Suggest | next: |
|---|---|---|
| Fuzzy idea, no approved spec yet | /mold | mold |
| Approved spec, not yet implemented | /cook <spec-path> | cook |
| Code written, not yet hardened or reviewed | /press <slug> then /age | press |
| Implementation done, review wanted now | /age <ref> | age |
| Review findings in hand, fixes not applied | /cure <slug> | cure |
| PR has review comments or failing CI | /affinage <pr> | affinage |
| Hard bug still un-diagnosed | /pasteurize <input> | cook |
| Work genuinely finished | record only, no baton | done |
When the session sits mid-phase (e.g. /cook was interrupted), suggest re-entering that same phase with the slug. Tailor to the optional focus argument when the user gave one: it overrides the table if the next session is meant to do something other than advance the pipeline.
The point of a handoff is to be short enough to read cold. Anything already captured in a durable artifact gets a reference, not a copy:
.cheese/ — link by path.Summarise an artifact only when the summary is genuinely shorter than its pointer. Re-pasting a diff or a spec into the handoff is the failure mode this skill exists to avoid.
Strip anything sensitive before writing: API keys, tokens, passwords, connection strings, and personally identifiable information. If a secret is required for the next session, reference where it lives (env var name, secret manager path), never its value.
The handoff document is the only thing /wheypoint writes. No commits, no PRs, no production-code edits. End by surfacing the slug's orientation line, a normal Markdown link to the note, and repo-root-aware resumption commands. Keep the note link outside fenced code so it is clickable. The link line should match this shape: Wheypoint dropped: [.cheese/notes/<slug>.md](<absolute-note-path>).
Resume from original repo:
cd <absolute-repo-path>
/cheese --continue <slug>
Resume from anywhere:
/cheese --continue <absolute-repo-path>/.cheese/notes/<slug>.md
npx claudepluginhub paulnsorensen/easy-cheeseCompacts the current conversation into a self-contained handoff document so a fresh agent or developer can resume work by reading only that file. Use when pausing work or summarizing long sessions.
Creates structured session handoff documents that capture working state for continuation or context rehydration. Useful before clearing context or ending a session.
Captures full session context into a handoff document so a fresh agent can resume work with zero prior context. Write a single actionable sentence for the next agent.