You're building something that takes time. This module is about not burning out before you get there.
The threat isn't the work. It's the waste — the energy you spend reading outputs that are 70 to 80 percent noise before you reach the ten lines you needed. Over a long project that accumulates. You arrive at mile 20 exhausted from reading, not from creating.
Four steps fix it. They only move in one direction.
What most sessions look like by default
80% — repetition, narration, flattery, preamble
20%
You gave Claude the origin. It doesn't need to recite it back. You asked for a thing. It doesn't need to announce it's about to make the thing. Show me — don't tell me you're about to show me.
What the sequence below produces
20%
80% — the actual deliverable
Lead with the deliverable. You evaluate it in ten seconds. You either feel it or you don't. No wading, no decoding, no energy spent on outputs that haven't earned it yet.
double-click any line that resonates
// step one
Lead With the Deliverable
Claude shows you the thing — the paragraph, the outline, the reframe, the structure — clean, without preamble. No recap of what you said. No announcement of what it's about to do. The deliverable is the first thing you read. You'll find the prompt that installs this at the end of the module.
// step two
Fast Options If the First Doesn't Land
If the first deliverable isn't right, don't ask for an explanation — ask for a variation. Keep the ratio flipped. More options, no narration between them.
When the first one misses
"Give me three more versions. Different angles. No explanation between them — just the options."
You're scanning, not reading. You'll know the one when you see it — and no amount of explanation between options gets you there faster.
// step three
When Something Resonates — Then Ask
This is the only moment the detail is earned. You found the one. Something clicked — the angle, the phrasing, the structure. Now you want to understand it. Now the breakdown has a purpose.
Not before. The explanation serves the winner. It doesn't help you find the winner.
After the one lands
"This one. Break it down — what did you do here, and why does it work?"
The detail is no longer noise — it's instruction. You chose this one. Now you're learning from it.
// step four
If It Needs to Be Documented — File It
If the breakdown belongs in your Launch Pack — a decision, a method, a framework worth carrying forward — tell Claude to file it now while it's in front of you. Tag it, hold it, mark it. When you run your Launch Pack session, Claude already knows what's waiting. You won't be hunting for it. It'll be there because you flagged it at the moment it earned its place.
Filing for the Launch Pack
"File this for the Launch Pack. Tag it: [what it is]. When I run the Launch Pack session, I want this included — what we decided, what produced it, and how to replicate it."
Claude holds it. When the Launch Pack session comes, it surfaces everything you flagged — organized, labeled, ready. The documentation was written at the moment of decision, not reconstructed from memory later.
Show. Resonate. Ask. File if it earns it. That sequence protects your energy across every session between now and the finish line.
// try this
One Session. One Rule.
Open your next session with this prompt. Run the whole sequence once — let Claude show you something without preamble, evaluate it fast, and only ask for the breakdown after you find the one that resonates. Notice how different the session feels when you're scanning instead of reading.
The install prompt — use this at the start of every session
"Before we start: show me first. No preamble, no recap of what I said, no announcement of what you're about to do. Lead with the deliverable. If I want the breakdown, I'll ask for it after I find the one that works."
One prompt. Sets the ratio for the entire session. Claude shifts from narrator to producer — and stays there.
where you are
NowYou have the four-step sequence and the install prompt that sets the ratio from the first message of every session.
NextUse the install prompt in your next session. One run-through of the full sequence is enough to feel the difference.
ThenProjects and Workspaces — now that you're pacing yourself correctly, you're ready to build the infrastructure for sustained creative work.
Continue to Module 15
Projects and Workspaces
Building the infrastructure for sustained creative work.
→