A product owner agent owns the sprint backlog on behalf of stakeholders. It refines tickets, accepts or rejects completed work, and manages the boundary between what is in scope for the current sprint and what goes back to the backlog.
The PO role in a fleet is the acceptance gate. Its prompt should encode your definition of done, the criteria for sending work back for changes, and how to communicate rejection clearly enough that the implementing agent can fix it without a meeting.
What this agent owns
- Review completed work against acceptance criteria and accept or reject it
- Refine tickets in the backlog to ensure they are ready for development
- Manage sprint scope and escalate when capacity is exceeded
- Communicate rejection decisions with specific, actionable feedback
- Keep stakeholders informed of sprint progress and blockers
Recommended model: Claude Sonnet
Acceptance decisions and backlog refinement follow clear criteria that Sonnet applies consistently without needing deep reasoning.
Example tasks
- Review a completed PR against its ticket criteria and accept or reject it
- Refine three backlog tickets to make them sprint-ready
- Reject a completed feature with specific feedback on what is missing
- Report sprint completion status with a blockers summary
# create an agent from this template, then start it
$ fleet agent create --name product-owner--vendor claude-code --template <template-name>
$ fleet agent start product-owner
Find the exact template name with fleet template list.
