fable produced 60+ (!) ready to merge prs for @mainframe overnight. here's how you can set up a software factory using fable as an orchestrator. prompt included! 1. narrate your *entire* todo list — everything that's top of mind — using dictation. i used @usemonologue and my prompt was ~10K words! you have to use voice because we want excruciating levels of detail. 2. locally, tell fable to plan all the work and put it in @linear. the goal is to make it such that a dumb model dropped in linear knows *exactly* what to do. aka all issues should have a clear DAG, plan, and optimize for max. parallelizability. i recommend running fable on high and having it fan out to codex subagents on xhigh (using the cc codex plugin.) to save usage. just make sure that fable itself is doing the architecture for the hardest issues! 3. now switch to @DevinAI. we'll use devin to run our factory because our orchestrator needs to be a cloud agent (it's going to run for a long time!), and be able to spin up other cloud subagents. 4. hook up the @linear @SlackHQ mcps. this will let your agents read the fable planned work, and communicate with you/your teammates. e.g. it can talk to your coworkers to make sure it's not stepping on anyone's feet! 5. a good feedback loop is *crucial.* before starting, make sure you have a bug bot (we use @cursor_ai.) and that your agents can test all its changes. e.g. we use the fantastic @limrun to make sure our agents can do ios development e2e. 6. create a devin ultra (fable) agent — this will be your orchestrator or 'middle manager.' we're going to tell it to look at linear and dispatch subagents for all tasks. the middle manager's goal is to keep spinning up subagents with the right level of intelligence until all the work is done. and keep all agents unblocked while you're sleeping, hanging out in the park, whatever! the reason the middle manager is able to orchestrate all of this is because fable planned everything in linear. and because the middle manager itself is also fable (contrary to most of its subagents.) 7. to prompt your middle manager, attach the middle manager prompt i'll post in the comments, modified for your repo. it's important that we *attach* the middle manager's prompt to our conversation vs. typing it out, so it never gets compacted. the middle manager's context window is holy. so our prompt tells it to spin up subagents — instead of doing things itself — for pretty much everything. 8. the prompt has some other cool, non-obvious details. firstly, every agent is told to keep working until it's met the burden of proof. in our case that's a (self)-review, bug bot being green, bug bot fixes being elegant, and a recording. we tell our middle manager to enforce this. secondly, we ask the middle manager to make sure linear stays up to date and communicate via the slack mcp. specifically, it should tag coworkers in slack whenever it has a question and post heartbeat updates in the eng channel. 9. your software factory is ready to go! in our case, it worked for 12+ hours without getting blocked. and produced extremely high quality prs. addendum: all of this is possible because with @AnthropicAI fable, models are finally smart enough to orchestrate/navigate large sets of work and their dependencies. and fable is a great software architect! now of course the 'downside' is that you're now review bottlenecked. we have 60+ PRs to review! but i think as an industry we should be able to come up with some innovation there. we'll certainly try our best to help here with @mainframe too! hope this is helpful! happy to answer any qs.