staruhub/ClaudeSkills / skills/Geek-skills-product-manager
product-manager
Verified资深产品经理助手,提供 PRD/MRD/BRD 创作与评审、产品策略、留存增长、竞品分析、功能优先级,以及 grill-me-to-doc 逐轮访谈。用户要求“逐个问我”“先把需求问清楚”“grill me”“把想法变成产品文档”时进入 grill-me-to-doc:先读仓库证据,每轮只问一个决策,给推荐答案与理由,记录决策和未决项,支持 resume,产出结构化 PRODUCT-DOC;文档完成且用户批准前硬停止,任何时候都不写实现代码。即使未提“产品”,讨论 App 功能、增长或商业模式也应触发。不用于:单纯代码实现、系统架构深设(用 solution-architect)、需多源引用的市场调研(用 deep-research)、纯营销文案。
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 18.4 KB |
| evals/routing-evals.json | config | 2.1 KB |
| references/GRILL-ME-TO-DOC.md | markdown | 6.0 KB |
| references/PM-BEST-PRACTICES.md | markdown | 16.7 KB |
| references/PRD-TEMPLATE.md | markdown | 11.6 KB |
| references/PRD-WRITING-GUIDE.md | markdown | 13.0 KB |
| references/PRODUCT-DOC-TEMPLATE.md | markdown | 1.6 KB |
| references/REVIEW-CHECKLIST.md | markdown | 12.8 KB |
| schemas/grill-state.schema.json | config | 5.0 KB |
| scripts/validate_grill_session.py | script | 12.3 KB |
references/PRODUCT-DOC-TEMPLATE.md
View on GitHub# PRODUCT-DOC: {product name}
## Document status
- Status: Draft | Approved
- Session ID:
- Approved by user: false
- Evidence as of:
## 1. Problem and desired outcome
State the observable problem, who experiences it, and the desired change.
## 2. Primary users and JTBD
Name the primary user and write the job-to-be-done in context.
## 3. Evidence and assumptions
Separate repository/user evidence from assumptions. Include traceable evidence
paths or source identifiers.
## 4. Scope and non-goals
List the minimum in-scope outcome and explicit exclusions.
## 5. User flow and failure recovery
Describe the happy path, important branches, failure states, retry/recovery, and
what the user sees.
## 6. Requirements
Use stable requirement IDs. Each requirement states inputs, behavior, outputs,
and failure handling. Include non-functional requirements where material.
## 7. Success metrics and guardrails
Define metric, population, window, baseline if known, target, and guardrail.
Label proposed numbers as targets rather than facts.
## 8. Risks and dependencies
Record product, data, safety, privacy, operational, and delivery risks with
mitigation or owner.
## 9. Open questions
Separate blocking from non-blocking questions. An approved document must have no
blocking question.
## 10. Acceptance criteria
Write testable, numbered criteria that cover the main flow and failures.
## Decision log
For each decision include ID, decision, rationale, source, and status.
## Implementation boundary
This document does not authorize implementation. The product-manager skill
stops after the approved document is delivered.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |