momentum

name

momentum

description

Turn an overwhelming idea into one shippable slice and one next action — so you start today instead of drowning in the plan. Use when you have an idea you want to build but the scope/plan is overwhelming, when you're stuck at "where do I even start", when a project has stalled, or when you can feel burnout coming from a plan that keeps growing. The opposite of a big plan — it shrinks, it doesn't expand.

momentum

You have an idea. You want to build it. But the moment you try to plan it, the scope balloons — every feature spawns three more, the whole thing feels infinite, and the overwhelm makes you do nothing. That stall is the burnout.

This skill's one job: shrink the mountain to a step you can take in the next ten minutes, and hide the rest of the mountain so your brain stops carrying it.

It does NOT produce a roadmap, a phased plan, or a task tree. Those are what's crushing you. If you catch yourself making one, stop.

Why overwhelm happens (so you can disarm it)

• You're holding the whole thing in your head at once. Planning-mind and doing-mind fight for the same space; overwhelm is that friction. Written down and shrunk, the fight ends.
• Scope is a feeling, not a fact. "Build the app" feels infinite. "Add one button that prints hello" is finite and doable — same idea, different size.
• Burnout is long stretches with no ship. No feedback, no small win, just a plan that grows. The cure is shipping something tiny, soon, and often.

The method

Run these in order. Keep it to a few minutes — this is a cut, not a study.

1. Name the one outcome (one sentence)

"When this works, I can ______."

The single core value, in one plain sentence. If you can't say it in one sentence, the idea's still fuzzy — ask one clarifying question, then write the sentence. Everything the idea "should also do" is not this sentence.

2. Find the walking skeleton

The thinnest end-to-end path that delivers a sliver of that outcome and actually runs. Vertical, not horizontal: one feature working start-to-finish beats five features half-built. Ugly, hardcoded, no styling, no edge cases — but it runs and does the one thing.

Ask: "What's the smallest version of this that I could show someone and it does something real?" That's the first slice.

3. Park everything else (out of sight)

Every "it should also…", every nice-to-have, every edge case → goes to the Parking Lot list. Written down, then ignored. Writing it down is what lets your brain release it — the list is a promise to your future self, not today's work. You do not look at it again until slice 1 ships.

4. One next action

The very next physical step, small enough to start now without dread. Not "design the schema" — "create the file and write one empty function." If the next action feels heavy, it's still too big; cut it again. The bar: you could start it in the next 10 minutes.

5. Timebox, then ship the slice

Work one fixed block (25–90 min, your call). Ship the slice even if it's ugly. Working-and-ugly beats perfect-and-imagined. The ship is the reward — momentum compounds from the first one, not the tenth.

6. Permission to stop

Decide "done for now" before you start, so you can stop without guilt. Burnout is often just not knowing when you're allowed to stop. When the slice runs and does its one thing: you're done for now. Walk away a winner.

The kickoff card

Fill this out (and nothing more). Save it next to the project as KICKOFF.md if it helps:

# <idea> — kickoff card

Outcome:  When this works, I can ______.

First slice (ships today):  ______
  → Next action (start now):  ______

Done-for-now =  ______   (the moment I'm allowed to stop)

Parking lot (NOT now — do not touch until the slice ships):
- ______
- ______

After the slice ships

Re-run this skill for the next slice: pull ONE item from the parking lot, make it the new outcome, repeat. One slice at a time. Never re-open the whole mountain — that just rebuilds the overwhelm you escaped. The project gets built as a series of small ships, not one heroic push.

Rules (for me, when running this with you)

• Produce exactly four things: the one-sentence outcome, the first slice, the one next action, the parking lot. Nothing more.
• No phased roadmaps, no estimates, no task trees — those are the disease, not the cure.
• At most one or two clarifying questions, and only if the outcome sentence is unclear. Questions add to overwhelm; spend them carefully.
• Bias every cut smaller. When unsure between two slice sizes, take the smaller one — it ships sooner.
• If you (the user) start expanding scope mid-run, I'll name it and park it, not plan it.
• Pairs with ponytail (cuts code scope) — this cuts project scope. And with brainstorm when the idea genuinely needs design first; but if the problem is overwhelm, start here, not there.