Agent skill

Product Playbook

by ReJeCtAll in ReJeCtAll/ExpertTeam-Codex

产品战略团队完整手册。覆盖需求文档撰写、路线图管理、竞品分析、用户研究综合、指标评审、Sprint规划、干系人沟通和产品头脑风暴全流程。当涉及任何产品管理相关的请求时自动触发。

MITAuto-check passedProduct & Project Management

Install Product Playbook

skills CLI
$ npx skills add ReJeCtAll/ExpertTeam-Codex --skill product-playbook -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ReJeCtAll/ExpertTeam-Codex product-playbook --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ReJeCtAll/ExpertTeam-Codex.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/product-playbook .claude/skills/product-playbook && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
product-playbook
GitHub stars
113
Used in
1 other repo
Token cost
~998 tokens
SKILL.md length
205 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

产品战略团队完整手册。覆盖需求文档撰写、路线图管理、竞品分析、用户研究综合、指标评审、Sprint规划、干系人沟通和产品头脑风暴全流程。当涉及任何产品管理相关的请求时自动触发。

  • Works in 8 steps: 需求文档 (Write Spec) → 路线图更新 (Roadmap Update) → 竞品简报 (Competitive Brief) → …
  • Product & Project Management work in your project
  • SKILL.md covers 1. 需求文档 (Write Spec), 2. 路线图更新 (Roadmap Update), 3. 竞品简报 (Competitive Brief) and 4. 用户研究综合 (Synthesize Research), plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Product Playbook is an agent skill from ReJeCtAll/ExpertTeam-Codex. 产品战略团队完整手册。覆盖需求文档撰写、路线图管理、竞品分析、用户研究综合、指标评审、Sprint规划、干系人沟通和产品头脑风暴全流程。当涉及任何产品管理相关的请求时自动触发。

Its SKILL.md is about 1000 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management. The repository describes itself as: 一套可直接安装到 ~/.codex 的专家配置,面向 Codex CLI / Codex App 桌面版的 Skill 调用方式 提供 3 个专家团、3 个单专家与 1 个总路由入口。 The licence is MIT.

When your agent uses it

  • Product & Project Management work in your project

Example prompts

  • “/product-playbook”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. 需求文档 (Write Spec)
  2. 路线图更新 (Roadmap Update)
  3. 竞品简报 (Competitive Brief)
  4. 用户研究综合 (Synthesize Research)
  5. 指标评审 (Metrics Review)
  6. Sprint 规划 (Sprint Planning)
  7. 干系人更新 (Stakeholder Update)
  8. 产品头脑风暴 (Product Brainstorming)

What it can do on your machine

Read from SKILL.md and the folder at commit 59c573b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Product Playbook loads about 998 tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 205 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~26
When it runs · the whole SKILL.md, loaded when a task matches
~998

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ReJeCtAll/ExpertTeam-Codex at commit 59c573b, republished under its MIT licence (© ReJeCtAll). 205 words, ~998 tokens.

