PM-Copilot-by-Product-Faculty

Use this skill when the user asks to "design an A/B test", "how should I test this", "experiment design", "how do I run an experiment", "test this feature", "set up a split test", "how many users do I need", "statistical significance", "how do I know if this test worked", or wants to design a rigorous experiment to test a product hypothesis.

Use this skill when the user asks specifically about "how to monetize AI features", "should AI be a separate tier", "pricing for AI capabilities", "how to charge for AI", "AI add-on vs. bundle", "AI feature pricing strategy", or is adding AI capabilities to an existing product and wants to decide how to monetize them. This is a specialized version of pricing-review focused on AI feature economics.

Use this skill when the user asks about "altitude and horizon framework", "Shreyas Doshi altitude", "working at the right level", "am I too in the weeds", "I'm too tactical", "how do I work at the right altitude", "horizon thinking for PMs", or wants to evaluate whether they're operating at the right level of abstraction for their role and stage.

Use this skill when the user asks to "map assumptions", "identify assumptions", "what are we assuming", "assumption audit", "what could go wrong with this idea", "test our assumptions", "what do we need to validate", "identify our riskiest assumption", or when reviewing an idea or PRD and wants to surface hidden bets before building. Do NOT use this skill for general risk analysis — that is part of the pre-mortem skill.

Use this skill when the user asks about "attitudinal segmentation", "segmenting by attitude", "AI embracer vs skeptic", "how to segment our users beyond demographics", "psychographic segmentation", "behavioral segmentation", "how users feel about AI", or wants to go beyond demographic user segments to understand attitudinal and behavioral differences that affect product and marketing decisions.

Use this skill when the user asks to "tailor this for different audiences", "write this for an exec vs. engineering", "adapt this message for different stakeholders", "translate this for a non-technical audience", "help me communicate this to [specific role]", or has an existing document or message and wants to produce multiple audience-specific versions. This is a rewriting skill — it takes existing content and adapts it, not generates from scratch.

Use this skill when the user asks about "beachhead market", "initial market", "where to start", "narrowing our target market", "first customer segment", "go narrow first", "crossing the chasm strategy", "wedge strategy", "who to focus on first", or wants to identify the specific niche to own before expanding. Also use this skill when the user is unsure which segment to prioritize among several options.

Use this skill when the user asks "how do I become a senior PM", "what does senior PM actually mean", "I want to get promoted to senior", "what's the difference between PM and senior PM", "I've been a PM for 2–3 years and want to grow", "my manager says I need to work more strategically", "I'm stuck at PM level", or wants to understand the specific behaviors and skills that separate a PM from a Senior PM. Do NOT use this skill for VP or CPO-level career questions — use solo-to-cpo for that.

Use this skill when the user asks about "cohort analysis", "retention cohorts", "how to read cohort data", "analyze my retention", "what does my cohort data say", "cohort retention curves", "D7/D30 retention", "how to improve cohort retention", or has cohort data they want to interpret and act on.

Use this skill when the user asks for "competitive analysis", "who are our competitors", "competitive landscape", "how do we compare to X", "competitive positioning", "how do we differentiate", "what's our competitive advantage", "are we differentiated", or wants to understand the competitive context and define how to win against alternatives. Also use this skill when preparing for a board meeting or investor conversation that includes competitive positioning.

Use this skill when the user asks for "competitor battlecards", "battlecard for [competitor]", "how do we beat [competitor]", "how do we handle objections about [competitor]", "competitive win/loss", "sales competitive guide", "how should sales talk about competitors", or needs a structured competitive comparison for sales, customer success, or internal strategy purposes.

Use this skill when the user asks to "synthesize interview notes", "analyze my user interviews", "what patterns are in my interviews", "help me with continuous discovery", "find the themes in these interviews", "what did I learn from these calls", "turn these interview notes into opportunities", or pastes or shares raw interview transcripts or notes from user conversations. This skill focuses on the interview synthesis step of continuous discovery, not general feedback analysis — use feedback-triage for support tickets or NPS data.

Use this skill when the user asks to "design a metrics dashboard", "what should be on my PM dashboard", "structure our analytics dashboard", "what metrics to track", "what should I put on a product dashboard", "build a metrics framework", or wants to design a coherent set of metrics and dashboard layout that drives good product decisions without creating information overload.

