Sequencing — Development skill for Claude Code

sequencing

**A Claude Skill that fixes the order.**

Almost everything with more than three parts has an order, and almost nobody decides it. The order arrives by accident. It's the sequence the material was made in, or remembered in, or the one a template handed you.

Then the deck drags and nobody can say where. The meeting runs out of time before the decision. The page loses people at the same scroll depth every time. The talk was good and somehow didn't land.

Music and comedy solved this decades ago because the feedback is instant. A set that peaks too early dies in the room and everybody watching knows it. That produced a real craft for arranging things, and it works on anything a person moves through in time.

`sequencing` runs that craft on your deck, page, agenda, talk, curriculum, launch, or argument. Ask Claude to improve a deck and it'll polish all ten slides and never tell you that slide seven should be slide two and slide four shouldn't exist.

How it works

Two mechanisms, and everything else serves them.

**Every item needs a job.** In a set, no slot is neutral. Each one opens, builds, peaks, rests, plants, pays off, lands, or closes. Assign a job to every item you have. Whatever's left over is a cut candidate, and it's usually the reason the thing drags.

**The swap test.** For every adjacent pair, ask whether swapping them loses anything. If it doesn't, the order isn't doing work at that seam. A sequence where most pairs swap freely isn't a sequence, it's a list, and the audience feels that even when they can't name it.

Before either one it asks the question everything depends on: can they leave? A pitch deck presented in a room and the same file sitting in an inbox are not the same artifact, and confusing the two is why decks that kill live die on slide four in email.

It never adds material. If something structural is missing, it names the gap and stops.

Install

git clone https://github.com/MichaelDoesMarketing/sequencing.git