The spec your agent drafted. Eng, design, and you, on one link.
PRDs, research synthesis, release notes, and the engineering plan beside them. Review before the backlog hardens.
The docs you produce now
The PRD, the interview synthesis, and the release note are all coming out of an agent now. The bottleneck is the people who have to react: the tech lead, the designer, support, and you. Pasting each draft into a different doc makes the agent's copy and the reviewed copy drift apart.
What you can review with Gander
Loomwright
PRDs and specs
Tech lead, designer, and stakeholder comment on the spec. The tech lead uses agent connect to split v1 from later. Read more →
Wrenfield
Research and interview synthesis
Interviewers and the PM check the synthesis. An interviewer uses agent connect to move a quote to the admin persona. Read more →
Loomwright
Release notes and changelogs
Product, support, and marketing comment on one draft. Support uses agent connect to add what admins do after upgrading. Read more →
Quillfeather
Implementation plans
Tech lead, on-call, and PM comment on the plan. On-call uses agent connect to add rollback. Read more →
A week with Gander
Tuesday you ask your agent for a PRD and run gander watch. You send the link to the tech lead and the designer.
The designer leaves a human thread on the empty state. The tech lead uses agent connect: "@agent split scope into v1 and later, v1 without the export." The agent rewrites the scope section and replies. Thursday's release notes go out on their own link so support can ask for the admin steps. The PRD stays the local file until it is ready for the tracker.
What you need
One person on your team runs an agent that writes markdown to a file on their machine (macOS, Linux, or Windows through WSL) and installs the Gander CLI. That person is the author. Everyone else opens the link in a browser. No install, no agent account.
Agents that fit
A spec does not need a second home. It needs eng and design on the file the agent is still editing.