Download SKILL.mdSave it as .claude/skills/product-playbook/SKILL.md (or your agent's skills folder).
name
product-playbook
description
产品战略团队完整手册。覆盖需求文档撰写、路线图管理、竞品分析、用户研究综合、指标评审、Sprint规划、干系人沟通和产品头脑风暴全流程。当涉及任何产品管理相关的请求时自动触发。

产品战略团队手册 (Product Playbook)

本手册覆盖产品战略团队的全部 8 项核心能力。主理人根据用户需求自动选择合适的工作流。


1. 需求文档 (Write Spec)

撰写清晰、可执行的功能规格说明文档(PRD)。

触发词: 写需求文档、PRD、功能规格、Feature Spec

工作流程
  1. 理解需求 — 问题是什么?谁的问题?MVP 还是全功能?约束和时间线?成功标准?
  2. 撰写规格 — 按模板输出
输出模板
markdown
# 功能规格: [功能名称]

**状态:** 草稿 | 评审中 | 已批准 | **作者:** [PM] | **日期:** [Date]

## 问题陈述
[我们在解决什么问题,为什么现在要做]

## 目标和非目标
### 目标
- [具体的、可衡量的目标]
### 非目标
- [明确我们不做什么]

## 用户故事
作为 [角色],我希望 [能力],以便 [收益]

## 方案设计
[详细方案 + 用户流程步骤 + 边界/错误场景处理]

## 技术考量
[API 变更、数据模型、性能影响、迁移计划]

## 成功指标
| 指标 | 当前 | 目标 | 评估时间 |
|------|------|------|---------|

## 验收标准
- Given [前置条件] → When [用户行为] → Then [预期结果]

## 里程碑 → 开放问题
范围管理
  • 每个规格写明确的非目标
  • 新增范围必须伴随砍掉某项或延期
  • 明确分离 v1 和 v2
  • 一个紧凑、定义清晰的规格好过一个宏大模糊的

2. 路线图更新 (Roadmap Update)

维护和更新产品路线图。

触发词: 路线图、Roadmap、优先级排序、季度规划

优先级评估框架
因素权重评估方式
用户影响30%影响多少用户?痛点有多严重?
业务价值25%对收入/留存/获客的贡献
战略对齐20%与公司战略方向的匹配度
工程成本15%开发工作量和复杂度
依赖风险10%技术和业务依赖
输出模板
markdown
## 产品路线图 — [季度/年份]
### 🎯 本季度主题: [概述]

### Now(当前在做)
| 功能 | 状态 | 负责人 | 预计完成 |
|------|------|--------|---------|
| [名称] | 🟢/🟡/🔴 | [团队] | [日期] |

### Next(下一个做)
| 功能 | 优先级 | 依赖 | 预估工作量 |

### Later(后续规划)
| 功能 | 原因 | 触发条件 |

### 变更日志
- [日期]: [什么变了,为什么]

原则: Now/Next/Later 比精确日期更诚实;每次更新都记录变更原因。


3. 竞品简报 (Competitive Brief)

创建竞品分析简报,服务于产品策略决策。

触发词: 竞品分析、竞品对比、竞争情报

工作流程
  1. 确定范围 — 分析哪些竞品?焦点?服务于什么决策?
  2. 调研 — 产品页、定价、发布日志、G2 评价、招聘信息、社交媒体
  3. 生成简报
输出要素
  • 竞品概览: 公司概要 + 产品定位 + 近期动态
  • 功能对比矩阵: ✅ 完整 | ⚠️ 部分 | ❌ 无 | 🚧 开发中
  • 优劣势分析: 每个竞品的 SWOT
  • 定位分析: 目标客户 + 品类宣称 + 差异化点 + 价值主张
  • 行动建议: 差异化优势 / 功能对标 / 监控点

原则: 聚焦可执行洞察而非学术研究;注明信息新鲜度和可靠性。


4. 用户研究综合 (Synthesize Research)

从多个研究来源中提取模式和可执行洞察。

触发词: 用户研究、访谈总结、调研分析、用户反馈综合

输入类型

用户访谈笔记、调查结果、可用性测试、NPS/CSAT、支持工单趋势、产品分析数据

分析方法
  • 主题提取: 编码 → 分组 → 频率统计
  • 洞察层次: 观察(看到什么)→ 洞察(意味什么)→ 建议(做什么)
  • 区分"说的"(态度)和"做的"(行为)
输出模板
markdown
## 用户研究综合报告: [主题]
**样本量:** [X] | **方法:** [访谈/调查/测试] | **日期:** [范围]

### 核心发现
1. **[发现]** (提及 X 次) — 观察 → 洞察 → 建议

### 用户细分
| 细分 | 特征 | 核心需求 | 痛点 |

### 优先级矩阵
| 需求 | 频率 | 严重程度 | 建议优先级 |

### 引述亮点 + 方法论说明

原则: 少量定性数据不能推广为"所有用户都...";矛盾的发现标出来而非忽略。


5. 指标评审 (Metrics Review)

审查产品指标表现,识别趋势和异常。

触发词: 指标分析、数据评审、指标下降、产品健康度

常用指标框架

AARRR(海盗指标): 获取 → 激活 → 留存 → 收入 → 推荐

北极星指标: 一个最能代表产品核心价值的指标

输出模板
markdown
## 指标评审 — [时间范围]

### 核心指标仪表盘
| 指标 | 本期 | 上期 | 环比 | 目标 | 状态 |
|------|------|------|------|------|------|
| [指标] | [值] | [值] | [±X%] | [目标] | 🟢/🟡/🔴 |

### 异常和洞察
- 🔴 [指标] 下降 [X%] — 可能原因: [分析]
- 🟢 [指标] 上升 [X%] — 归因: [分析]

### 细分分析 → 建议行动

6. Sprint 规划 (Sprint Planning)

规划迭代内容,拆分需求为可交付的用户故事。

触发词: Sprint 规划、迭代计划、需求拆分、故事拆分

输出模板
markdown
## Sprint [X] 计划 — [日期范围]

### Sprint 目标: [概述]
### 容量: 总 [X] 点 / 计划 [Y] 点 ([Z]%) / 缓冲 [保留比例]

### 故事列表
| ID | 用户故事 | 验收标准 | 估算 | 负责人 | 优先级 |
|----|---------|---------|------|--------|--------|

### 依赖和风险
| 依赖 | 影响的故事 | 缓解措施 |

### 溢出候选
[如果提前完成可以额外做的故事]

原则: 每个故事独立可交付 + 清晰验收标准 + Fibonacci 估算。


7. 干系人更新 (Stakeholder Update)

撰写清晰、针对受众的项目状态更新。

触发词: 周报、月报、项目进展、干系人沟通

输出模板
markdown
## 项目状态更新 — [日期]

### TL;DR
[1-2 句关键信息 — 忙碌的高管只看这个]

### 进展 🟢
- [里程碑/成果,附数据]

### 风险和阻塞 🟡/🔴
| 风险 | 影响 | 缓解方案 | 需要的帮助 |

### 下一步 + 指标仪表盘

四原则: 先说结论 / 量化一切 / 明确说需要什么 / 针对受众调整。


8. 产品头脑风暴 (Product Brainstorming)

结构化的创意发散和收敛流程。

触发词: 头脑风暴、创意发散、方案探索、产品创意

三阶段流程

Phase 1 发散: 约束移除 → 类比思维 → 极端用户 → 反转思维

Phase 2 收敛:

创意用户影响实施难度差异化总分

Phase 3 深化: 对 Top 2-3 创意 → 核心用户故事 + 方案草图 + 关键假设 + MVP 定义

输出模板
markdown
## 头脑风暴: [主题]
### 问题空间: [探索什么,为什么]
### 创意清单 (编号 + 一句话 + 用户价值 + 风险)
### Top 3 深度展开
### 下一步: 需要验证的假设 / 需要做的原型

© ReJeCtAll, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .codex/skills/product-playbook of ReJeCtAll/ExpertTeam-Codex.

Open the folder on GitHubat commit 59c573b

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in ReJeCtAll/ExpertTeam-Codex, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Product Playbook next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Product Playbook compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Product Playbook this skillReJeCtAll/ExpertTeam-Codex1131 repos~998Automated safety check: PassMIT
User Story Writerdeanpeters/Product-Manager-Skills7.2k2 repos~2.9kAutomated safety check: PassCustom licence
Game Changing FeaturesopenstatusHQ/data-table-filters2.3k3 repos~2.1kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Convex Create Componentspokvulcan/poker-planning1158 repos~2.6kAutomated safety check: PassMIT
Self Improving Agentfarm-fe/farm5.6k2 repos~3.3kAutomated safety check: NotesMIT

Similar skills

  • User Story Writer

    deanpeters/Product-Manager-Skills

    Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.

    7.2k GitHub starsUsed in 2 repos~2.9k tokens
    Product & Project ManagementAuto-check passed
  • Game Changing Features

    openstatusHQ/data-table-filters

    Find 10x product opportunities and high-leverage improvements.

    2.3k GitHub starsUsed in 3 repos~2.1k tokens
    Product & Project ManagementAuto-check passed
  • Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed
  • Convex Create Component

    spokvulcan/poker-planning

    Builds reusable Convex components with isolated tables and app-facing APIs.

    115 GitHub starsUsed in 8 repos~2.6k tokens
    Product & Project ManagementAuto-check passed
  • A universal self-improving agent that learns from ALL skill experiences.

    5.6k GitHub starsUsed in 2 repos~3.3k tokens
    Product & Project ManagementAuto-check: notes
  • Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.

    136k GitHub stars~2.4k tokensUpdated today
    Product & Project ManagementAuto-check passed

More from ReJeCtAll/ExpertTeam-Codex

All 12 skills in this repo
  • Expert Database

    ReJeCtAll/ExpertTeam-Codex

    数据库优化专家入口。用于 Codex CLI 的 $expert-database 调用. An agent skill from ReJeCtAll/ExpertTeam-Codex.

    113 GitHub stars~692 tokensUpdated 3 mo ago
    Auto-check passed
  • Expert Design

    ReJeCtAll/ExpertTeam-Codex

    设计原型专家团入口。用于 Codex CLI 的 $expert-design 调用. An agent skill from ReJeCtAll/ExpertTeam-Codex.

    113 GitHub stars~441 tokensUpdated 3 mo ago
    Auto-check passed
  • Expert Ops

    ReJeCtAll/ExpertTeam-Codex

    基础设施运维专家入口。用于 Codex CLI 的 $expert-ops 调用. An agent skill from ReJeCtAll/ExpertTeam-Codex.

    113 GitHub stars~625 tokensUpdated 3 mo ago
    Auto-check passed
  • Expert Product

    ReJeCtAll/ExpertTeam-Codex

    产品战略团队专家团入口。用于 Codex CLI 的 $expert-product 调用. An agent skill from ReJeCtAll/ExpertTeam-Codex.

    113 GitHub stars~430 tokensUpdated 3 mo ago
    Auto-check passed
  • Expert Security

    ReJeCtAll/ExpertTeam-Codex

    安全专家入口。用于 Codex CLI 的 $expert-security 调用. An agent skill from ReJeCtAll/ExpertTeam-Codex.

    113 GitHub stars~780 tokensUpdated 3 mo ago
    Auto-check passed
  • Expert Software

    ReJeCtAll/ExpertTeam-Codex

    软件开发团队专家团入口。用于 Codex CLI 的 $expert-software 调用. An agent skill from ReJeCtAll/ExpertTeam-Codex.

    113 GitHub stars~467 tokensUpdated 3 mo ago
    Auto-check passed

Questions about Product Playbook

What does Product Playbook do?

产品战略团队完整手册。覆盖需求文档撰写、路线图管理、竞品分析、用户研究综合、指标评审、Sprint规划、干系人沟通和产品头脑风暴全流程。当涉及任何产品管理相关的请求时自动触发。. Product Playbook is an agent skill from ReJeCtAll/ExpertTeam-Codex.

When should I use Product Playbook?

Product Playbook fits situations like: product & Project Management work in your project.

How do I install Product Playbook in Claude Code?

Run `npx skills add ReJeCtAll/ExpertTeam-Codex --skill product-playbook -a claude-code`. Or copy the skill folder (.codex/skills/product-playbook in ReJeCtAll/ExpertTeam-Codex) into .claude/skills/product-playbook in your project. Claude Code loads it when a task matches its description.

How do I install Product Playbook in Codex?

Run `npx skills add ReJeCtAll/ExpertTeam-Codex --skill product-playbook -a codex`. Or copy the skill folder (.codex/skills/product-playbook in ReJeCtAll/ExpertTeam-Codex) into .agents/skills/product-playbook in your project. Codex loads it when a task matches its description.

Can I use Product Playbook in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ReJeCtAll/ExpertTeam-Codex --skill product-playbook -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/product-playbook, .gemini/skills/product-playbook, .github/skills/product-playbook and .opencode/skills/product-playbook in your project.

What does Product Playbook need to run?

SKILL.md names no scripts, command-line tools or credentials: Product Playbook is instructions for the agent only.

Does Product Playbook access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Product Playbook safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Product Playbook use?

Product Playbook is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Product Playbook use?

About 998 tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Product Playbook?

Skills that share tags, products or a category with Product Playbook: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Game Changing Features (openstatusHQ/data-table-filters, 2.3k stars), CCPM Project Management (automazeio/ccpm, 8.4k stars) and Convex Create Component (spokvulcan/poker-planning, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Product Playbook?

ReJeCtAll (a GitHub user) maintains it in ReJeCtAll/ExpertTeam-Codex, which has 113 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on July 8, 2026.

Source: ReJeCtAll/ExpertTeam-Codex on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.