← ClaudeAtlas

principle-sequence-verifiable-unitslisted

Break migrations, sweeps, multi-step changes, commits, and pull requests into small units that each end in a known, verifiable state before the next begins.
3metaJun/mstack · ★ 0 · Code & Development · score 73
Install: claude install-skill 3metaJun/mstack
# Sequence work into verifiable units Order work so each unit ends in a check and no later unit builds on an unknown state. For execution: 1. Start from a known baseline. 2. Choose the smallest change that produces a meaningful check. 3. Make that one change. 4. Run the check and stop on failure. 5. Continue only after the unit is green. For delivery, arrange commits or pull requests so a reviewer can replay the argument. Useful sequences include failing test then fix, baseline capture then treatment, schema then consumer, or scaffold then feature. Each unit should be coherent on its own and make the next unit easier to verify. Do not batch repeated edits and defer validation to the end. When a generator or codemod makes the per-unit check cheap, still run the check after each unit. Use `principle-prove-it-works` to keep checks direct and `principle-build-the-lever` to make them rerunnable.