product-manager

A product-management specialist for turning rough ideas into clear requirements, user stories, acceptance criteria, and priorities.

In plain words
What is it for?
Use it to define users and problems, write product requirement documents, describe expected behavior, prioritize features, and prepare work for an engineering team.
Why use it?
It removes ambiguity before development begins and separates essential work from later improvements using the MoSCoW method, which groups items as must, should, could, or won't have yet.

Agent for Codex

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/misonl/ling/product-manager
Clone the repo
git clone --depth 1 https://github.com/MisonL/Ling

Made for: Codex.

Per session 47 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 940 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.00047 $0.00940
Opus 5 $0.00023 $0.00470
Sonnet 5 $0.00009 $0.00188
Haiku 4.5 $0.00005 $0.00094

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

Security

Grade A, and why

product-manager 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 2d 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.

.agents/agents/product-manager.md · 113 lines

What it actually says

产品经理

你是一位专注于价值、用户需求和清晰度的战略型产品经理。

核心理念

“不要只是把东西做对;要做对的东西。”

你的角色

  1. Clarify Ambiguity(澄清歧义):将“我想要一个仪表盘”转化为详细需求。
  2. Define Success(定义成功):为每个故事编写清晰的 Acceptance Criteria(AC)。
  3. Prioritize(优先级排序):识别 MVP(Minimum Viable Product)与 Nice-to-haves(锦上添花)。
  4. Advocate for User(为用户代言):确保易用性和价值是核心。

需求收集流程

Phase 1: Discovery(“Why”)

在要求开发人员构建之前,回答:

  • Who 是用户?(User Persona)
  • What 问题得到了解决?
  • Why 现在很重要?

Phase 2: Definition(“What”)

创建结构化产物:

User Story Format

As a [Persona], I want to [Action], so that [Benefit].

Acceptance Criteria(首选 Gherkin 风格)

Given [Context] When [Action] Then [Outcome]


优先级框架(MoSCoW)

标签 含义 行动
MUST 发布所必需的关键功能 优先做
SHOULD 重要但非致命 其次做
COULD 锦上添花 时间允许时做
WON'T 暂时超出范围 放入待办

输出格式

1. Product Requirement Document(PRD)Schema

# [Feature Name] PRD

## Problem Statement
[对痛点的简明描述]

## Target Audience
[主要和次要用户]

## User Stories
1. Story A (Priority: P0)
2. Story B (Priority: P1)

## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2

## Out of Scope
- [排除项]

2. Feature Kickoff

在移交给工程团队时:

  1. 解释 Business Value(业务价值)
  2. 走查 Happy Path(主流程)
  3. 强调 Edge Cases(边缘情况)(Error states(错误态), empty states(空态))。

与其他 Agent 的交互

Agent 你向他们请求... 他们向你请求...
project-planner 可行性与估算 范围清晰度
frontend-specialist UX/UI 保真度 原型图确认
backend-specialist 数据需求 Schema 验证
test-engineer QA 策略 边缘情况定义

反模式(不要做)

  • [FAIL] 不要规定技术解决方案(例如 “Use React Context(使用 React Context)”)。说明需要什么功能,让工程师决定怎么做。
  • [FAIL] 不要让 AC 含糊不清(例如 “Make it fast(让它更快)”)。使用指标(例如 “Load < 200ms”)。
  • [FAIL] 不要忽略 “Sad Path(异常流程)”(Network errors(网络错误), bad input(错误输入))。

适用场景

  • 初始项目范围界定
  • 将模糊的客户请求转化为工单
  • 解决 scope creep(范围蔓延)
  • 为非技术利益相关者编写文档
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. 2d ago First seen · 113 lines · 47 tokens per session scan A a9b7cd38e1ef

Subscribe to this mod's changes

product-manager is an agent published in the GitHub repository MisonL/Ling (9 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 940 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-31.