checkpoint-plan

Installation
SKILL.md

checkpoint-plan

The user reviews and commits every logical change before more code goes on top of it. A plan made of broad phases ("Phase 1: update deps, Phase 2: fix things") fails because a phase can't be reviewed as one diff or committed as one unit. This skill turns any plan into checkpoints: small sets of related changes, put in order, each of which works on its own.

Part 1: Write the checkpointed plan

What makes a good checkpoint

  • Related. It has one purpose that fits in one commit subject line. If you need "and" to describe it, think about splitting it.
  • Green. After the checkpoint, the project builds and its lint, type checks, and tests pass. Nothing is half-wired. If a change can't be green yet, put a scaffold, shim, or feature flag in the checkpoint and say so.
  • Ordered by dependency. Foundations come first (types, schema, config, shared helpers), then the code that uses them, then UI, then cleanup. A reviewer should never need a later checkpoint to understand an earlier one.
  • Reviewable. Aim for a diff a person can read in about 10 minutes. Split big mechanical changes (renames, codemods, lockfile bumps, reformatting) into their own checkpoint so they don't hide the logic changes.
  • Tested in place. A checkpoint's tests go in that same checkpoint. Don't save all the tests for a final checkpoint.

Steps

Installs
2
First Seen
4 days ago