Your agent writes the plan. Your team reviews it before it runs.
Implementation plans, RFCs, migration plans, runbooks, post-mortems. One live doc per draft, comments anchored to the code, and on-call changes handed back to the agent.
The docs you produce now
If you code with an agent, it drafts more of your plans than you do. The implementation plan, the RFC, the migration plan, the runbook for the new endpoint, the post-mortem after the incident. Writing got fast. Review didn't. Each one needs the tech lead, the on-call for the touched service, and the PM, and they all look in different places.
What you can review with Gander
Quillfeather
Implementation plans
Tech lead, on-call, and PM comment on the plan. On-call uses agent connect to add rollback. Read more →
Cobaltfern
RFCs, design docs, ADRs
Design review before the PR exists, with the agent that did the research still on call. Read more →
Oxbeam
Migration and rollout plans
Cutover plans change hourly. Review the live one, not last night's paste. Read more →
Saltmarsh
Runbooks
Get the on-call rotation to break the runbook before 3 AM does. Read more →
Emberlane
Incident post-mortems
Everyone who was on the incident comments on one timeline. Read more →
A week with Gander
Tuesday morning your coding agent finishes the migration plan and saves plans/ledger-cutover.md. You run gander watch and drop the link in the platform channel and the on-call channel.
The tech lead opens it first and leaves a thread on the cutover sequencing, with a question for you about the dry-run. The architect replies with the option you rejected and why. That's a conversation between two people, so it stays a normal thread. The agent never sees it.
On-call opens the link on the bus. They highlight the production cutover step and use agent connect: "@agent add a dry-run step and a maintenance window for the member-facing surface." The comment goes to your agent session, the one that wrote the plan and still has the codebase and the runbook open. It edits the plan, replies in the thread with what it added, and the page updates for everyone on the link. You didn't paste anything anywhere.
By Friday the plan is signed off, the file lands in the repo as the design doc, and the migration has a dry-run on the calendar. The file on your machine was the plan the whole time.
What you need
You run the coding agent, run gander watch on the plan file, and send the link. macOS, Linux, or Windows through WSL. Reviewers only need a browser. No IDE, no repo clone, no agent account.
Agents that fit
./plans/ and offers a gander. gander mcp install wires agent connect into the session.~/.cursor/mcp.json.An engineering plan doesn't need a new doc tool. It needs the tech lead, on-call, and PM on the same live file, with the agent that wrote it still on call. Then it goes to git.