Multica Pm Requirement Spec
产品经理需求规范:把 Issue/诉求结构化为带编号 PRD(G-/FR-/BR-/AC-/KPI-/OP-/RISK-)。含知识库背景检索;结构就绪后交 multica-pm-artifact-publish 落地。
Install
npx skills add it235/multica-best-practices --skill multica-pm-requirement-specgit clone --depth 1 https://github.com/it235/multica-best-practices.git /tmp/multica-best-practices
mkdir -p ~/.claude/skills
cp -r /tmp/multica-best-practices/templates/zh_CN/skills/product-manager/multica-pm-requirement-spec ~/.claude/skills/multica-pm-requirement-specPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# PM Requirement Spec(产品经理需求规范 · 内容) ## Purpose 把 Issue、会议结论、零散想法变成**清晰、可评审、可拆任务**的 PRD 内容(只管「写什么」,不管「落到哪个平台」)。 > 与 `multica-pm-artifact-publish` 分工:**本 skill = 需求规范与编号;publish = Confluence / JIRA 创建与更新**。换平台只改 publish,不动本 skill。 ## Platform 协作 | Platform skill | 本 skill 用途 | | --- | --- | | `团队知识库(可选)` | Step 0.5 查术语、历史需求背景(**参考**,不当新 AC) | | `multica-platform-jira` / `multica-platform-confluence` | **不直接调用**;读写由 `multica-pm-artifact-publish` 编排 | 智能体指令见 [`references/agent-instructions.md`](references/agent-instructions.md)。 ## 两阶段(规范 ≠ 提交) | 阶段 | 动作 | 停止点 | | --- | --- | --- | | **A 结构化** | 采集 + KB → 编号 PRD 草稿 | 交付 Markdown/HTML 草稿 + 修订记录 | | **B 提交** | 用户/Leader 确认范围后 → `multica-pm-artifact-publish` | 回传 Confluence + JIRA 链接 | Review 后修订:回到阶段 A 改内容 → 再调 publish **更新**(非重复创建)。详见 publish skill Workflow B。 ## Step 0.5 — 知识库(用法二分) 调用 `团队知识库(可选)` → `kb_ask.py`(禁止 SSH/curl)。 | 信息类型 | 能否写进 PRD | 写哪里 | | --- | --- | --- | | 术语、模块边界、历史背景 | **参考** | 背景/修订记录/OP- 引用 | | 菜单路径、权限名、字段别名(当前需求相关) | **应当使用** | FR-/BR-/AC- 可执行描述 | | 历史规则、他系统口径、当前需求未写的字段 | **禁止当新 FR/AC** | 仅背景;冲突以当前 Issue 为准 | 138 不可用:标注「知识库不可用」,**不阻断**结构化;禁止臆造业务规则。超时停轮见 platform KB SKILL。 ## Process 1. 识别业务目标(G- + KPI-) 2. 用户角色 / 权限 3. 范围(含 / 不含)与非目标 4. 约束(兼容性 / 性能 / 安全 / 时间) 5. 验收标准(AC-,可测试) 6. 歧义 → OP- 待确认清单 7. 依赖与风险(RISK-) ## Requirement Structure 章节基线见 `multica-platform-confluence` 的 `scripts/templates/prd-template.md`: | 章节 | 编号 | | --- | --- | | 一句话定义、背景 | — | | 目标与成功标准 | G- + KPI- | | 用户故事 | U- |
Details
- Skill name
multica-pm-requirement-spec- Repository
- it235/multica-best-practices
- Path
templates/zh_CN/skills/product-manager/multica-pm-requirement-spec/SKILL.md- License
- MIT
- Repo updated
- 4 November 2026
FAQ
What does the Multica Pm Requirement Spec skill do?
产品经理需求规范:把 Issue/诉求结构化为带编号 PRD(G-/FR-/BR-/AC-/KPI-/OP-/RISK-)。含知识库背景检索;结构就绪后交 multica-pm-artifact-publish 落地。
How do I install the Multica Pm Requirement Spec skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add it235/multica-best-practices --skill multica-pm-requirement-spec. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Multica Pm Requirement Spec popular?
It lives in it235/multica-best-practices, which has 279 GitHub stars and 33 forks.
Related skills
Multica Artifact Architect
279it235/multica-best-practices
Land technical design artifacts to the code repo or knowledge platform (default Git repo / Confluence). Used by @Architect to upload technical design for downstream implementation and test consumption. Swappable platform.
Multica Artifact Architect
279it235/multica-best-practices
架构师产物薄编排:校验设计草稿规范,落地时只调 multica-platform-confluence + multica-platform-jira。用于 @Architect 发布设计文档。
Multica Artifact Backend
279it235/multica-best-practices
Land API contract artifacts to the API collaboration platform (default Apifox). Used by @BackendDev to upload API contract for downstream frontend / test consumption. Swappable platform.
Pbi Requirements Gathering
135lukasreese/powerbi-claude-skills
[power-bi] Power BI Requirements Gathering — a structured, conversation-driven skill that captures everything needed before building a Power BI solution. Use this skill EVERY TIME someone is starting a new Power BI project, needs to gather requirements from a client or stakeholder, wants to avoid common project failure points, or is scoping a Power BI engagement. Also trigger when the user mentions 'requirements', 'kickoff', 'scoping', 'what questions should I ask', 'project planning', 'client brief', 'starting a Power BI project', 'discovery session', or 'pre-sales assessment'. Guides Claude
Multica Pm Requirement Spec
279it235/multica-best-practices
Turn an Issue into a clear, actionable engineering task. Used for requirement clarification, scope confirmation, and acceptance-criteria definition.
Orchestrate Project Blueprint
224LiarMTTT/TavernWeave
Turn a vague product, character-card, frontend, or Vibe Coding wish into a bounded total design, first-playable contract, scale-appropriate blueprint, resumable NEXT handoff, and evidence-gated first implementation. Use when the user says 脑暴模式 (including 脑暴模式,Soul 联席), asks to 梳理构思/总设计案/蓝图/子蓝图/第一版, wants one-command project kickoff, wants a project progress board with evidence-based percentages and feedback, or needs to stop a long task from recursively expanding. Also use for 提示词规格/从样例归纳提示词: turn requirements or output examples into a scoped prompt contract with unseen-input checks. It may co
Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.