Code is the easy part.
pair runs your development process with AI, from PRD to merged PR.
Assisted, supervised or autonomous:
you decide who drives.
npm install -g @foomakers/pair-cli
Claude Code plugin, optional: /plugin install pair@pair
New in v0.5.1:
delivery workflow, lifecycle modes, autonomous backlog delivery. Read what's newSound familiar?
These are the questions every team hits when AI enters the workflow.
Who owns the process when AI writes the code?
Fast code without a process is fast debt.
Who checks the AI's work?
An agent that writes, judges and merges its own PR grades its own homework.
Where do decisions live between sessions?
Every new prompt starts from zero unless decisions are files.
How far do you let it run?
All or nothing is not a policy. You need gates, tiers and a way to take the wheel.
Works with
Assisted mode on every tool. Supervised and Autonomous need a harness with subagents or an engine: Claude Code, Codex, pi, opencode.
One lifecycle, from idea to merged PR.
Four phases take a product from PRD to code. Two workflows, refinement and delivery, run on top of them. Three modes decide who drives. Same process every time, whoever or whatever runs it.
Induction
Once per project: PRD, bootstrap, prioritized initiatives.
Strategic planning
Per initiative: epics sized for a few sprints each.
Iteration
Per epic: stories, refinement, tasks. Ready means ready.
Execution
Per story: implement, independent review, merged pull request.
Assisted, Supervised, Autonomous.
Three modes, like the levels of driving automation. Same phases, same gates. Raise the level as trust grows.
Assisted
You drive, pair helps.
Scope: each step
You: every step
pair guides every phase with AI. You run each skill and approve each step.
Supervised
pair drives one stretch, you take over when asked.
Scope: one card, end to end
You: at checkpoints and escalations
pair automates one card end to end, from Ready to a review-approved PR, and stops at a checkpoint or an escalation.
Autonomous
pair drives inside the area you define.
Scope: the backlog, filtered by your criterion
You: only on escalation
pair watches the backlog and processes every card matching a criterion you set, for example risk:green, and hands a card back when a human is needed.
Safe by default: nothing merges unattended until you declare it.
AI should not grade its own work.
One card, one state machine, independent roles. The delivery workflow takes a Ready card to a review-approved PR.
Implement
Tests and code, test-first, one pull request per story.
Verify
An independent reviewer checks the exact PR head. The implementer never reviews.
Fix inside a seal
Every finding gets a failing test first, sealed byte for byte. The fix lands above it and cannot weaken it.
Resume anywhere
State is files, not a chat. An interruption costs nothing.
Demo
Risk tiers decide the ceremony.
Every story carries a risk tier. The tier decides the gate, the review depth and whether a PR may merge without a human. Review can raise a tier, never lower it. Escalation reaches a human only when the tier says so.
How tags drive automationBuilt for every scale
Alone, with a team, or across an organization: pair adapts to your workflow.
Solo Dev
AI writes code fast, but your project has no structure, no tests, no process.
Start Assisted today. Hand your green cards to Autonomous when you trust the gates.
Get startedTeam
Every team member uses AI differently. No shared conventions, inconsistent output.
One .pair/ folder, every assistant, the same decisions. Supervised runs for the known backlog.
Set up your teamOrganization
Scaling AI adoption across teams without governance is a recipe for technical debt.
Own the Knowledge Base, publish versions, every project installs from a tag. GitHub or Azure DevOps.
Roll out across teamsWhat you get
Everything your AI assistant needs to follow your process and your standards.
Skills
Composable process skills on the Agent Skills open standard, run by any assistant that reads them.
Knowledge Base
Guidelines, templates, and standards your AI reads automatically.
Adoption Files
Tech decisions, architecture and way of working, versioned and enforced.
Workflows
/pair-workflow-cycle, /pair-loop and pair-cli run chain the skills and stop where you tell them.
Open Source
pair is free and open source, MIT licensed.
foomakers/pairAir-gapped? Download the manual zip from GitHub Releases.