Update backend and frontend

Use Polygraph to ship a feature that touches both an API and the UI that calls it.

A new endpoint needs to be coordinated with UI/UX changes. The repos sit on separate teams' release schedules, but the change has to land coherently or one side breaks the other. The work is a single feature (in a monorepo this would be one PR).

Example prompt

I'm inside the backend repo and run polygraph session start.

Add acme/frontend to this session.

Refer to my feature spec at <specification-file>.
This requires both API (backend) and UI/UX (frontend) changes.

Read both repos first. Confirm the auth contract and the shared response
type, then propose a plan with one bullet per repo before you write code.

Replace acme/frontend with the actual repo. The <specification-file> describes the feature so AI agents know what to build (e.g. PRD.md).

The agent reads both repos before writing code, so it understands the architecture and existing patterns. It then produces a plan for the current session that the child agents can execute on.

Open the PRs

Once the work is complete, ask the agent to open PRs against both repos.

Push both branches and open PRs.

For a change to a contract that several services share, see Update multiple microservices.