konglong87

Use when: 需要创意方案、探索产品方向、发散思维、本质问题分析、产品遇到瓶颈需要突破 Do NOT use when: 需求已明确需要直接执行、已有成熟方案无需创新

Use when: 需要输出PRD/BRD/MRD产品文档、方案文档、商业计划文档、需要文档模板 Do NOT use when: 文档已完备无需生成、仅需口头讨论无需书面输出

Use when: 开始新产品规划、需要系统化收集需求、验证产品想法真伪、用户提到"我想做一个产品" Do NOT use when: 需求已明确且已验证、仅需执行而非调研

Use when: 有新需求需要录入跟踪、需求状态需要变更、需要统一管理需求池、需求数量增多需要结构化 Do NOT use when: 需求极少可直接管理、仅需一次性分析无需持续跟踪

Use when: 需要细化功能实现细节、拆解复杂功能、为开发准备详细任务、功能点需多维度描述 Do NOT use when: 功能已足够简单可直接进入开发、仅需功能列表无需深度拆解

Use when: 需要将需求转化为用户故事、准备敏捷开发任务、进行需求拆分、编写验收标准 Do NOT use when: 需求已可直接进入开发、团队不使用用户故事格式

Use when: 有初步需求清单需要细化细节、需明确需求场景和边界条件、需求描述模糊需要结构化 Do NOT use when: 需求已足够详细可直达开发、仅需快速立项无需深入

Use when: 需要确定第一版产品功能范围、已有需求清单需筛选 MVP 功能、需要确定最小可行产品边界 Do NOT use when: 产品已上线需要完整功能集、仅需梳理需求无需裁剪范围

Use when: 需要设计产品数据指标、规划数据埋点、建立数据监控体系、进行数据分析和趋势预测 Do NOT use when: 数据指标已明确、仅需简单统计无需指标体系

Use when: 需要理解用户体验全链路、发现用户痛点与机会点、优化用户转化流程 Do NOT use when: 用户流程已非常清晰、仅需单一功能分析而非全局体验

Use when: 有多个需求需要排定先后顺序、资源有限需决定先做什么、需求冲突需要客观评分 Do NOT use when: 只有一个需求无需排序、优先级已由上级/业务方明确指定

Use when: 产品上线后需要分析用户增长、制定增长策略、诊断产品健康度、优化AARRR各环节 Do NOT use when: 产品未上线、仅需单一指标分析无需全链路

Use when: 需要分析用户反馈和评论、评估用户满意度、收集产品改进建议、进行情感分析 Do NOT use when: 用户反馈数据极少、仅需收集无需分析

Use when: 迭代结束后需要复盘总结经验教训、改进团队流程、记录改进行动项 Do NOT use when: 迭代尚未结束、团队不需要正式复盘

Use when: 技术方案确定后涉及多部门协作、需要明确协作流程与职责分工、跨团队沟通困难 Do NOT use when: 单一团队独立完成、协作关系已明确无需梳理

Use when: 需要做重大战略决策（自研vs外包vs收购）、投资评估、多方案比较选择 Do NOT use when: 决策已由高层确定、决策影响极小无需系统分析

Product Manager Skills Pack - Full lifecycle support from demand to delivery 让一个产品经理拥有一个产品团队的能力 Use when: Starting a new product, planning features, analyzing market, designing solutions, managing growth, strategic decision

Use when: 需要了解市场格局与竞争态势、收集行业数据、分析竞品优劣势、评估市场机会 Do NOT use when: 市场已有充分内部调研数据、仅需简单规模估算无需深度分析

Use when: 需要进行市场调研数据收集、竞品信息采集、行业舆情监控、合规政策检查 Do NOT use when: 已有完整数据无需补充、仅需内部数据分析无需外部信息

Use when: 需要明确产品定位、设计商业模式、规划盈利方式、制定定价策略、进行盈利预测 Do NOT use when: 产品定位已明确、仅需执行无需重新定位

Use when: 需要制定增长策略、优化增长指标、突破增长瓶颈、设计系统化增长方案 Do NOT use when: 产品仍在验证期未上线、仅需单一渠道优化而非系统方案

Use when: 需要规划产品中长期发展、设定里程碑、对齐团队方向、制定季度/年度计划 Do NOT use when: 短期执行无需长期规划、方向已锁定无需路线图

Use when: 风险管控完成后准备上线发布、需要制定上线检查清单与回滚方案、正式发版流程 Do NOT use when: 上线流程已标准化且由运维自动化执行、仅需简单发布无需检查清单

Use when: 需要分析用户转化漏斗、诊断流失原因、生成优化建议、提升用户转化率 Do NOT use when: 用户转化路径已非常清晰、仅需单一指标监控无需全链路分析

