@AlexFinn: I did it. I figured out the perfect AI coding loop It's called the Finn Loop and it's 100x'd my vibe code output while …
Summary
AlexFinn shares the 'Finn Loop', an automated AI coding workflow using /spec, /build, and /review skills that runs in Codex/Claude Code, integrates with Linear for task management, and notifies via Slack, promising significant productivity gains by minimizing manual intervention.
View Cached Full Text
Cached at: 07/13/26, 10:00 PM
I did it. I figured out the perfect AI coding loop
It’s called the Finn Loop and it’s 100x’d my vibe code output while cutting the work I need to do down by 95%
ANYONE can implement this. It’s super easy. Here’s how it works:
-
3 new skills inside your coding agent. /spec, /build, /review
-
You start out with /spec “your idea”. The skill then asks you enough questions to fully understand your idea in detail then create a detailed spec inside Linear (amazing project management tool. Very generous free tier)
-
In another Codex/Claude Code session: you have a /build loop running. Once a spec is created, the /build skill picks it up and builds it out for you. Then advances the status of the issue in Linear
-
In another session, you have /review loop running. It picks up every issue that is built out then reviews it. Checks for security issues, optimization issues, then tests the code in its own browser, lays out test steps, takes screenshots, creates a PR, and puts it in its own vercel test sandbox for you to test it
-
The review loop then takes all of that and pings you in a channel in your favorite messaging service. I use Slack for this. It shows you the PR, gives you all the testing steps, and executive summary of the changes, and a link to the Vercel sandbox where you can test it
-
You go to the message in Slack, review the change, then send a rocket ship emoji as a reaction. This signals to the loop that the PR should be merged.
The only manual steps in this loop are you submitting an idea to your agent, and verifying the change at the end. Everything in between is automated in the loop.
Your vibe coding workflow today is hand holding your agent step by step on everything you build. You spend all day doing this.
Your vibe coding workflow when using the Finn Loop is you wake up, make a cup of coffee, give your agent a list of ideas, then come back at night and review all the changes. You’re free to do whatever you want during the day.
Let me know if you want my full spec, build, and review skills. Will release them soon. Will also film a tutorial video on this.
There’s also a ton more details I’ll share shortly too, like the interface I built for monitoring all of this.
You also can probably just send this tweet to your agent and it will recreate the Finn loop for you.
Carve off some time and try this out today. I promise it will dramatically improve your workflow
Similar Articles
anyone else getting burned out by the "vibe coding" loop?
A developer shares frustration with the 'vibe coding' loop—spending more time managing AI prompts than writing code—and asks how others stay productive with tools like Cursor and Claude.
@mvanhorn: https://x.com/mvanhorn/status/2068426104088748331
An article explaining the differences between goal, loop, and schedule commands in AI coding tools like Claude Code and Codex, and providing 15 practical loop examples for running automated tasks.
@sairahul1: https://x.com/sairahul1/status/2058832033628241931
A Twitter thread describing how to build a software factory using Claude Code with seven specialized AI agents to avoid the pitfalls of vibe coding, enabling one developer to ship features efficiently.
@0xCodez: https://x.com/0xCodez/status/2064374643729773029
A 14-step roadmap on loop engineering, guiding developers from manually prompting AI coding agents to designing automated systems that handle the prompting, verification, and iteration themselves.
@shmidtqq: https://x.com/shmidtqq/status/2068704187492221405
An in-depth guide to loop engineering for AI coding agents, explaining how to build automated loops that repeatedly prompt agents, verify results, and avoid runaway costs, illustrated with a case study of one engineer shipping 259 PRs in a month.