Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Sequence work into verifiable units
Order work as a sequence of small units, each ending in a state you can check, and don't advance until the current one is green. The same discipline runs at two altitudes, how you execute and how you deliver.
**Why:** A break caught at the unit that caused it is cheap to localize. A break caught after a batch is buried, and you have already built further on a broken base. Sequencing those same units into a delivery a reviewer can replay turns "trust me" into "watch it go red, then green."
**Execution.** In a sweep, migration, or any run of similar edits, verify each change before starting the next. Never batch the edits and verify once at the end. Each unit is a before/after bracket: known-good state, one change, run the check, then proceed. Rebase onto clean trunk first so every check measures against the real baseline. When a lever does the edits, the per-unit check is nearly free; run it anyway.
…
The line at the top of this page pins the label git:20260827.04830a9, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_v5w4lyzhgbhvvujx
GET https://markdownregistry.com/api/v1/resolve?ref=painhardcore/pstack/principle-sequence-verifiable-units
GET https://markdownregistry.com/api/v1/blob/40de5b6d82a408423fffcc9553c73aaf278bd6a1ba24659a4e56174726374bcb
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
painhardcore/pstack · .opencode/skills/architect/SKILL.md · Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use…
painhardcore/pstack · .opencode/skills/arena/SKILL.md · Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for…
painhardcore/pstack · .opencode/skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe…
painhardcore/pstack · .opencode/skills/create-verification-skill/SKILL.md · Generate a project-local verification skill that drives your app the way a user does — any language, framework, or…
painhardcore/pstack · .opencode/skills/figure-it-out/SKILL.md · Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a…
painhardcore/pstack · .opencode/skills/how/SKILL.md · Explain how a subsystem works, trace a runtime flow, or determine where code and ownership belong before making a…
painhardcore/pstack · .opencode/skills/interrogate/SKILL.md · Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find…
painhardcore/pstack · .opencode/skills/principle-boundary-discipline/SKILL.md · Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI…
cursor/plugins · harness/pstack/claude-code/skills/principle-sequence-verifiable-units/SKILL.md · Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work…
cursor/plugins · pstack/skills/principle-sequence-verifiable-units/SKILL.md · Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work…
michael-denyer/pstack-claude · plugins/pstack/skills/principle-sequence-verifiable-units/SKILL.md · Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work…
backnotprop/pstack · skills/principle-sequence-verifiable-units/SKILL.md · Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work…
j-star-films-studios/vibecode-protocol-suite · assets/.agent/skills/engineering-principles/sequence-verifiable-units/SKILL.md · Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work…
creedants/pstack-t3 · skills/principle-sequence-verifiable-units/SKILL.md · Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work…
arjitj2/open-pstack · plugins/pstack/skills/principle-sequence-verifiable-units/SKILL.md · Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work…
edbertchan/catstack · corpus/skills/principle-sequence-verifiable-units/SKILL.md · Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work…
