storybloq's approach to using fable efficiently: it plans and reviews, opus implements in parallel
这条记录涉及编程工具或代码能力更新，适合开发者评估工作流变化和可复用价值。
Storybloq 是一款会话管理器，它将项目状态以纯文本文件形式保存在代码库的 `.story/` 文件夹中，以便新会话能从上次结束的地方继续。Storybloq 的核心在于其“编排”功能，它利用 Fable 进行规划、制定规范和审查，然后将具体的实现工作分配给并行运行的 Opus 代理。…
A couple of months ago I posted about storybloq, a session manager for Claude Code that I built. It keeps your project state (tickets, issues, handovers, notes, lessons) as plain files in a .story/
folder in your repo, so a new session picks up where the last one left off instead of starting from zero.
Using Fable to write out every implementation is a waste. Fable should do to the thinking: the plan, the spec, and the review.
So in Storybloq's orchestration you can do that. Fable plans the work, turns each backlog item into a full spec, and holds the review gates, then hands the implementation to a fleet opus agents running in parallel. You get fable's judgment on every decision without paying fable rates to type out the code.
That is the core of what shipped today, orchestration. You point it at your backlog and fable drives the opus agents through it, with a plan review before any code is written and a review of the actual diff before it ships.
Federation, for multi-repo setups. If your app is more than one repo (backend, client, a shared package), storybloq reads across all of them: what is blocked on what, what to work on next across the whole system instead of one repo at a time. If you work across repos I really recommend it. It is the change I use most.
backlog through git without clobbering each other. Concurrent edits to the same file merge field by field instead of leaving conflict markers, and it tracks who is working what so two agents do not grab the same item.
Put together: set up a multi-repo backlog in storybloq, break down your project into tickets and phases in a roadmap, then let fable drive opus agents through the items in parallel, gated on the plan and the diff.