/wheypoint

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.

Inputs

• The conversation so far. That is the primary input.
• Optional argument: a description of what the next session will focus on. When present, treat it as the lens and tailor the document to it. Drop state that does not serve that focus to a one-line pointer.

Flow

1. Derive a slug from the task (e.g. auth-retry-backoff). Reuse an existing slug if this session already owns one under .cheese/.
2. Inventory what already exists. List the .cheese/ artifacts, specs, PRs, issues, commits, and diffs this session produced or touched. These get referenced, never re-summarised.
3. Write the handoff document to .cheese/notes/<slug>.md with the slug header (## Handoff slug) and body (## Document) below.
4. Redact secrets on the way out (## Redaction).
5. Point at resumption. End by telling the user how to resume with /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.