// distribution 1
Agent Skill
Free, available today, and built to integrate into your existing coding-agent workflow through one copied prompt.
Cursor · Codex · Claude Code · OpenCode
Arbityr
Be able to defend it
before you build it.
A decision-making system for developers building with AI.
Think before AI helps you ship the wrong thing.
Free Skill below · voice agent coming soonFree Skill today · voice agent coming soon
ArbityrThe best developers are not anti-AI.
They are anti-autopilot.
everything by handfully autopilot
The answer is not at either extreme.
The answer is in the middle.
scroll to explore
// see it in action
How a real decision session runs.
Two real engineering decisions, run through the process. Watch what Arbityr surfaces.
// available now
One prompt to your AI agent. Arbityr installs.
The same decision pressure-test ships in two forms: a free Skill you can add to your current developer workflow today, and a voice agent for spoken decision sessions that is rolling out next.
Click to open the install prompt, copy it, and paste it into your coding agent.
// distribution 2
Voice Agent
Coming soon as the web app. Check out the demos above, then join the waitlist for private alpha access.
Join the voice-agent waitlist// the pain
AI made coding faster.
It also made bad decisions cheaper.
The problem is not that AI writes bad code.
It is that it helps you skip thinking.
You can ship in minutes
and spend weeks defending why.
// what arbityr is
A fair witness.
The tool that helped you build the idea will defend it. The cold model will challenge it forever. Arbityr does neither — it pressure tests until it's satisfied, then stops.
A structured process. No stake in the outcome. Stops when your decision holds — won't pretend it does when it doesn't.
// the difference
chatbot
- — one-off conversation
- — answer-shaped output
- — no audit trail
- — can't be reviewed
arbityr
- — runs a structured process on your decision
- — stops when it's satisfied, not when you give up
- — defensible artifact
- — reviewable by your team
// the decision process
A structured process. Five moves. Arbityr drives four of them.
1
youBring the decision and context
Point at code, a diff, a doc, or paste a brief. One message.
2
arbityrArbityr maps the decision
Reads your context. Names what's actually being decided, not what you think is being decided.
3
arbityrThe system finds the pressure points
Not one challenge. A structured sequence, each one building on the last, each one specific to your context.
4
arbityrEvery hidden choice gets surfaced
The things you decided by not deciding. Each one made explicit before you move on.
5
arbityrLeave with a decision spec
What was decided, why, what was ruled out, the load-bearing assumption. Use it in a PR, a design review, or a team log.
run it once → one decision you can defend. run it every time → a system your whole team runs on.
// who it is for
Two seats at the table. Same decision layer.
For IC engineers
Make your technical decisions easier to explain, review, and defend before implementation.
Use AI to move faster without outsourcing the judgment that makes the code worth shipping.
- ✓ structured pre-commit thinking
- ✓ ammo for design reviews
- ✓ a record of why, not just what
For product & engineering managers
Add a decision layer before your team turns AI prompts into production decisions.
Help your team think before prompts turn into shipped work.
- ✓ shared decision vocabulary
- ✓ fewer "why did we ship this?" postmortems
- ✓ a culture of defensible velocity
Join the voice agent waitlist.
private alpha batches ↓
I am opening the voice agent slowly so Arbityr can learn from real spoken engineering decisions, not empty signups.