Developer AI
Your developer’s AI reads the confirmed requirements
Connect the project to the Claude Code or Codex your developer uses. When they talk to it, PLARO first tells it “since the last notice — 1 new version · 3 requirement changes · 1 open question,” and one command plans the changes in that repository. Developers don’t sign up — they sign in with a code mailed to them — and PLARO only gives read access.
Change notice “v1 → v2” → the change-planning command → PLARO shows “received up to v2”
What goes in, what comes out
- Goes in
- The developer’s email (one per person) — they sign in with a mailed code
- Comes out
- Requirements · what changed · open questions · unmet acceptance criteria → Claude Code · Codex
- Limits
- 5 connections per project · one stops after 90 days without use · a sign-in lasts 30 days
- Time
- Told when they send a message — if it doesn’t arrive within 5 seconds, work just goes on
- What it doesn’t do
- Writing · pushing · sending meeting transcripts, amounts or client contacts
How you use it
01 · The PM enters the developer’s email
PLARO mails them how to set it up. Revoke it any time.
02 · The developer connects
Two lines for the Claude Code plugin, one for Codex. They sign in with a mailed code — there is no key to pass around.
03 · Told when they talk to it
“v1 → v2” — what changed and whether the client confirmed reach the developer’s AI first.
04 · Three commands to plan with
Plan the changes (plan_changes) · plan the project (plan_project) · check before acceptance (check_acceptance). The PM sees “Sam — received up to v2.”
Example — Online store renewal
- Before
- Working from v1 — the R-2 card payment screen
- In the conversation
- PLARO “v1 → v2: R-2 changed (card → card + PayPal) · confirmed by the client”
- After
- Change plan — PayPal on the R-2 payment screen · 3 places to touch · 2 tests · ask the PM about R-7
Questions about this feature
- Which tools are supported?
- Claude Code and Codex for now. We connected both and checked them end to end.
- Does our code go to PLARO?
- No. PLARO only hands out the requirements; it never reads or writes your repository.
- Does the developer’s AI get the transcripts?
- Meeting and chat transcripts, amounts and client names and contacts are not sent. A name you write into a requirement’s text goes with it.
- What if the developer changes?
- The PM revokes the connection and enters the new developer’s email, any time. A connection unused for 90 days stops by itself.
Getting started
Requirements document example and reusable template
Use an online store redesign sample to separate requirements, acceptance criteria and open questions, and keep document versions.
Review meeting changes and request client confirmation
Compare a meeting excerpt with requirements v1, review the proposed change, then create v2 and request client confirmation.