agentleFS
Sign inStart free
marylinmarylin/Continuum/skills/checkpoint/SKILL.md

checkpoint

Skill0 starsChanged 7 months agoMITView on GitHub

Save a cognitive snapshot — what you're doing, why, decisions made, and what's next. Use before ending a session, before /compact, when context is getting long, or anytime you want to preserve reasoning for a future session.

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 84 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No git commit (it's a working state, not a milestone)

    line 49

“Common” is measured: kept by at least 6 in 10 of the 84 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Checkpoint

Save a cognitive snapshot of current work for future sessions.

Step 1: Identify feature

Find active progress file in .lifecycle/plans/ (look for files with incomplete [ ] or [~] tasks). If no active progress file, ask: "No active plan found. What are you working on?" Use the answer as the feature name.

Step 2: Write checkpoint

Write .lifecycle/checkpoints/[feature-slug]-checkpoint.md:

# Checkpoint: [feature]
**Saved:** [ISO timestamp]
**Task:** [current task from progress file]
**Progress:** [N/M tasks complete]

## Context
[What I'm doing and why — 2-3 sentences max]

## Decisions Made
- [Decision]: [reasoning] — one line each

## What's Next
1. [Concrete next step]
2. [Step after that]

## Gotchas
- [Things the next session should watch for]

Slugify the feature name (lowercase, spaces to hyphens) for the filename. Overwrite previous checkpoint for the same feature — only the latest matters.

Step 3: Confirm

Checkpoint saved for [feature]. Resume with /resume or recover with /recover.

Rules:

  • Lightweight — should take <5 seconds and <200 tokens to invoke
  • No git commit (it's a working state, not a milestone)
  • Focus on reasoning and decisions, not file lists

$ARGUMENTS

Download now (ZIP)

  • Other versions90 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 90

    1. pedrohcgs/claude-code-my-workflow★ 1.6ksame name
    2. leonvanzyl/agentic-coding-starter-kit★ 447same name
    3. myICOR/myPKA★ 312same name
    4. hsantanna88/clo-author★ 262same name
    5. hugosantanna/clo-author★ 262same name
    6. sterlingcrispin/claude_slash_commands★ 200same name
    7. flonat/flonat-research★ 145same name
    8. josipjelic/orchestrated-project-template★ 96same name
    9. panayiotism/claude-harness★ 79same name
    10. svy04/ballast★ 73same name

    80 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use aside, spinoff and 10 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • TheKREATORSSkill

      aside

      Answer a quick side question without interrupting or losing context from the current task. Resume work automatically after answering.

      Also in 3 projects that use this

    • AhmedMerzaSkill

      spinoff

      After a branch is finished, harvest the work it made CHEAP — the helper you wrote that four other sites now hand-roll, the plumbing that turned a deferred feature small, the pattern that just split the codebase in two. Produces a follow-up backlog (0–3 candidates, feeding /issue), NEVER commits on the current branch. Invoke with /spinoff at the tail of the chain — after /fix-review has settled the review findings, before the MR merges — or when the user asks \"what else should we do while we're here / what did this unlock / anything to follow up on\". This is ship-check's optional twin — that finds what's MISSING and blocks the merge; this finds what's now CHEAP and blocks nothing. Restraint-gated: \"nothing spun off\" is the common and correct answer, and a finding that would have been equally valid before this branch is not a finding.

      Also in 3 projects that use this

    • TheKREATORSSkill

      instinct-export

      Export instincts from project/global scope to a file

      Also in 3 projects that use this

    • seek888Skill

      open-gstack-browser

      Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in. Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser". Voice triggers (speech-to-text aliases): "show me the browser".

      Also in 5 projects that use this

    • seek888Skill

      design-html

      Design finalization: generates production-quality Pretext-native HTML/CSS. Works with approved mockups from /design-shotgun, CEO plans from /plan-ceo-review, design review context from /plan-design-review, or from scratch with a user description. Text actually reflows, heights are computed, layouts are dynamic. 30KB overhead, zero deps. Smart API routing: picks the right Pretext patterns for each design type. Use when: "finalize this design", "turn this into HTML", "build me a page", "implement this design", or after any planning skill. Proactively suggest when user has approved a design or has a plan ready. (gstack) Voice triggers (speech-to-text aliases): "build the design", "code the mockup", "make it real".

      Also in 5 projects that use this

    • diego-tobalinaSkill

      build-fix

      Fix build and compilation errors systematically. Run when build fails.

      Also in 4 projects that use this

    • +2 more from TheKREATORS
    • +3 more from seek888
  • In this repository6 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free