Skip to content

Google Analytics, Vercel Web Analytics, Leadsy, the Ship or Die traffic check, the TikTok Pixel, the OpenAI Ads Measurement Pixel and Behavly stay off until you accept. The help chat starts once you have chosen. The scheduling button starts once you have chosen. Read our Privacy Policy.

StellarFirmStellarFirm
Mission manual
Esc

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

Module 03 · AI Agent Assistants

Product owner

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

Last updated

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 does#

  • 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.
  • Bring evidence to priorities: customer conversations from Intercom, product analytics from Mixpanel, and boards from monday.com.
  • Hand scoped work to the Coder.
  • Check domain names for a launch and register the one you pick, after your Approve. Pointing it at your site goes to the Coder.

Skills#

SkillWhat it does, 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.
Customer evidenceGathers what customers say in Intercom and what they do in Mixpanel about an item, and says how strong the evidence is.

More skills arrive from StellarFirm's skill library without an app update, such as a one-page PRD, a story map, RICE scoring, a Now, Next, Later roadmap, OKRs, release readiness, and feature adoption checks. The skills above stay available even when the library cannot be reached.

Integrations#

IntegrationUsed for
GitHubIssues and pull requests
LinearIssues and projects
Jira and ConfluenceTickets and specs
AsanaTasks and plans
NotionSpecs and notes
SlackChatting and sharing updates
GmailStakeholder update drafts
IntercomCustomer conversations and feedback
NovuReading notification workflows and subscribers; triggering a workflow waits for your Approve, and deleting and cancelling wait for it too unless you turned on auto-approve for deletions or closing in Settings
MixpanelProduct analytics and experiments
PostHog analyticsTrends, funnels, retention, and experiment results
Firecrawl, Exa, Tavily, Jina AIMarket and competitor research with sources
monday.comBoards and roadmap items
Porkbun, Name.com, Gandi, Namecheap, GoDaddy, CloudflareChecking domain names and registering one

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#

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#

Checkpoint

Anything that reaches other people, closes something, or spends your money waits for your Approve. The Product owner does not close issues, comment on them, send a stakeholder update, or register a domain until you say so. Filing and changing issues you asked for runs on its own. Drafts are shown to you first, and a domain request shows what the registrar charges now and for each renewal year.

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