Connecting your developer’s Claude Code or Codex to the requirements
How a developer’s email lets their AI read the confirmed requirements and what changed — what goes and what doesn’t, connecting and signing in for each tool, and managing connections.
By PLARO · Content date
What the AI reads, and what it never gets
It reads the current version’s requirements (number, details, acceptance criteria, source), what changed between versions and why with the client’s confirmation, and open questions and failed acceptance checks. It never gets AI findings nobody processed, meeting and chat text or quotes from it, amounts, quotes, agreements or schedules, or client names and contacts. It is read-only, and the developer needs no account.
The PM enters the developer’s email
In the project’s developer AI connection, enter the developer’s email (the name is optional) and press [Connect and mail the guide]. PLARO mails that address the steps for each tool. There is no key to hand over; [Copy the connection guide] gives the same steps to send by chat or email. A project can have up to 5 connections.
Connecting Claude Code
In Claude Code, enter /plugin marketplace add plaro-kr/plaro-ai, then /plugin install plaro@plaro-ai. Then pick plaro in /mcp and sign in: the browser opens, you enter the address the PM wrote and the 6-digit code mailed to it, and pick the project. From then on, changed requirements come in when you send a message, and three commands appear — plan the changes (plan_changes), plan the project (plan_project) and check before acceptance (check_acceptance).
Connecting Codex
In a terminal, run codex mcp add plaro --url https://plaro.kr/mcp/v1: the browser opens at once, and signing in works as for Claude Code. The tool renews the sign-in by itself for 30 days; after that, or after signing out, run codex mcp login plaro to sign in again.
Two lines in the repository, and managing connections
Add two lines to the repository’s instruction file (AGENTS.md — or CLAUDE.md for Claude Code if there is one): “This repository’s requirements are in the PLARO project” and “Before building or changing a feature, check the related requirements, open questions and recent changes with the plaro tools”. Then even a tool without notices looks at PLARO first. The PM sees in the connection list who received which version and can revoke any connection at any time; a connection nobody uses for 90 days stops by itself. Claude Code is a product of Anthropic and Codex of OpenAI; PLARO is not affiliated with or endorsed by either.
Guides to requirements and meeting changes
PLARO compares client project requirements with meeting content, helps managers keep reviewed changes in new document versions, and records client confirmation.
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.