正在打开每日关注
正在打开每日关注
以 /spec、/build、/review 串起从想法到合并的 Agent 自动研发闭环。
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: 1. 3 new skills inside your coding agent. /spec, /build, /review 2. 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) 3. 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 4. 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 5. 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 6. 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
是什么 这条推文提出“Finn Loop”,把 Agent 驱动研发拆成 /spec、/build、/review 三个长期运行的技能环节:先通过提问澄清想法并写入 Linear,再由另一会话自动实现,最后由审查会话完成安全检查、优化、浏览器测试、截图、PR 和 Vercel 沙箱验证,结果通过 Slack 返回给人。
核心设计 它的关键不是单次提示词,而是把研发过程设计成可接力的状态机:Linear 充当任务队列与状态源,多个 Agent 会话各自负责清晰边界,/review 与 /build 构成反馈回路,人工只在输入想法和最终审批处介入。图片用极简手绘箭头强化了“规格—构建—审查—合并”的顺序与循环关系。
关键洞察 该模式适合将需求相对明确、验收标准可自动化的任务批量化,能减少上下文切换和重复监督,把工程师从逐步陪跑转向结果验收。真正的杠杆来自流程编排、状态推进和独立验证,而非单纯增加模型调用。
边界与风险 “100 倍产出”和“减少 95% 工作”属于作者的个人宣传,不能直接视为普遍结论。自动规格可能误解目标,Agent 之间也可能放大错误;安全审查、测试覆盖、沙箱隔离、权限控制和合并门槛仍需明确。它讨论的是 Agent 工程与研发效能,不是以视觉、交互或体验为主要价值的设计内容。