Use when: 需要生成数据报告、收集整理用户反馈、进行数据驱动的分析汇报 Do NOT use when: 数据已由BI系统自动生成、无需人工分析

Use when: 项目进行中出现需求变更、需要评估变更影响范围和风险、记录变更历史 Do NOT use when: 变更极小无需正式评估、变更已有明确决策无需分析

Use when: 需要设计商业模式画布、规划盈利模式、制定定价策略、设计收入模型 Do NOT use when: 商业模式已确定且已验证、仅需简单定价调整而非全面设计

Use when: 管理多个产品线需要组合决策、BCG矩阵分析、产品生命周期评估、资源分配 Do NOT use when: 单一产品无需组合管理、产品线已固定无需调整

Use when: 需要检查super-pm更新、升级到新版本、回退到旧版本 Do NOT use when: 正常使用skill无需版本管理、首次安装而非升级

Use to verify product optimization, make data-driven A/B experiment decisions, and assess the causal impact of feature changes. Avoid when changes are unquantifiable, sample size is insufficient, or strict statistical verification is not needed.

Use when starting any product management task - automatically detects task type and invokes appropriate PM skill using intelligent routing.

This skill is for designing product prototypes, planning interaction flows, determining interface layouts, and facilitating the transition from PRD to visual design.

Use when there is a need to plan iteration content, set iteration schedules, clarify iteration priorities, and implement requirements into the schedule. Do NOT use when iterations have already been planned by the team or do not require systematic management.

Use to interface with the technical team on solutions, evaluate technical feasibility, define architecture, and assess third-party services. Do NOT use if the technical solution is already determined or if only a functional description is needed without technical evaluation.

Use when establishing agile development processes, designing team collaboration, and planning iteration rhythms for a new project. Do not use if your team already has mature agile processes or only needs a project management tool, not process design.

Use for: Risk investigation after technical solution completion, pre-launch risk identification and assessment, and risk control at key project nodes. Do NOT use when: Project risks are minimal and controllable, or a complete risk management mechanism already exists.

Use when it's necessary to allocate R&D resources across multiple products, conduct ROI evaluation, resolve resource conflicts, and for team planning. Do NOT use when resources are abundant and prioritization is not needed, or for a single product without the need for multi-project coordination.

管理项目经验知识的沉淀与读取，实现知识闭环

Use when facing complex problems requiring innovative solutions, when conventional approaches fail, when breaking down assumptions, or when user asks to 'think from first principles', 'get to the root', 'fundamentally rethink', 'what's the essence', 'strip away assumptions'.

Use when implementing domain logic, designing aggregates, entities, value objects, repositories, domain services, domain model design, ensuring data consistency, or when user mentions 'aggregate design', 'aggregate root', 'entity vs value object', 'domain event', 'repository pattern', 'domain service', 'data consistency', 'invariant protection', 'domain model', 'business rules', 'consistency bound

Use when executing iterative tasks, continuous improvement, quality assurance, process optimization, or when user asks to 'apply PDCA', 'iterate and improve', 'continuous improvement cycle', 'plan-do-check-act'.

MUST use for ANY user request. This is a rigid requirement that applies to all tasks and conversations.

微信公众号文章写作和排版助手。输入主题+内容大纲→自动生成结构完整、排版精美的公众号文章（WeChat兼容HTML+行内样式），同时可配套调用infographic-generator生成4主题配图。触发词：'公众号文章','写公众号','公众号排版','微信文章','推文'。

Use when starting new projects, designing system architecture, identifying bounded contexts, mapping context relationships, system refactoring, system redesign, or when user mentions 'DDD', 'domain-driven design', 'bounded context', 'context mapping', 'microservices design', 'business modeling', 'system boundaries', 'domain thinking', '领域思维', '领域驱动', '重构项目', '重构系统', '重新设计系统', '优化重构系统'.

Intelligent skill router for methodology-skills. Analyzes user request and recommends the best methodology sequence. Use when user asks 'which skill should I use', 'help me choose a methodology', or when starting complex tasks.

MUST use after prompt-enhancer. Create implementation plan with MECE decomposition, dependency analysis, risk assessment, and mandatory plan-review.

Use when user needs 公众号配图 or wants to generate rich HTML pages with multi-theme screenshots. Triggers: '生成配图', '公众号配图', '帮我做配图', '生成截图', '生成信息图', 'infographic', or when user provides a writing topic + content/outline for visual article images.

Use when user requests complex systems involving multiple modules or subsystems - like "build a XX system", "design XX architecture", or "implement XX with multiple features". Triggers to prevent over-engineering before validating core assumptions.