agentleFS
hidenobunagaihidenobunagai/astack/skills/principle-sequence-verifiable-units/SKILL.md

principle-sequence-verifiable-units

Skill1 starsChanged 12 days agoMITView on GitHub

Apply to multi-step analysis work: backfills, notebook-to-pipeline conversions, migrations of many similar queries, and how commits and PRs are stacked. Break work into small units that each end in a checkable state, verify each before the next, and order delivery so a reviewer can follow it.

47 other projects use a version of this, 44 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-pstack, poteto-help and 4 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.
  • bnemaSkill

    setup-pstack

    Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.

    Also in 25 projects that use this

  • ianclearySkill

    poteto-help

    Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

    Also in 14 projects that use this

  • eryzerzSkill

    make-bot-ui

    Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

    Also in 19 projects that use this

  • tristanphvnSkill

    ketchup-video

    Catch the user up like /keel:ketchup, with a short silent video of slides for what happened and the waiting calls as text under it. Use for /keel:ketchup-video.

    Also in 11 projects that use this

  • JoshueOsunaSkill

    Poteto Mode

    poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

    Also in 3 projects that use this

  • instructureSkill

    ketchup

    Rebuild context after /clear by analyzing uncommitted changes across Canvas LMS and all plugin repositories

    Also in 18 projects that use this

The file

Files
SKILL.md

Sequence Work into Verifiable Units

Order work as a sequence of small units. Each unit ends in a state you can check. Do not advance until the current unit is green.

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. The same units, delivered in order, let a reviewer replay the work: watch it fail, then watch it pass.

In a backfill, migration, or run of similar edits, verify each change before starting the next. Each unit is a before-and-after bracket: a known-good state, one change, the check, then proceed. Start from a clean, re-run baseline so every check measures against the real starting point. When a script makes the edits, the per-unit check is nearly free. Run it anyway.

For delivery, stack commits and PRs in the order that proves the work. Each unit is its own commit on top of the last. The canonical shape is the failing data-quality assertion first, then the fix on top. Other story orders are a removal before the reshape, a baseline capture before the treatment, and the scaffold before the feature. Each change lands on its own, and the sequence reads as an argument.

This is the sequencing companion to principle-prove-it-works, which keeps each check real, and to principle-build-the-lever, which makes the per-unit check cheap.

Download now (ZIP)

Does it work?

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

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.