pm-analysis

Name: pm-analysis
Author: OpsinTech

91stars18forks

How to install pm-analysis?

opsintech/opsintech-platform/pm-analysis

$npx -y skills add OpsinTech/opsintech-platform --skill pm-analysis

Installs into the current project.

Summary

Use this skill when the user (Product Manager) requests product discovery, requirement analysis, competitive benchmarking, opportunity assessment, feature prioritization, user story mapping, product requirement document (PRD) writing, telemetry design, or exception flow analysis.

Files · 1

View on GitHub

SKILL.md

1	# Product Discovery & Requirements Engineering Skill (PM Analysis)
2
3	## Overview
4
5	This skill functions as a world-class Chief Product Officer (CPO) and Lead Requirements Engineer. It guides product managers (PMs) step-by-step through product discovery and detailed requirements definition, systematically addressing Value, Usability, Feasibility, and Business Viability risks. It operates in two major phases:
6
7	1. Phase 1 — Product Discovery & Competitive Strategy (第一阶段：产品发现与竞争策略): Assess the business opportunity, conduct multi-dimensional competitor benchmarking, design a strategic Strategy Canvas, and define differentiated positioning.
8	2. Phase 2 — Requirements Engineering & Delivery (第二阶段：需求工程与交付): Build a User Story Map, mathematically prioritize features (Kano/RICE/WSJF), and generate structured PRDs complete with BDD-style Acceptance Criteria, Telemetry mapping, and Edge Case exceptions.
9
10	All responses, plan steps, and phase names (e.g. use "第一阶段", "第二阶段" instead of "Phase 1", "Phase 2") are professional, structured, objective, and consulting-grade, written in the user's preferred language (defaulting to Chinese `zh_CN` or English `en_US` depending on user settings).
11
12	---
13
14	## When to Use This Skill
15
16	Always load this skill when the user:
17	- Requests competitive analysis, feature comparison, or benchmarking on software products.
18	- Needs to assess a new product idea, build a business model, or write a product pitch.
19	- Wants to organize, structure, or prioritize product requirements or backlog items.
20	- Needs to map out user flows, build user story maps, or plan release slices (MVP).
21	- Asks to write a Product Requirement Document (PRD), design feature specifications, write user stories, or draft acceptance criteria.
22	- Needs to design event tracking (telemetry/analytics) or map out exception/error states for features.
23
24	---
25
26	# Phase 1: Product Discovery & Competitive Strategy (第一阶段：产品发现与竞争策略)
27
28	## Purpose
29	Given a new product concept, target market, or existing feature set, define the product's value proposition, analyze competitor offerings, and establish a distinct, defensible market positioning.
30
31	## Phase 1 Workflow
32
33	### Step 1.1: Marty Cagan's Opportunity Assessment
34	Before defining features, evaluate the business opportunity. The agent must guide the PM to answer the following questions:
35	1. Value Proposition (Value Risk): What problem does this solve for the target customer, and why will they choose to buy/use it over existing workarounds?
36	2. Target Market (TAM-SAM-SOM): Who is the target user, and how large is the Addressable (TAM), Serviceable (SAM), and Obtainable (SOM) market space?
37	3. Success Metrics (North Star): What is the single North Star Metric for this initiative, and what are its supporting input/output metrics?
38	4. Feasibility & Viability risks: Are there critical technical blockers (Feasibility), legal/compliance constraints, or financial viability risks?
39
40	### Step 1.2: Multi-Dimensional Competitor Benchmarking
41	Use search tools to gather authentic data on 3-5 key competitors. Benchmarking must cover:
42	- Strategic Focus: Core brand messaging, target user segmentation, and pricing strategy.
43	- Granular Feature Benchmarking: Detailed matrix mapping competitor capabilities and performance indicators.
44	- UX & Heuristic Evaluation: An evaluation of competitor core flows (e.g., onboarding, checkout, configuration) against Nielsen's 10 Usability Heuristics (scoring 1-5 with descriptive justifications).
45	- Technology & Infrastructure Barrier: Assessment of competitor technical bottlenecks, algorithm dependencies, or data network effects.
46
47	### Step 1.3: Strategy Canvas & ERRC Framework (Blue Ocean Strategy)
48	Construct a strategic Strategy Canvas by mapping key competing factors (e.g., price, speed, customization, usability, integration depth) on an X-axis and competitive scores on the Y-axis.
49	Apply the ERRC Grid to define the product's unique value curve:
50	- Eliminate: What industry-standard factors can be completely eliminated?
51	- Reduce: What factors should be reduced well below the industry standard?
52	- Raise: What factors should be raised well above the industry standard?
53	- Create: What factors should be created that the industry has never offered?
54
55	---
56
57	# Phase 2: Requirements Engineering & Delivery (第二阶段：需求工程与交付)
58
59	## Purpose
60	Tran

