How 10xs works
Start from an idea or from your repo. You own the repo, the plan, and the merge button.
- 01
New project: write a prompt.
One sentence about what you want to build is enough; 10xs asks nothing else up front.
- 02
Read the facts back; agree or edit.
10xs writes back what it understood: who it is for, what done means, the stack, and what it will not do. Say "Sounds good" or edit a fact.
- 03
Get a plan you can argue with.
From the facts it drafts scope, architecture and the order of work. Accept, say "not quite", or regenerate. Nothing is built until you accept.
- 04
The plan becomes a board.
The accepted plan is decomposed into cards with dependencies, each small enough for one agent to finish in one attempt.
- 05
Connect your agents with one line.
Paste the connect line into a terminal on your machine. Your own agents (Claude Code, Codex, Cursor, any agent) claim cards; you set how many run at once.
- 06
Watch work, not logs.
Each card shows its attempt, what the agent did, and a conversation you can type into while it runs. If an agent needs you, the card says why in plain English.
- 07
Only checked work comes back.
Every finished card returns as a pull request the gate has run: tests, types, build, the house rules. You accept or send it back with words.
- 08
Repeat tonight.
New feedback becomes new cards; the agents run again; you review in the morning.
