Documentación
Agentes de código
Cómo cualquier agente de código sigue el contrato Peacae.
Working with coding agents
Any coding agent that can read instructions can follow Peacae. Point it at the agent contract — one contract, any vendor.
| Tool | How |
|---|---|
| Chat / CLI agents | “Follow the agent instructions” |
| Agent instruction loaders | Root agent instructions point at the contract |
| Cursor | Same; optional thin skill pointer in the editor |
Good prompts
Paste into your coding agent. For longer briefs to design and build tools (Peacae optional), see the Prompt library.
You → agent
Plan X using Peacae.
Start the next planned task and keep the board updated.
If blocked, set blocked_at and write what you need from me.
Submit for review when ready; don’t mark done unless I say so.
If you need another repo, track it here and put real tasks in that project’s setup.
Review discipline (agent ↔ developer)
Default: finish work → in_review_at, not done_at.
done_at is for your explicit approval (or an explicit self-approve instruction).
When ready, the agent should say:
Task is in review — say approve if you want it marked done (and commit when you want).
| Who | Action |
|---|---|
| Agent | Implements, sets in_review_at + a short notes summary, asks for approval (does not commit unless asked) |
| Developer | Reviews; says approve (or requests changes) |
| Agent | On approve, sets done_at. Commits only when asked |
That handoff is the collaboration between AI agent and developer in Peacae — no separate ticket tool required.
Cross-project work
If you send the agent into another repo or product:
| Where | What |
|---|---|
| Current project board | Always add a clear task naming the other project/path, why, and done criteria (short notes). |
| Other project’s setup | Prefer real execution tasks there when that repo has agent-ready setup. |
| If the other setup isn’t writable | Keep tracking on the current board with short clear notes / blocked_at. |
Pattern: coordination here + execution there. No silent side trips. Do not merge two products onto one board without labeling the coordination task.
synced (Desktop-owned)
Peacae Desktop may write "synced": true on a feature/task on the board after a successful cloud push, and "synced": false when that row’s content changes again. Agents may read it; they must never write it. Sync queues still live in Desktop — this flag is just the board-visible hint.