You really don't need "software factory" or "loop engineering" to work effectively, or in this case burn $10K per month on a subscription of $200/month. A few very simple tips: * make every ticket ready to start -- pay attention to the grooming and design phase of any task -- ruthlessly delete tickets; * set up a separate repo for the OS that's different than the code repo -- this repo stores working agreements, workflows, learnings, docs. Keep the code repo(s) clean and dry -- pure code and nothing else. * always start working from the OS repo: OS + linear tickets == durable work context. Code is just a short-lived artifact * if you actually need to use goals, write them down in the OS first and then issue them to agents. * don't ever read code, but design a few "gates" your agent have to go through. For me: pixel gate for me to review UX, code review gate(automatic), release gate (automatic). * Design your "squad" -- a group of agents together doing one task. One squad for one complete epic. Tickets should be filed at squad level, such as "finish onboarding v2", not at task level, like "add a button to onboarding". -- 过去的 30 天其实没有用任何所谓的“软件工厂”/loop/graph，就是遵照一些基本的软件工程的原则，默默地就烧掉了 13B 的 tokens，折合 API 价格 $10110. 就是几个很普通的原则如上