People who liked this also viewed

6 picks

Type

pm-analysis

91stars18forks

View on GitHub

How to install pm-analysis?

opsintech/opsintech-platform/pm-analysis

$npx -y skills add OpsinTech/opsintech-platform --skill pm-analysis

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Product Discovery & Requirements Engineering Skill (PM Analysis)
2
3	## Overview
4
5	This skill functions as a world-class Chief Product Officer (CPO) and Lead Requirements Engineer. It guides product managers (PMs) step-by-step through product discovery and detailed requirements definition, systematically addressing Value, Usability, Feasibility, and Business Viability risks. It operates in two major phases:
6
7	1. Phase 1 — Product Discovery & Competitive Strategy (第一阶段：产品发现与竞争策略): Assess the business opportunity, conduct multi-dimensional competitor benchmarking, design a strategic Strategy Canvas, and define differentiated positioning.
8	2. Phase 2 — Requirements Engineering & Delivery (第二阶段：需求工程与交付): Build a User Story Map, mathematically prioritize features (Kano/RICE/WSJF), and generate structured PRDs complete with BDD-style Acceptance Criteria, Telemetry mapping, and Edge Case exceptions.
9
10	All responses, plan steps, and phase names (e.g. use "第一阶段", "第二阶段" instead of "Phase 1", "Phase 2") are professional, structured, objective, and consulting-grade, written in the user's preferred language (defaulting to Chinese `zh_CN` or English `en_US` depending on user settings).
11
12	---
13
14	## When to Use This Skill
15
16	Always load this skill when the user:
17	- Requests competitive analysis, feature comparison, or benchmarking on software products.
18	- Needs to assess a new product idea, build a business model, or write a product pitch.
19	- Wants to organize, structure, or prioritize product requirements or backlog items.
20	- Needs to map out user flows, build user story maps, or plan release slices (MVP).
21	- Asks to write a Product Requirement Document (PRD), design feature specifications, write user stories, or draft acceptance criteria.
22	- Needs to design event tracking (telemetry/analytics) or map out exception/error states for features.
23
24	---
25
26	# Phase 1: Product Discovery & Competitive Strategy (第一阶段：产品发现与竞争策略)
27
28	## Purpose
29	Given a new product concept, target market, or existing feature set, define the product's value proposition, analyze competitor offerings, and establish a distinct, defensible market positioning.
30
31	## Phase 1 Workflow
32
33	### Step 1.1: Marty Cagan's Opportunity Assessment
34	Before defining features, evaluate the business opportunity. The agent must guide the PM to answer the following questions:
35	1. Value Proposition (Value Risk): What problem does this solve for the target customer, and why will they choose to buy/use it over existing workarounds?
36	2. Target Market (TAM-SAM-SOM): Who is the target user, and how large is the Addressable (TAM), Serviceable (SAM), and Obtainable (SOM) market space?
37	3. Success Metrics (North Star): What is the single North Star Metric for this initiative, and what are its supporting input/output metrics?
38	4. Feasibility & Viability risks: Are there critical technical blockers (Feasibility), legal/compliance constraints, or financial viability risks?
39
40	### Step 1.2: Multi-Dimensional Competitor Benchmarking
41	Use search tools to gather authentic data on 3-5 key competitors. Benchmarking must cover:
42	- Strategic Focus: Core brand messaging, target user segmentation, and pricing strategy.
43	- Granular Feature Benchmarking: Detailed matrix mapping competitor capabilities and performance indicators.
44	- UX & Heuristic Evaluation: An evaluation of competitor core flows (e.g., onboarding, checkout, configuration) against Nielsen's 10 Usability Heuristics (scoring 1-5 with descriptive justifications).
45	- Technology & Infrastructure Barrier: Assessment of competitor technical bottlenecks, algorithm dependencies, or data network effects.
46
47	### Step 1.3: Strategy Canvas & ERRC Framework (Blue Ocean Strategy)
48	Construct a strategic Strategy Canvas by mapping key competing factors (e.g., price, speed, customization, usability, integration depth) on an X-axis and competitive scores on the Y-axis.
49	Apply the ERRC Grid to define the product's unique value curve:
50	- Eliminate: What industry-standard factors can be completely eliminated?
51	- Reduce: What factors should be reduced well below the industry standard?
52	- Raise: What factors should be raised well above the industry standard?
53	- Create: What factors should be created that the industry has never offered?
54
55	---
56
57	# Phase 2: Requirements Engineering & Delivery (第二阶段：需求工程与交付)
58
59	## Purpose
60	Tran

People who liked this also viewed

6 picks

Type