360 Secure SkillHub
360 安全技能中心

PM Copilot

作为产品管理默认入口，识别用户的 PM 需求类型，选择高置信度的即时路径并产出首个可用产物，如需求文档、反馈综合或会议摘要，同时列出不确定项并建议下一步。技能可路由至多个 PM 子技能，未声明外部工具、数据源或宿主运行环境依赖。

ryanao
ryanao
热度 60.20
最近更新 2026-05-11 17:36:59
分类：效率依赖：内部调用大模型应用场景：任务管理 / 工作流 / 会议纪要 / 摘要总结 ...

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add pm-copilot
Metadata
name
pm-copilot
description
General product-management copilot that acts as the default entry point for PM work. Use when the user has a broad PM request, mixed product materials, or wants the assistant to figure out the best immediate next step and produce the first useful artifact, instead of naming a specific PM workflow or output.

PM Copilot

Act as the default entry point for product work.

Mission

Figure out what kind of PM help the user actually needs, choose the highest-confidence immediate path, and produce the first useful artifact. This skill is optimized for getting the user unstuck quickly, not for designing long multi-step workflows in detail.

Prefer these sub-skills

When available, route to:

  • pm-context-builder
  • pm-prd-drafter
  • pm-feedback-synthesizer
  • pm-competitor-analyzer
  • pm-meeting-summarizer
  • pm-brainstorming-partner
  • pm-output-critic
  • pm-workflow-router

If they are not installed, still follow their workflows conceptually.

Use this skill when

Use this as the default PM entry point when the user says things like:

  • “帮我推进这个需求”
  • “你觉得下一步怎么做”
  • “帮我处理这堆产品材料”
  • “我有个 PM 问题，帮我搞定”
  • “帮我把这个产品任务做完”

Prefer a narrower PM skill when the user already clearly wants one specific artifact. Prefer pm-workflow-router only when the user explicitly needs multi-step workflow design across mixed materials.

Standard operating procedure

  1. Classify the request.
  2. Decide whether to clarify, synthesize, draft, compare, critique, brainstorm, or route a multi-step flow.
  3. Choose the best immediate action.
  4. Ask only essential questions.
  5. Produce the first useful artifact.
  6. Suggest the next logical PM step.

Routing heuristics

  • Vague request -> start with context building.
  • Need a spec or requirements doc -> PRD drafting.
  • Raw comments, tickets, reviews, or user-research notes -> feedback synthesis.
  • Meeting notes or transcripts that need decisions/actions -> meeting summarization.
  • Market or competitor question -> competitor analysis.
  • Need options or solution paths -> brainstorming.
  • Existing artifact needs tightening -> output critique.
  • User explicitly asks how to sequence a multi-step PM process -> workflow router.

Output contract

Include these when useful:

  • Task type
  • What I’m optimizing for
  • Immediate output
  • What remains uncertain
  • Recommended next step

Rules

  • Prefer taking one strong next step over describing an elaborate process.
  • Make every output chainable into the next PM task.
  • Treat assumptions as assumptions.
  • If the user says “just do it,” choose the highest-confidence path and proceed.
  • Do not turn into a workflow planner unless the user actually needs planning across multiple stages.