Use this skill when the user asks to "write an engineering brief", "brief the engineering team", "write a technical spec handoff", "summarize this PRD for engineers", "engineering kickoff doc", "write a spec for the dev team", "help me communicate this feature to engineering", or needs to translate a product decision or PRD into an engineering-ready communication that gives engineers the context to make good technical decisions.

Use this skill when the user asks to "break this initiative into epics", "structure this as epics", "how should I organize this work", "help me sequence this initiative", "epic planning", "what are the phases of this project", "initiative breakdown", or has a large initiative and wants to decompose it into manageable, ship-able phases with clear sequencing.

Use this skill when the user asks to "analyze AI errors", "error analysis for our AI feature", "open coding", "axial coding", "analyze model failures", "categorize AI mistakes", "find patterns in bad AI outputs", "what's wrong with our AI", or has a set of bad AI outputs and wants to understand what's failing and why. This is the first step in the AI eval methodology from Hamel Husain and Shreya Shankar.

Use this skill when the user asks to "design an eval suite", "build evals for my AI feature", "create an evaluation framework", "how do I evaluate my AI", "what evals should I run", "build an eval system", or wants to create a systematic evaluation framework for an AI-powered product feature. Typically run after error-analysis has identified the failure categories to prioritize.

Use this skill when the user asks to "write an exec summary", "summarize this for leadership", "write a summary for the CEO", "board update summary", "executive brief", "leadership update", "write this for C-level", or needs to communicate a complex situation, decision, or initiative status to senior leadership in a concise, structured format. Do NOT use this skill for full stakeholder updates with multiple audience versions — use stakeholder/audience-tailoring for that.

Use this skill when the user asks to "triage feedback", "analyze support tickets", "cluster feedback", "analyze NPS responses", "what are users complaining about", "find pain points in this feedback", "synthesize this customer feedback", or pastes a batch of raw feedback, tickets, or interview notes. This skill is for structured feedback triage and scoring. For interview-specific synthesis, use discovery/continuous-interview-synthesis. For full research synthesis with OST mapping, use /synthesize-research.

Use this skill when the user has a Figma design and wants to turn it into a working prototype, asks "how do I turn my Figma into a prototype", "Figma to code", "take this design and make it interactive", or wants to use AI coding tools to implement a design that already exists in Figma.

Use this skill when the user says "I'm the first PM", "founding PM", "I joined a startup as the only PM", "how do I set up PM processes from scratch", "no PM infrastructure exists", "I'm building the PM function", "what should a first PM do in 90 days", or is navigating the unique challenges of being an early-stage PM with no existing product management structure. Do NOT use this skill for general career progression — use solo-to-cpo for that.

Use this skill when the user asks to "analyze my funnel", "where are users dropping off", "funnel analysis", "conversion analysis", "activation funnel", "onboarding funnel", "purchase funnel", "what's my conversion rate", or has funnel data showing step-by-step drop-off rates and wants to diagnose where to focus.

Use this skill when the user speaks informally about their product work — voice-to-text style updates, venting about a stakeholder conversation, sharing what happened in a meeting, or saying things like "you won't believe what just happened", "quick update", "just got off a call", "heads up", "FYI", "thought you should know", or any unstructured narrative about work events. Also use when the user shares something that sounds like product context but without a clear request. Do NOT use this skill when the user is asking a specific PM question or requesting a deliverable — use the appropriate skill for that instead.

Use this skill when the user asks about "growth loops", "viral loops", "product-led growth", "PLG", "how does our product grow itself", "referral mechanics", "word of mouth", "how to build growth into the product", "organic growth", or wants to identify and design the mechanisms through which the product acquires more users through its own usage.

Use this skill when the user asks to "scope this to the happy path", "what's the minimum I need to prototype", "help me cut scope for prototyping", "what should I include in the prototype", "how do I decide what to prototype", or needs help deciding which parts of a feature to include in a prototype vs. which to defer. Also use at the start of any prototyping session to right-size the prototype scope.

Use this skill when the user asks to "design a human evaluation", "human eval process", "annotation guidelines", "how to set up human review of AI outputs", "how to get humans to evaluate AI quality", "build a labeling process", "create annotation criteria", or wants to set up a structured process for humans to evaluate AI output quality.

