PRDs and specs

The PRD your agent drafted, reviewed before the backlog hardens.

Eng, design, and the stakeholder comment on one spec. Agent connect splits v1 from later when the tech lead asks.

Set it up for your agentHow agent connect works
livespecs/shift-swap-approvals.md

Shift-swap approvals

Owner: Imani Brooks. Surface: Loomwright mobile. Status: scope cut open.

Managers approve or decline a swap in the Loomwright mobile app. This spec is the cut for the first release. Payroll sync is named so the boundary stays visible when the draft is shortened.

Who it's for

  • Managers who approve swaps from the floor, not from a desktop, on the shift they already work.
  • Employees who requested the swap and need a yes or a no the same day, before they leave.
  • Admins who turn the feature on once per location, in Settings, and then re-save that location.

Empty state

Empty state: a blank calendar.

The first screen is what a manager sees at the start of a shift. A blank calendar does not say whether anyone is waiting. The pending list is a cheap query and can ship in v1.

Scope

v1 includes manager approval, a CSV export, and payroll sync.v1 is manager approval on mobile. Export waits.

Bulk export and payroll sync move to a later release.
  • v1: open a request, approve or decline, and notify the employee on the same swap.
  • Later: CSV export of decisions, then payroll sync. Not this release, and not a hidden setting.

Acceptance

A manager approves one swap on a phone. The employee sees that decision before the shift ends.

blank calendar

Mei Tanaka

The empty state should show who is waiting, not a blank calendar.

Sam Adeyemi

The pending list is a cheap query. We can do that in v1.

CSV export

Sam Adeyemi

@agent split scope into v1 and later, v1 without the export.

agent

Split the spec. v1 is approval on mobile. Export is later. Leaving this open so you can confirm the cut.

Start with @agent to ask the agent
ResolveReply
Fictional example: a Loomwright shift-swap PRD in Gander, with a design thread and a scripted agent connect reply.

How PRDs get reviewed today

A PRD in a shared doc collects comments well, until the agent rewrites the file on disk and the comments are stuck on yesterday's copy.

A review meeting gets design and eng in one hour. The notes from that meeting still have to be carried back to the agent. A ticket is a good end state and a bad place to revise a draft that is still moving.

Split the spec before anyone builds the export

Imani Brooks asks her agent for a PRD: managers approve shift swaps in the Loomwright mobile app. The agent writes specs/shift-swap-approvals.md. Imani runs gander watch and sends the link to Sam Adeyemi and Mei Tanaka.

Mei highlights the empty state and says the first screen should show who is waiting, not a blank calendar. Sam replies that the API can return that list. The thread stays between them.

Sam opens a new comment: "@agent split scope into v1 and later, v1 without the export." Imani's agent rewrites the scope, replies, and leaves the thread open because the cut is large. Mei and Imani see v1 without export on the same link. The spec goes to the tracker when the team accepts the cut.

Who's in the doc

WriterTech leadDesignerThe author's agent

Writer PM. Runs the agent and sends the link.

Tech lead Looks for scope that will slip the release.

Designer Looks for the empty state, the flow, and the words on the screen.

The author's agent Has the brief. Splits the spec when the tech lead uses agent connect.

Reviewers only need a browser. Talk to each other in normal threads. Use agent connect when you want the draft changed.

Agents that fit prds and specs

CursorThe spec can live in the repo next to the app, with MCP for agent connect.
Claude CodeSame repo path. Plan-style files and MCP work the same way.
Grok BotA prose-first PRD from a brief, with the Gander MCP server connected for agent connect.

Review the spec on the file the agent is editing. Move it to the tracker when the scope is real.

See how it works on the homepage