pm-copilot
From the author
Product-management copilot based on the Pragmatic Institute Framework (Foundations, Focus, Build). Use this as the entry point whenever a product manager wants to work through building a product or feature the market-driven way — e.g. "I want to build a feature", "help me plan this product", "where do I start", "I have an idea for X". It figures out where the PM is in the Pragmatic journey, guides them through the right stages (market research, personas, positioning, strategy, requirements, roadmap, launch), and produces a client-ready artifact (Markdown or Word .docx) at every stage. Also use it to explain the Pragmatic Framework or choose which PM artifact to create.
Install
npx skills add julianoczkowski/product-manager --skill pm-copilot -a claude-code
Installs to .claude/skills/pm-copilot/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 77
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- pm-product-roadmapjulianoczkowski/product-managerBuild a Pragmatic Institute Product Roadmap that communicates vision, direction and priorities over time — a plan, not a commitment. Use when the PM asks for a "roadmap", "product vision", "what's coming", "phases", "themes over time", or wants to align stakeholders on direction (as distinct from a dated release plan). Frames outcomes and market problems over time-frames, not features on dates. Produces a Product Roadmap as a Markdown or Word .docx artifact.Planning★ 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.Documents★ 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.Documents★ 52
- pm-prdjulianoczkowski/product-managerAssemble a full, market-driven Product Requirements Document (PRD) the Pragmatic way — problem-before-solution, evidence-based, persona-first. Use when the PM asks for a PRD, product spec, feature doc, "write the requirements doc", or "put it all together for the team". Pulls in existing personas, positioning, market problems, requirements and use scenarios if present, and gathers anything missing inline. Produces a Product Requirements Document as a Markdown or Word .docx artifact.Planning★ 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.Documents★ 52
- product-managerNickCrew/Claude-CortexUse this skill when writing product requirements documents, prioritizing features, creating user stories, defining acceptance criteria, or setting product metrics. Trigger phrases: 'write a PRD for', 'prioritize this feature backlog', 'write user stories for', 'help me define acceptance criteria', 'what metrics should we track for'. Not for writing code, designing UI mockups, or conducting user research interviews.Design★ 65
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in