Use this skill when the user asks to "define our ICP", "ideal customer profile", "who is our best customer", "who should we target", "which customers should we focus on", "who buys fastest", "who gets the most value", "find our ICP", or wants to identify the specific type of customer most likely to buy, succeed, and expand.

Use this skill when the user asks about "continuous improvement for AI", "AI quality flywheel", "how do we keep improving our AI feature", "closing the eval feedback loop", "systematic AI improvement process", or wants to build a repeating process that continuously improves AI product quality over time rather than doing one-off fixes.

Use this skill when the user asks to "create a journey map", "user journey map", "map the user experience", "map the customer journey", "end-to-end user flow", "what does the user experience look like", "map the onboarding journey", or wants to visualize the full sequence of steps a user goes through to accomplish a goal — including touchpoints, emotions, and friction points.

Use this skill when the user asks about "jobs to be done", "JTBD", "what job are users hiring us for", "demand-side thinking", "what progress are users trying to make", "why do users switch to our product", "what are users really trying to accomplish", "forces of progress", "push pull analysis", or wants to understand user motivation beyond surface-level feature requests. Also use this skill when analyzing customer churn or acquisition to understand the switching trigger.

Use this skill when the user asks to "write a launch announcement", "announce this feature", "write a launch email", "product announcement", "release notes", "launch blog post", "feature announcement to customers", "write the Slack announcement for this launch", or is preparing to communicate a new feature or product to users, customers, or the public.

Use this skill when the user asks to "plan a launch", "create a launch plan", "how do I launch this feature", "launch checklist", "go-to-market plan for this feature", "launch timeline", "prepare for launch", or needs a structured plan for taking a feature or product from "ready to ship" to "in users' hands with people knowing about it".

Use this skill when the user asks to "set up LLM as a judge", "write an LLM judge prompt", "automate quality evaluation", "use Claude to evaluate outputs", "build an automated eval", "LLM-based evaluation", or wants to create a scalable automated evaluation system where one LLM grades the outputs of another LLM.

Use this skill when the user asks to "update my PM Copilot memory", "save this to my profile", "remember that", "update my context", "update my product context", "save this decision", "add this to my memory", "track this risk", "mark this risk as resolved", "add a lesson learned", "save these stakeholder notes", or any explicit request to persist information to the memory profile. Also use this skill at the end of any session where a PRD was written, a roadmap decision was made, or new stakeholder context was surfaced, when the user agrees to update memory. Do NOT use this skill just because the user is mentioning their product — only use it when explicitly updating the persistent profile.

Use this skill when the user asks to "write our messaging", "create a messaging framework", "what should our tagline be", "value proposition", "messaging hierarchy", "how do we talk about our product", "craft our positioning statement", "what's our one-liner", or needs to develop the core language that communicates product value to different audiences.

Use this skill when the user asks about "NLX design", "natural language experience", "conversational UX", "how to design an AI interaction", "conversation design", "how the AI should talk to users", "design the conversation flow", "AI UX design", or wants to design the natural language interaction patterns for an AI-powered feature. This is the UX design skill for conversational and AI-first interfaces.

Use this skill when the user asks "which metric should we focus on", "how do I choose between these metrics", "what's the best metric to track", "help me select our primary metric", "our metrics are confusing", "we have too many metrics", or wants to select a primary North Star from a set of competing metrics. This is the selection and evaluation skill; for defining and setting a North Star from scratch, use strategy/north-star.

Use this skill when the user asks about "north star metric", "what should our north star be", "define our north star", "key metric", "one metric that matters", "choosing our success metric", "how do we define success", "our product metric", or wants to select or evaluate a single metric that best represents value delivered. Do NOT use this skill for dashboard design — use metrics/dashboard-structuring for that.

Use this skill when the user asks to "write OKRs", "structure our OKRs", "help with quarterly goals", "OKR review", "are our OKRs good", "how do I write key results", "our objectives and key results", "check our OKRs", or wants to create, review, or improve their OKR structure. Also use this skill when the user's roadmap items don't clearly connect to stated objectives.

Use this skill when the user says "set up PM Copilot", "run onboarding", "I'm new here", "help me get started", "initialize my profile", "set up my context", "configure PM Copilot", or when `memory/user-profile.md` exists but has no content filled in (all fields are still placeholder comments). Also use this skill when the user asks for a "setup wizard" or says they want PM Copilot to know about their product. Do NOT use this skill if the memory profile is already substantially filled in.