Every week ends with something you built.Not something you learned about.
The Rabbit Loop is the structure behind every mission on Skilled Rabbit. Four phases. A concrete output at the end of each one. By the time you reach the end of your journey, you haven’t collected notes. You’ve built a body of work.
Most structured learning separates theory from practice. You learn a concept, then later — maybe — apply it. The Rabbit Loop collapses that gap. Every checkpoint starts with understanding and ends with having done. The understanding doesn’t transfer until the doing happens. That’s not a pedagogical opinion. It’s what every week on this platform is designed around.
Why we build it this way — read the philosophyFour phases. Every checkpoint. Every week.
The Rabbit Loop is the smallest repeating unit of the training. It runs inside every checkpoint — and by extension, inside every mission and every week. The four phases aren’t steps to follow. They’re the shape learning takes when it actually sticks.
Understand what you’re going to build — nothing more.
Before you touch anything, you understand the scope of this specific checkpoint. Not the whole mission. Not the whole week. This one checkpoint. The WHAT phase is deliberately narrow — it prevents the paralysis that comes from seeing the full picture before you’re ready for it.
Take the smallest real step — not the perfect one.
This is where most self-directed learning breaks down. People wait for the perfect setup, the complete understanding, the right moment. The HOW phase forces the smallest real step — the one that moves the work forward, even imperfectly. Finney coaches hardest here.
Do it. Publish. Show. Submit.
The GO phase is non-negotiable. Not “draft it” or “try it privately.” The checkpoint isn’t complete until the output exists in a form you can point at. A prompt you ran. A workflow you triggered. A feature you deployed. Accountability is built into the structure — not bolted on as a motivational extra.
The moment you see what you’ve made.
The WOW moment is the proof that the skill landed. Not the coach saying “well done” — you seeing what you produced and understanding that you made it. This is what builds the identity: not “I know how to do X” but “I have done X, and I can do it again.” Every week on Skilled Rabbit is designed backward from this moment.
The loop repeats three times per mission, five missions per week. By the end of a single week, you’ve been through the Rabbit Loop fifteen times. By the end of a journey, hundreds of times. The skill doesn’t come from understanding the loop. It comes from running it — repeatedly, on real work, with Finney in the background asking the question that keeps you honest.
Five missions. Fifteen checkpoints. One body of work.
Every week on Skilled Rabbit follows the same shape. Not because rigidity is a virtue, but because the structure is what makes forward movement possible without a classroom or a cohort.
150 XP available per week: 5 missions × 3 checkpoints × 10 XP each. XP is a progress marker, not a gamification layer — it tells you and Finney where you are, not how good you are.
Each mission ends when the output from that mission exists. Each week ends with Field Notes — a short, structured reflection on what you built, what worked, and what you’ll approach differently next week. Not a report. Not homework. A record of the work, written for yourself.
Five to seven hours a week. That’s what most learners spend. Built for people with jobs, families, and limited patience for filler.
You don’t finish a journey. You reach a depth.
Skilled Rabbit measures progress in depth, not completion. The distinction matters. Completion means you got to the end. Depth means the skill is in you — not just on a certificate.
Every training is a journey to a specific depth in the rabbit hole.
You understand the concept. You can explain it to someone else. Your first outputs are inconsistent — sometimes excellent, sometimes not — because the skill is still fragile. You’re in the hole. You can see where it goes.
Example — You’ve written your first structured prompts. Some work well. You don’t yet know reliably why.
You apply it. The inconsistency is shrinking. You’ve built enough times that the pattern is starting to feel automatic. You’re past the point where quitting makes sense — because you’ve already seen what the next level looks like.
Example — You’ve automated three recurring workflows. They run without you. You’re starting to see which parts of your work are next.
You build with it. You design systems, not just individual outputs. You’ve moved from “I can do this task with AI” to “I can design a process that does this task.” Other people start asking how you work.
Example — You’ve shipped a feature or product. You make architectural decisions. The work you produce is indistinguishable from what a specialist would produce.
It’s part of how you work. You can’t un-know it. The skill is no longer something you apply — it’s something you are. You reach maximum depth when you’ve shipped something live, earned something real, and started thinking about what comes next.
Example — You have a deployed product with paying users. You’ve iterated based on feedback. You’re thinking about the next version, not whether the first one was possible.
Each training takes you to a different depth. Prompt Mastery reaches Core — the skill is structural by the end. My Coworker reaches Deep in your specific role. Think › Build › Ship goes all the way to the bottom of the rabbit hole.
You don’t have to decide in advance how far you go. Start at Surface. The hole will show you the rest.
The last week doesn’t feel like the first.
The Rabbit Loop is designed to compound. Each time you run it, the next run is faster — not because the work gets easier, but because your tolerance for ambiguity grows. You’ve been through the WOW moment before. You know what it feels like to be stuck in HOW and come out the other side. That knowledge changes how you approach the next checkpoint.
By the end of your journey, you have:
A body of work
Not notes. Not a certificate tied to a multiple-choice exam. A prompt library, an automated workflow stack, or a deployed product — depending on which journey you took. Something you built, week by week, that you can use, show, or hand to a colleague.
A repeatable skill
The Rabbit Loop becomes automatic. You stop thinking about WHAT / HOW / GO / WOW as a framework and start moving through it naturally — on work outside the training, on problems that don’t have a Finney-coached path. The skill generalises.
A different identity
This is the part that’s hardest to describe before it happens. After weeks of finishing things — real things, not exercises — you become someone who finishes things. That shift is not motivational language. It’s what the WOW moment, repeated again and again, produces.
Finney runs the loop with you.He doesn’t run it for you.
Finney is present at every phase of the Rabbit Loop — but what he does changes depending on where you are.
At WHAT, he asks what you already know before adding anything. At HOW, he gives you the smallest push when you’re stuck — not the answer, the direction. At GO, he holds the accountability that a solo learner would otherwise skip. At WOW, he reflects back what you built — specifically, not generically.
He also tracks the pattern across sessions. If you keep getting stuck at the same phase across different missions, he notices. If your WOW moments are getting shorter — meaning the skill is building — he notices that too.
Learn more about how Finney works
The first loops are free.The rabbit hole starts here.
You don’t need to understand the full method before you start. You need to run it once. The first checkpoint of the first mission is where the Rabbit Loop becomes real — not as a description but as an experience.