Flow mode
How I take a feature from idea to merged PR with agents. One model plans, a different one reviews the plan, a third reviews the code, and it has to work in a real run before it ships.
About
An agent reviewing its own work tends to approve it. So every feature I build goes through a spec, a plan, a review by a different model, a real run and a second review of the code. Then there's a PR, and it merges when I say so.
It starts with questions. The agent reads the code first, then brings you only the decisions that are yours, as multiple choice with a recommendation. Each decision in the spec records who made it.
Reviews catch bad reasoning. Real runs catch what nobody thought to ask about, so your version should name your own checks. Put them in your project's agent instructions, and the skill reads them from there.
Production changes, secrets, releases, new spend and merges stay with you unless you say otherwise.
Read more in How I ship with T3 Code, tstack and flow mode.
Built on
The PR and review steps use tstack by Theo Browne. sol-loop is what runs the code review, and it needs a way to reach another provider's model. T3 Code does that for me.
The optional steps use unslop by poteto for PR descriptions, and working with agents for journals.
The skill is a local text file your agent reads. It doesn't send your project to no.dev. If your agent uses a cloud model, that provider's normal data handling still applies.
Start by asking: "Use flow mode to build this feature." Small fixes don't need it.
Installation
Flow mode calls skills from tstack, so install those first. Read them before you do. They're instructions your agent will follow.
git clone https://github.com/t3dotgg/tstack
cp -R tstack/skills/* ~/.claude/skills/ # Claude Code
cp -R tstack/skills/* ~/.codex/skills/ # Codex
tstack needs an authenticated GitHub CLI and python3. sol-loop also needs a way to run another provider's model, which T3 Code provides. See the tstack README for details.
Then download SKILL.md from the top of this page and inspect it.
For Claude Code, create a flow-mode directory inside ~/.claude/skills/ and place the file there as SKILL.md. For a single project, use .claude/skills/flow-mode/SKILL.md in that repository. Invoke /flow-mode.
For Codex, create ~/.agents/skills/flow-mode/ and place the file there as SKILL.md. For a single project, use .agents/skills/flow-mode/SKILL.md. Select the skill or invoke $flow-mode.
Start a new agent session if the new skill does not appear.
On first use, tell the agent where your specs live, which checks CI runs, how to run your product for real, and what costs money. It will offer to save that in your agent instructions. Review the addition before saving it.