principle-sequence-verifiable-units

Sequences multi-step work into small units verified before advancing.

Updated Jul 29, 2026

Search Tags:#testing #code review #verification #migration #incremental delivery #commit stacking

One-click install

npx skills add https://github.com/mmdmcy/fluttAIrbar --skill principle-sequence-verifiable-units-mmdmcy

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: principle-sequence-verifiable-units
Source: https://github.com/mmdmcy/fluttAIrbar/tree/main/plugins/pstack/skills/principle-sequence-verifiable-units
Command: npx skills add https://github.com/mmdmcy/fluttAIrbar --skill principle-sequence-verifiable-units-mmdmcy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large batches of edits verified only at the end bury failures, making bugs expensive to localize and forcing rework on top of a broken base. This Skill enforces a discipline where every unit of work ends in a checkable state before the next begins. ## Core Features & Use Cases - Per-Unit Verification: Run a check after each edit in a sweep or migration instead of batching verification at the end. - Delivery Sequencing: Order commits and PRs so the stack proves itself, such as a failing test first followed by the fix. - Use Case: During a codebase-wide migration, apply one change, run its test to confirm green, then proceed, and stack the commits so a reviewer can replay the red-to-green story. ## Quick Start Use the principle-sequence-verifiable-units skill to break this migration into small verifiable units and order the commits so each one stands alone.

Frequently Asked Questions about principle-sequence-verifiable-units

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I break a large migration into verifiable steps?▼

Pick the smallest unit that ends in a check, such as one edit plus its test. Verify that unit before starting the next, rebasing onto clean trunk first so each check measures against the real baseline.

How should I order commits and PRs for review?▼

Order the stack so it proves the work: a failing test first to show the bug is real, then the fix on top to show it resolved. Each commit should land on its own so the sequence reads as an argument.

Why verify each edit instead of testing at the end?▼

A break caught at the unit that caused it is cheap to localize, while a break caught after a batch is buried under later changes. Per-unit checks keep the base known-good throughout the run.

When is batch verification acceptable instead of per-unit checks?▼

This discipline argues it rarely is, even when automation makes edits cheap. The per-unit check is nearly free when a lever does the edits, so deferring verification to a final batch only adds risk without saving effort.