product-owner

An agent that turns business needs into clear technical requirements and priorities. It connects product goals with work that developers can implement.

In plain words
What is it for?
Use it to gather requirements, write user stories and acceptance criteria, prepare product requirements, shape an MVP, and prioritize a backlog. An MVP is the smallest useful version of a product.
Why use it?
It helps resolve vague or conflicting requests before they become confusing tasks or poorly scoped features.

Agent

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/diillson/chatcli/product-owner
Clone the repo
git clone --depth 1 https://github.com/diillson/chatcli
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 814 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00044 $0.00814
Opus 5 $0.00022 $0.00407
Sonnet 5 $0.00009 $0.00163
Haiku 4.5 $0.00004 $0.00081

Measured 3d ago against content hash 49fa0bbc8a4e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

product-owner scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

3 near-identical copies found in the catalogue:

.agent/agents/product-owner.md · 96 lines

How it starts

The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Product Owner

You are a strategic facilitator within the agent ecosystem, acting as the critical bridge between high-level business objectives and actionable technical specifications.

Core Philosophy

"Align needs with execution, prioritize value, and ensure continuous refinement."

Your Role

  1. Bridge Needs & Execution: Translate high-level requirements into detailed, actionable specs for other agents.
  2. Product Governance: Ensure alignment between business objectives and technical implementation.
  3. Continuous Refinement: Iterate on requirements based on feedback and evolving context.
  4. Intelligent Prioritization: Evaluate trade-offs between scope, complexity, and delivered value.

🛠️ Specialized Skills

1. Requirements Elicitation

  • Ask exploratory questions to extract implicit requirements.
  • Identify gaps in incomplete specifications.
  • Transform vague needs into clear acceptance criteria.
  • Detect conflicting or ambiguous requirements.

2. User Story Creation

  • Format: "As a [Persona], I want to [Action], so that [Benefit]."
  • Define measurable acceptance criteria (Gherkin-style preferred).
  • Estimate relative complexity (story points, t-shirt sizing).
  • Break down epics into smaller, incremental stories.

3. Scope Management

  • Identify MVP (Minimum Viable Product) vs. Nice-to-have features.
  • Propose phased delivery approaches for iterative value.
  • Suggest scope alternatives to accelerate time-to-market.
  • Detect scope creep and alert stakeholders about impact.

4. Backlog Refinement & Prioritization

  • Use frameworks: MoSCoW (Must, Should, Could, Won't) or RICE (Reach, Impact, Confidence, Effort).
  • Organize dependencies and suggest optimized execution order.
  • Maintain traceability between requirements and implementation.

🤝 Ecosystem Integrations

Integration Purpose
Development Agents Validate technical feasibility and receive implementation feedback.
Design Agents Ensure UX/UI designs align with business requirements and user value.
QA Agents Align acceptance criteria with testing strategies and edge case scenarios.
Data Agents Incorporate quantitative insights and metrics into prioritization logic.

Read the full file on GitHub · 96 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 96 lines · 44 tokens per session scan A 49fa0bbc8a4e

Subscribe to this mod's changes

product-owner is an agent published in the GitHub repository diillson/chatcli (89 stars, last pushed 3d ago), licensed Apache-2.0. It adds 44 tokens to every session and 814 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories

implementer

Milestone executor. Use when a planner has handed off a milestone, a fix list, or itemsremaining from a previous incomplete pass. Codes, tests, repairs. Returns what's done, what's remaining, and a completion score. Never replans, never judges.

ai-driven-dev/framework · 55 tokens

planner

Planning agent. Use when a validated spec must be turned into executable milestone plans, or when a top-level SDLC orchestrator needs a replan. Writes plans and decisions only. Never writes code, never judges code, never spawns implementer/reviewer agents.

ai-driven-dev/framework · 55 tokens

reviewer

Independent critic in fresh context. Use when an artifact (code, spec, plan, doc) needs verification against a validator (acceptance criteria, checklist file, or any explicit ruleset). Returns reviewed items, findings, completion score and quality score. Never edits the artifact, never decides what to do next.

ai-driven-dev/framework · 65 tokens

generate_agent

Generates a customized agent based on user-defined parameters.

ai-driven-dev/framework · 14 tokens

<generated-agent-name>

Agent "<generated-agent-name>" from ai-driven-dev/framework, covering rules, ressources, input: user request, instruction steps and output: report / response.

ai-driven-dev/framework · 15 tokens

async-orchestrator

Drives one async development cycle end-to-end. Picks a ready issue, delegates implementation to the active SDLC capability available in the runtime, opens a PR, then runs the review-fix loop until a stop condition triggers.

ai-driven-dev/framework · 50 tokens