pm-distinctive-competence
De la autor
Articulate your organization's Distinctive Competencies the Pragmatic Institute way — the unique abilities to deliver value that are valued, different, and provable. Use when a PM says "what makes us different", "our moat", "unique strengths", "why us", "competitive advantage", or "distinctive competence". Strategy = intersect market problems with what only you can do. Produces a Distinctive Competencies worksheet as a Markdown or Word .docx artifact.
Instalare
npx skills add julianoczkowski/product-manager --skill pm-distinctive-competence -a claude-code
Se instalează în .claude/skills/pm-distinctive-competence/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
Vrei ca agentul să-ți propună skill-uri în timp ce scrii? Vezi cum folosești skill-urile din IDE.
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 77
aiqbench calculează scorul de încredere din semnale publice. Nu este un audit de securitate, așa că citește un skill înainte să-l instalezi.
Skill-uri similare
Cele mai apropiate de acesta prin ce fac și când sunt folosite.
- pm-competitive-landscapejulianoczkowski/product-managerMap the Pragmatic Institute Competitive Landscape — identify competitive AND alternative offerings, assess their strengths and weaknesses, and develop a strategy for winning (knowing when to fight and when to run). Use when a PM says "competitive analysis", "competitors", "battlecard", "how do we win against X", "alternatives", or "where do we play". Includes the Solution Matrix (customer impact vs. depth of investment). Produces a Competitive Landscape analysis and a Solution Matrix as a Markdown or Word .docx artifact.Documente★ 52
- pm-positioningjulianoczkowski/product-managerCreate a Pragmatic Institute Positioning Document — describe a product by the market problems it solves (not features), for one persona in one segment. Use when the PM asks for positioning, messaging, "how do we describe/pitch this", an internal positioning doc, or a positioning statement. Produces a Positioning Document plus a Problem-Oriented Capabilities (POC) worksheet as a Markdown or Word .docx artifact.Documente★ 52
- pm-opportunity-scoringjulianoczkowski/product-managerScore and rank product opportunities objectively with the Pragmatic Institute Opportunity Scoring model — across distinctive competency fit, competitive landscape, investment level, and impact to buyers/users. Use when the PM asks which idea to pursue, "score these opportunities", prioritize projects/bets, or compare options objectively instead of by opinion. Produces an Opportunity Scorecard as a Markdown or Word .docx artifact.Documente★ 52
- pm-market-problemsjulianoczkowski/product-managerRun Pragmatic Institute market discovery and validate real market problems before anything gets built. Use when a PM says "I want to build a feature", "do market research", "talk to customers", "discovery", "validate this idea", "is this problem real", "NIHITO", or "who should I interview". Enforces the outside-in rule: build only for problems that are urgent, pervasive, and that the market will pay to solve. Produces a Market Discovery Document and a Market Problems Table as a Markdown or Word .docx artifact.Documente★ 52
- pm-product-canvasjulianoczkowski/product-managerBuild a Pragmatic Institute Product Canvas / business case to justify investing in an opportunity — the market-driven way. Use when the PM asks to "make the business case", "justify this to leadership", "size the market", "should we buy, build or partner", "what's the ROI", "build a product canvas", or "get buy-in for this idea". Frames the opportunity as Value Proposition, Value Creation and Value Capture, sizes the market, runs the Buy/Build/Partner decision, and ends in a go/no-go recommendation with quantified risk. Produces a Product Canvas / Business Case as a Markdown or Word .docx artifact.Documente★ 52
- pm-requirementsjulianoczkowski/product-managerWrite market-driven, prioritized product requirements (a Market Requirements Document / MRD) the Pragmatic Institute way. Use when the PM asks for "requirements", "an MRD", "what should we build", "prioritize features", "market requirements", or wants development to stop saying "requirements aren't specific enough". Articulates each requirement as a persona's problem, prioritizes with Market Evidence × Impact, and groups them for delivery. Produces a Market Requirements Document as a Markdown or Word .docx artifact.Planificare★ 52
Note și recenzii
—
nicio recenzie
Ai încercat acest skill? Notează-l ca să-i ajuți pe alții. Autentifică-te
Discuție
Intră în discuție. Autentifică-te