# Product owner

> Coming soon. The Product owner triages your backlog, turns vague requests into clear issues, and drafts stakeholder updates, with every write behind Approve.

Status: Coming soon

> [!SOON]
> The Product owner is Coming soon. This page describes what it will do when it opens, so you can plan ahead. Today the [Coder](/docs/personas/coder) is the one available persona.

The Product owner is the assistant that keeps your backlog clear and your team pointed at the right work. It turns a rough idea into a well-scoped issue, ranks what to do next, and hands build work to the Coder with a short brief.

## What it will do

- Triage and tidy the backlog so the next job is obvious.
- Rewrite vague issues with a goal, scope, and acceptance criteria.
- Break a large feature into small pieces that can ship on their own.
- Rank work for the week or the sprint against your goal.
- Draft status updates for the people who need to know.
- Hand scoped work to the Coder.

## Skills

| Skill | What it will do, in plain words |
| --- | --- |
| Week goal backlog | The first win. Rewrites vague open issues with acceptance criteria and ranks the backlog against this week's goal. |
| Triage the backlog | Reviews open issues, groups them, and suggests what to keep, change, or close. |
| Clarify requirements | Turns a vague request into a problem, users, scope, non-goals, acceptance criteria, and open questions. |
| Draft an issue | Writes a well-scoped issue or user story with a goal, scope, and acceptance criteria. |
| Split an epic | Breaks a big feature into small, independently shippable issues, in a sensible order. |
| Prioritize the sprint | Ranks candidate work by impact, effort, and risk against your goal and capacity. |
| Link duplicates | Finds issues that overlap and proposes which one to keep. |
| Status update | Drafts a stakeholder update or release notes from your issues and the conversation. |
| Hand off to the Coder | Passes a scoped piece of build work to the Coder as an issue with a short brief. |

## Integrations

| Integration | Status | Used for |
| --- | --- | --- |
| [GitHub](/docs/integrations/github) | Available now, used by the Coder | Issues and pull requests |
| [Linear](/docs/integrations/linear) | Coming soon | Issues and projects |
| [Jira and Confluence](/docs/integrations/jira-and-confluence) | Coming soon | Tickets and specs |
| [Asana](/docs/integrations/asana) | Coming soon | Tasks and plans |
| [Notion](/docs/integrations/notion) | Coming soon | Specs and notes |
| [Slack](/docs/integrations/slack) | Coming soon | Chatting and sharing updates |
| [Gmail](/docs/integrations/gmail) | Coming soon | Stakeholder update drafts |

## Example goals

- Clean up the backlog before Monday planning.
- Turn a customer request into a ticket the Coder can build.
- Split a big feature into a first release and a follow-up.
- Write the weekly update for investors or the team.

## Prompts for when it opens

```prompt title="Set the week's priorities"
Product owner, our goal this week is [goal]. Rewrite the vague open issues on [repository] with acceptance criteria and rank the backlog against that goal.
```

```prompt title="Triage the backlog"
Product owner, triage the open issues on [repository]. Group them by theme, flag duplicates, and tell me what to close, change, or do first.
```

```prompt title="Clarify a request"
Product owner, a customer asked for [request]. Turn it into clear requirements: the problem, who it is for, scope, what is out of scope, and acceptance criteria. List the open questions.
```

```prompt title="Write an issue"
Product owner, draft an issue for [feature]. Include the goal, the scope, and acceptance criteria. Show it to me before you file anything.
```

```prompt title="Split a big feature"
Product owner, split [epic] into small issues that can each ship alone. Put them in the order we should build them.
```

```prompt title="Plan the sprint"
Product owner, we have capacity for about [number] items this sprint and our goal is [goal]. Rank the candidates by impact, effort, and risk, and suggest what to cut.
```

```prompt title="Hand work to the Coder"
Product owner, hand [issue] to the Coder with a short brief: what to build, how we will know it works, and anything to avoid.
```

```prompt title="Write the weekly update"
Product owner, draft this week's update for [audience] from the issues we closed and the work in progress. Keep it short and honest about risks.
```

## What it never does

> [!IMPORTANT]
> Every write waits for your Approve. The Product owner does not file, change, or close issues, and does not send a stakeholder update, until you say so. Drafts are shown to you first.

It plans and writes. It does not write code: building is the [Coder](/docs/personas/coder)'s job.

---

Source: https://stellarfirm.ai/docs/personas/product-owner