Skip to content
StellarFirmStellarFirm
Join waitlist
Mission manual
Esc

Type a word to search every page. Try , or .

Module 03 · Personas

Product owner

Coming soon

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

View as Markdown
On this page

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#

SkillWhat it will do, in plain words
Week goal backlogThe first win. Rewrites vague open issues with acceptance criteria and ranks the backlog against this week's goal.
Triage the backlogReviews open issues, groups them, and suggests what to keep, change, or close.
Clarify requirementsTurns a vague request into a problem, users, scope, non-goals, acceptance criteria, and open questions.
Draft an issueWrites a well-scoped issue or user story with a goal, scope, and acceptance criteria.
Split an epicBreaks a big feature into small, independently shippable issues, in a sensible order.
Prioritize the sprintRanks candidate work by impact, effort, and risk against your goal and capacity.
Link duplicatesFinds issues that overlap and proposes which one to keep.
Status updateDrafts a stakeholder update or release notes from your issues and the conversation.
Hand off to the CoderPasses a scoped piece of build work to the Coder as an issue with a short brief.

Integrations#

IntegrationStatusUsed for
GitHubAvailable now, used by the CoderIssues and pull requests
LinearComing soonIssues and projects
Jira and ConfluenceComing soonTickets and specs
AsanaComing soonTasks and plans
NotionComing soonSpecs and notes
SlackComing soonChatting and sharing updates
GmailComing soonStakeholder 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#

PromptSet 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.
PromptTriage 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.
PromptClarify 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.
PromptWrite 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.
PromptSplit a big feature
Product owner, split [epic] into small issues that can each ship alone. Put them in the order we should build them.
PromptPlan 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.
PromptHand 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.
PromptWrite 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#

It plans and writes. It does not write code: building is the Coder's job.