Stats
Actions
Available In
Tags
Plugin
pm
Product management skills: user stories, story mapping, story splitting, PRD development, contagious (STEPPS), product discovery, OKR planning, hypothesis-driven development, competitive analysis, go-to-market planning, pricing & monetization, stakeholder management, metrics interpretation, feature prioritization, customer research synthesis, roadmap communication, post-launch retrospective, technical feasibility assessment, and pm-strategy-workflow.
What's Inside
Skills22
competitive-analysis
/competitive-analysis
Use when making a product or business decision where knowing the competitive context changes the answer — before a launch, when writing strategy, or when articulating differentiation. Triggers on: "competitor analysis", "competitive landscape", "how do we differentiate", "who are our competitors", "경쟁사 분석", "시장 분석", "차별화 전략". Best for: pre-launch competitive positioning, PRD strategic context, GTM messaging differentiation. Not for: internal tools with no external competitors; user research on what customers want (shows what competitors built, not what users need).
contagious
/contagious
Use when someone wants to make a product, feature, campaign, or idea spread through word-of-mouth or organic sharing. Triggers on: "word of mouth", "virality", "how to make this spread", "shareability", "바이럴", "입소문", "공유되게 하고 싶어", "제품이 퍼지게". Best for: diagnosing why something isn't spreading; engineering shareability into a launch or feature; scoring a campaign against the STEPPS framework. Not for: paid acquisition strategy; SEO or performance marketing; viral coefficient math.
customer-research-synthesis
/customer-research-synthesis
Use when raw qualitative research — interview notes, survey responses, session recordings — needs to become structured insights that drive decisions. Triggers on: "인터뷰 정리", "고객 인터뷰 분석", "리서치 결과 정리", "설문 분석", "VOC 정리", "UX research synthesis", "interview notes analysis", "what did users tell us". Best for: affinity mapping with n= counts; Jobs-to-be-Done extraction; insight cards that feed PRD or prioritization. Not for: quantitative survey stats (use metrics-interpretation); competitive research (use competitive-analysis).
feature-prioritization
/feature-prioritization
Use when there are more things to build than capacity allows and the team needs a defensible, data-backed order. Triggers on: "backlog 정리", "우선순위 정해줘", "P1이 너무 많아", "what to build next", "how do we decide", "backlog grooming", "피처 순위 매겨줘". Best for: scoring a large backlog with RICE or MoSCoW; resolving stakeholder disagreements about priority; trimming scope for a specific cycle. Not for: communicating the roadmap to an audience (use roadmap-communication); setting goals or OKRs (use okr-planning).
go-to-market-planning
/go-to-market-planning
Use when a product or feature is near-complete and the team needs to answer: who do we target first, what do we say, where do we reach them, and how do we know the launch succeeded? Triggers on: "GTM plan", "launch strategy", "출시 전략", "론칭 계획", "how do we launch this", "launch phases", "beachhead segment". Best for: planning a major product or feature launch end-to-end; defining phased rollout (beta → limited → full); aligning sales, marketing, and product on launch narrative. Not for: minor releases needing only a release note; pre-PMF products where broad launch is premature; messaging strategy creation from scratch.
Stats
Version1.1.2
LanguageHTML
Stars1
MaintenanceExcellent
LicenseMIT
Last Commit
Added
Available In
Tags
Categories
