/assumptions
WorkflowChains 3 skills: product-assumptions, risky-assumptions, work-backwards
Browse every skill in AI PM OS — searchable, categorized, with the slash-command to run in Claude Code or Claude Cowork.
These 11 workflows are the highest-leverage way to use PM OS — each chains multiple skills end-to-end. Or pick a category on the left to browse the library.
Chains 3 skills: product-assumptions, risky-assumptions, work-backwards
Chains 1 skill: orchestrate-pm-alignment
Chains 6 skills: causal-tree, two-way-door, decision-journal, mece-tree, structure-problem…
Chains 4 skills: clarification-chain, fermi-decomposition, value-of-information, rule-of-five
Chains 3 skills: hidden-agendas, cialdini, meeting-summary
Chains 4 skills: ost-intake, ost, mece-tree, ost-prioritize
Chains 8 skills: requirements-from-talk, requirements-from-design, requirements-reconcile, use-cases, user-stories…
Chains 5 skills: transcript-cleanup, interview-insights, jtbd-forces, product-hypothesis, experiment-design
Standalone workflow.
Chains 7 skills: power-map, stakeholder-map, stakeholder-risk, comms-plan, meeting-prep…
Chains 5 skills: find-the-strategic-crux, netmba-competitor-analysis, product-strategy, limit-strategy, value-chain
Use when you're preparing a 1:1 and want it to be a real conversation, not a status readout — framed around the one outcome it must produce, with the 2–3 topics that need live discussion prepped. Not for prepping a general meeting (`meeting-prep`), a standalone difficult conversation (`difficult-conversation`), or managing up as an ongoing channel (`manage-the-upward-channel`).
Use when you want to be coached through building a talk yourself, step by step — outline, storyboard, headlines, fill, rehearse — with a story structure underneath. Not for generating the narrative for you (`presentation-narrative`), a slide-by-slide outline (`problem-deck`), or stress-testing a finished deck (`exec-deck`).
Summarizes meeting transcripts into structured conversation summaries. Use when needing to identify actions and details from discussions using nested bullet points.
Creates personalized ADHD motivation plans based on client situations. Use when needing to devise tailored strategies using the Four Cs of ADHD Motivation: Captivate, Create, Compete, and Complete.
Simulates a realistic designer or engineer to help a PM practice handling difficult situations. Use when a PM wants to rehearse a scenario before it happens or replay one that already happened to try a different approach.
Generates user-friendly affordances and signifiers for a given design challenge. Use when tasked with creating innovative design solutions that enhance user experience.
Determines an app's 'aha moment' from user data and app description. Use when analyzing key actions or conditions that lead to user engagement and retention.
Assists a product manager in completing an AI Recommendation Canvas for a specific customer problem and persona. Use when the user needs to evaluate AI product solutions using the Recommendation Canvas Framework.
Use when you want to be tutored on a topic *Socratically* — guided to the answer with questions and hints tailored to your level and prior knowledge, not handed the solution. Not for a structured mastery plan for a skill (`skill-mastery`), a rapid skill-acquisition roadmap (`skill-acquisition`), or PM performance coaching (`coaching`).
Use when a new app needs its design *foundation* set before any screens get built — the one core feature, a grayscale sketch of the main screen, and a deliberately tiny design system. Fires at project kickoff or "where do I start designing this?". Not for full wireframe flows (`wireframe-sketch`), a testable prototype (`clickable-prototype`), or translating a PM spec to design (`pm-to-design`).
Surface, prioritize, and find early signals for the riskiest assumptions in your product strategy — from assumption generation through prioritization to identifying the easiest validation signal. Use when mapping product assumptions, prioritizing risk, or designing validation experiments.
This skill conducts a comprehensive behavioral interview to identify a product manager's blind spots. Use when a PM seeks a thorough behavioral audit across all clusters or wants to know areas they consistently get wrong.
Use when the user wants an ideation session on any topic where the point is to beat the *banal bar* — the obvious ideas anyone would produce — through breadth techniques: association, inversion, adjacent-field transplants. Fires on "brainstorm X with me," "I need non-obvious ideas about Y." Not for product-idea sessions (`product-brainstorm`), constraint-driven ideation (`constrained-ideas`), question generation (`good-question-brainstormer`), or problem reframing (`lateral-thinking`).
Reflects on breadboards by comparing expected behavior against implementation wiring and finding design smells. Use when reviewing or improving breadboards created by the breadboarding skill.
Transform a workflow description into affordance tables showing UI and Code affordances with their wiring. Use to map existing systems or design new ones from shaped parts.
Use when a stakeholder hands over a vague *brief* — "make it modern," "improve the UX," "simplify this" — and the PM needs a concrete problem statement with a metric before any design work starts. Not for interpreting exec feedback on existing work (`exec-feedback`), framing from a session transcript (`problem-framing-canvas`), or pulling a team out of solution mode (`problem-first`).
Determines whether a reported bug merits attention over current or planned work. Use when triaging bug reports to decide if immediate action is required or if the bug can be deferred.
Develops robust and coherent business strategies grounded in strengths, weaknesses, opportunities, and threats. Use when requiring expert strategic thinking to guide questioning, creation, and articulation of a business strategy.
Use when someone shares career thoughts and wants tailored guidance — themes reflected back from their own words, a path direction with trade-offs, positioning help, and one concrete *next step*. Not for writing the résumé itself (`resume`), interview preparation (`pm-interview`), building interview stories (`star-stories`), or a plan to master a specific skill (`skill-mastery`).
Uncovers root causes and explores potential consequences of actions or situations from a question. Use when deeply exploring a question through recursive questioning and forward-thinking analysis.
Analyzes product churn data and exit survey responses to develop a targeted churn-reduction plan. Use when examining user characteristics and reasons for churn to generate insights and propose specific, actionable strategies.
Generates powerful ideas to help a product manager influence others based on Robert Cialdini's seven principles of influence. Use when you need to devise influence strategies for a specific target and goal.
Converts vague 'intangibles' into concrete, observable, quantifiable metrics using the three-link Clarification Chain method. Use when a user says something 'can't be measured', claims a concept is 'too subjective' or 'immeasurable', or needs to define KPIs for abstract goals.
Produces a clickable prototype of a screen for user testing based on image descriptions and app information. Use when needing to create a workable prototype incrementally, starting from basic HTML structure to styled UI elements.
Acts as an executive communication coach to offer message framing options, produce drafts tailored to the user's voice, and propose a mini communication plan. Use when you need to communicate effectively with internal teams or executives.
Use when ideas must fit hard *constraints* — a fixed budget, a project type, a deadline, a one-person team — and the constraints should drive the ideation rather than filter it afterward. Fires on "what can I do with $500," "ideas for X within Y." Not for open-topic ideation (`brainstorm-genius`), product-idea sessions (`product-brainstorm`), or reframing the problem itself (`lateral-thinking`).
Build a grounded product strategy from first principles — from identifying the strategic crux through competitive analysis to a limit-based strategy and value chain map. Use when developing product strategy, identifying the strategic crux, or doing competitive analysis.
Finds, diagnoses, and fixes misalignment in corporate settings. Use when teams are stuck, decisions aren't being made, meetings are dysfunctional, or there's confusion about who has authority.
Creates a detailed empathy map for a specific audience in relation to a given topic, providing insights into the audience's thoughts, feelings, and behaviors. Use when you need to generate deep psychological and behavioral insights about an audience's interaction with a topic.
Use when a severe product outage needs a communication plan — stakeholders ranked by impact, a tailored message per group, a promised update *cadence*, and a post-mortem framework to fill after. Not for a routine communication plan (`comms-plan`), a launch announcement (`press-release`), or mapping stakeholder power and interest (`stakeholder-map`).
Applies Gary Klein's Critical Decision Method (CDM) from Sources of Power to extract tacit knowledge from experts or reflect on your own past decisions. Runs a structured 4-pass cognitive interview that surfaces the invisible perceptual cues, hidden assumptions, and pattern-matching skills experts can't articulate when asked directly. Produces decision requirements, critical cue list, training scenario, and debrief summary. Use when the user wants to understand how an expert makes decisions, debrief a critical incident, build training materials from expert knowledge, conduct a cognitive critique of their own choices, or design systems around expert decision-making.
Generates 12 unique calls to action (CTAs) for a specified product using four proven copywriting strategies. Use when needing to create compelling CTAs that match the feeling, provide actionable next steps, handle objections, and make the offer specific.
Implements DAVCI (Decider, Approver, Veto, Consulted, Informed) to define clear decision rights. Use when aiming to establish structured decision-making protocols with defined roles and responsibilities.
Strip cleverness from product thinking so claims operate at the level of truth rather than clever proxies. Use when the user says "de-clever this", "plain version of this", "is this clever or true?", "audit this for cleverness", or asks for a plain-statement check on a decision, thesis, or insight. Also use proactively when reviewing strategy docs, PRDs, newsletter drafts, decision rationale, or product discussions that lean on framework names ("classic cold-start problem"), coined terms ("engagement debt"), contrarian inversions, aphorisms deployed as trump cards, altitude statements ("own the workflow, not the feature"), meta-escalations ("we're solving the wrong problem"), or speculative second-order chains. Do NOT use for presentation or pitch prep — route that to prep-the-room or manage-the-upward-channel. Source: Shreyas Doshi's "sound less clever" post.
Conducts a structured audit of a product manager's decision-making process. Use when questioning the quality of a decision, seeking to audit its rigor, transparency, and customer-centricity, regardless of the outcome.
Use when a decision is about to be made and needs to go *on the record* — expected outcomes with probabilities, assumptions with base rates, quit conditions, and a review date — so the future review judges the process, not the hindsight. Also /decisions Step 3, taking the causal map and classification as input. Not for auditing a past decision (`decision-audit`) or classifying reversibility (`two-way-door`).
Use when a PM needs a *story-driven* demo script for a prototype or feature — a named protagonist, a scenario with stakes, and a beat-by-beat walkthrough — instead of a feature tour. Fires on "script my demo," "make this demo land," or prep for showing a prototype to stakeholders. Not for the deck around the demo (`presentation-narrative`, `5-step-story-deck`) or for reading the room politically (`prep-the-room`).
Evaluates a product design and provides suggestions for improvement based on context and screenshots. Use when developing a comprehensive analysis to find areas for improvement.
Diagnose a buyer's switch — where they sit on the timeline, which of the four forces blocks them, what move comes next. Use when a deal is stuck, a customer interview needs prep or scoring, a job statement needs writing, a prospect needs disqualifying, or a sales call needs debriefing.
Prepare for a difficult work conversation by following a 5-step framework: Prepare, Listen, Empathize, Clarify, and Solve. Use when you need to produce a one-page prep doc, provide calm opening lines and questions, anticipate reactions with de-escalation responses, and close with clear next steps.
Generates innovative counter-positioning strategies to disrupt an incumbent company or product by breaking assumptions and asking thought-provoking 'what if' questions. Use when needing to devise disruptive strategies for a company or product.
Design balanced solutions for addressing rare but critical user scenarios in product development without overcomplicating the core product experience. Use when you need to analyze an edge case scenario, brainstorm potential solutions, and recommend a balanced approach that addresses the issue while maintaining a streamlined core experience.
Use when a PM wants application *archetypes* instead of a single answer or an internal-architecture call. Three openings: "I want to build X — what's out there?"; "I want to do X — what kind of app is this even?"; "they said it should be a Slack app — is it?". Returns 3 archetypes backed by real GitHub repos and a paragraph the user can paste to an AI builder. Not for an engineering team's internal architecture call (`tech-arch-brief`), bug triage (`solution-flaws`), or translating a decided plan to stakeholders (`tech-to-business`).
Engineer a build in function-space, not problem-space — reframe symptoms, design right-to-left, prototype orthogonally not A/B-style, cut to a kick-ass half, set a wall. Use when a feature request needs reframing, a prototype needs designing, scope needs cutting, a project needs a postmortem, or a build needs scanning for confirmation bias and premature scaling.
Use when you have a deck or investment case and need to stress-test it through the executive's skeptical lens before you present — surfacing the assumptions that must hold, the ways it blows up, the analyses that would settle it, and the questions to expect. Not for building the deck (`problem-deck`, `presentation-narrative`), planning it for an audience (`strategic-deck`), or writing a status update (`status-update`).
Use when an executive drops context-light feedback on existing work — "this feels cluttered," "not strategic enough," "something's off" — and the PM must act without a follow-up meeting on the calendar. Produces competing *interpretations*, a send-ready clarifying message, and a no-regret interim step. Not for a vague incoming brief (`brief-to-problem`) or preparing for the exec meeting itself (`prep-the-room`).
Refines a draft update or deck outline to sharpen the message and narrative, identify vagueness, and provide speaking notes. Use when the user requires a senior exec's perspective on clarity, brevity, and impact in their communication.
Use when you have a hypothesis (or a goal to validate) and need the minimum experiment that could *disprove* it — method, primary metric, minimum detectable effect, sample size, and stop/scale rules. Also /research Step 5, one experiment per product hypothesis. Not for defining the success metric itself (`success-metric`), wiring up the mechanics of an A/B test (`ab-test-setup`), or choosing which assumptions to test (`risky-assumptions`).
Provides expert guidance and analysis in the field of product management, including drafting PRDs, analyzing existing PRDs, or giving general product management advice. Use when requiring expert product strategy development from task-specific inputs.
Improves feature results analysis from a draft to a final report. Use when reviewing and enhancing a Feature Results Writeup (FRW) draft with placeholder metrics.
Use when a PM wants a post-launch learning plan — *checkpoints* after launch, what each one measures, who reviews it, and how findings reach the next iteration's plan. Also fires on "we launched X and never learned anything from it." Not for defining the success metric itself (`success-metric`), designing an experiment (`experiment-design`), or NPS programs (`nps-to-cx-plan`).
Breaks unknown or seemingly immeasurable quantities into estimable components using Fermi decomposition. Use when the user needs to estimate market size, cost, or quantity without direct data.
Guides a PM, product leader, or strategist through a 5-step problem-solving process to find the strategic crux and arrive at a clear recommendation. Use when the user needs to think through a messy or underspecified strategy problem.
Use when a company's successes and disappointments need distilling into a Jim Collins-style *flywheel* — 4–6 components in a self-reinforcing loop that explains why the wins won and the losses lost. Fires on "what's our flywheel" or "why do some bets work for us and others don't." Not for the growth model and its constraint (`growth-strategy`), sequencing items into a loop (`reinforcing-sequence`), or durable moats (`moats`).
Identifies, evaluates, or creates focal points in coordination and negotiation problems using Thomas Schelling's framework from 'The Strategy of Conflict'. A focal point is a solution that people converge on without explicit agreement because it is uniquely prominent, simple, or recognizable. Use when multiple parties need to converge on a single choice without full communication, such as setting a standard, deadline, or meeting point.
Transforms startup struggles into focused action from the founder's situation. Use when guiding a startup founder to focus, develop a common-sense solution, and consider high-intensity execution based on their specific situation.
Use when a multi-step flow (onboarding, checkout, signup, approval) is losing people and you want to cut steps without removing the checkpoints that prevent costly errors — each step tagged, priced against the drop-off it causes, and redesigned. Not for the first-run activation path (`onboarding-redesign`), mapping the whole end-to-end experience (`journey-map`), or retention work (`churn-reduction`).
Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.
Generates user stories with Gherkin acceptance criteria from requirements. Use when tasked with producing INVEST-compliant user stories that align with user personas, goals, and product context, including acceptance criteria and additional notes.
Generates, improves, and ranks high-leverage questions for strategy, product discovery, innovation, writing, decisions, and life planning. Use when the user asks to brainstorm better questions, question storm, find an eigenquestion, reframe a problem, generate product discovery questions, ask sharper why/what-if/how questions, or turn a vague topic into actionable inquiry.
Use when a product's growth needs a strategy built from its actual growth model — how it acquires and keeps users today, the *constraint* currently limiting that loop, where the model runs out, and the methods that attack the constraint. Fires on "how do we grow this" or "growth has stalled." Not for building the flywheel diagram (`flywheel`), reducing churn specifically (`churn-reduction`), or finding the activation moment (`aha-moment`).
Use when someone faces a personal opportunity or commitment and wants to check whether external pressure is overriding their *gut* — capture the instinct, name the pressures, weigh the honest costs, and see if the gut holds. Not for classifying a decision's reversibility (`two-way-door`), the full product-decision workflow (`decisions`), or stress-testing a decision already made (`talk-me-out-of-it`).
Dynamic system tour — reads actual project structure before responding so the tour reflects what is really in the system. Use when the user wants a system tour, asks what PM OS can do, or says '/help' or '/pm-help'.
Identifies potential hidden agendas of stakeholders in a given situation. Use when analyzing possible underlying motivations that may not be immediately apparent.
Embodies the Ideal Customer Profile (ICP) representative for a product. Use when requiring authentic, experience-based feedback on product features and decisions.
Use when a specific KPI number has to survive scrutiny — build the explicit arithmetic model of a feature's impact on named KPIs, every term a sourced or flagged assumption, with sensitivity ranges on the shaky ones. Not for a first rough is-it-worth-building estimate (`impact-sizing`), defining the success metric (`success-metric`), or designing the test that validates the assumptions (`experiment-design`).
Use when you need a top-down estimate of whether a feature is worth building — a funnel from exposed users down to actual adopters, converted into rough engagement and revenue impact, with the riskiest assumptions named. Not for a per-KPI arithmetic model that defends a number to execs (`impact-model`), defining the success metric for a change (`success-metric`), or the full measurement workflow (`/measure`).
Import context from Claude, ChatGPT, or Gemini via paste-back into PM OS Context, user-memory, and project events. Use when the user wants to import context from another AI assistant, paste in a saved memory dump, or says '/import-ai-memory'.
Develops effective strategies leveraging company strengths against industry trends to achieve specific goals. Use when tasked with aligning company competencies with market trends to formulate actionable strategies.
Identifies potential inflection points and converging trends to predict future product opportunities. Use when you need to analyze current developments and forecast future opportunities in the market.
Creates four distinct descriptions of a complex tool interface from a single image. Use when needing to describe the interface for different audiences, including novices, in a process diagram, as a 5th grader, and for an internet-savvy user.
Creates a comprehensive discussion guide for customer interviews based on a given topic to gather insights for feature development. Use when you need to develop an effective customer interview guide for any subject.
Use when one customer interview transcript needs JTBD analysis — the *four forces* (pushes, pulls, habits, anxieties) coded with verbatim quotes, plus the jobs, struggles, and workarounds tagged by type and intensity. Also /research Step 2. Not for coding many interviews into a clusterable dataset (`jtbd-forces`), diagnosing a stuck deal with the forces (`diagnose-the-switch`), or reconstructing a work conversation (`transcript-insights`).
Generates structured interview notes from a transcript using flexible frameworks. Use when needing to analyze an interview transcript and produce concise, informative notes based on specific frameworks like Chronological, Topical, AEIOU, or Empathy Map.
Converts leadership intuition into actionable research plans to validate or refute a feature idea. Use when creating a comprehensive research plan based on leadership's gut feelings.
Use when you have user behavior data and want the end-to-end customer experience mapped as ordered stages — touchpoints, time spent, friction and delight, and the emotional state at each — to find where the experience breaks. Every stage grounded in data; inferred emotions flagged. Not for redesigning one flow's friction (`friction-reduce`), the first-run activation path (`onboarding-redesign`), or an empathy map of a single persona (`create-empathy-maps`).
Transforms interview data into clustered JTBD forces by coding and affinitizing pushes, pulls, habits, and anxieties from user interviews. Use when needing to create a dataset ready for cluster analysis.
Transforms interview transcripts into actionable job stories by identifying underlying problems and presenting them as job stories. Use when analyzing user interview transcripts.
Guides users through the Jobs-to-be-Done Market Definition Canvas to define market opportunities. Use when transitioning from a product-focused view to a problem-space definition for market analysis.
Creates a realistic interview transcript between a product designer and a group of core audience members, exploring the problems and needs of the audience in relation to a specific product type. Use when aiming to create a Jobs to Be Done (JTBD) map of the 4 forces of progress.
Generates creative ways to reframe a given problem and come up with additional options using Edward De Bono's lateral thinking methods from his book 'Serious Creativity'. Use when you need to find novel or non-obvious approaches to problem-solving.
Analyzes a professional's performance in a meeting to enhance their leadership presence and influence. Use when the user needs to improve their respect, senior-level leadership, and organizational influence based on a meeting transcript.
Use when someone wants to design a more satisfying life by finding the *patterns* behind their happiest moments — walk their adult years, capture what genuinely satisfied them, and surface the recurring themes to build more of. Not for career-direction advice from career thoughts (`career-guidance`), tracking motivation over time (`motivation-journal`), or a periodic life review (`monthly-review`).
Applies the Limit-Based Product Thinking framework to a given problem or product idea. Use when needing to envision the ultimate state of a product and work backwards to create a strategic execution plan.
A decision-making framework grounded in Assembly Theory for increasing the likelihood of fortunate outcomes. Use this skill when facing ambiguous choices, formulating experiments, designing strategies, evaluating opportunities, building things meant to persist, or when the user asks about improving their luck, fortune, resilience, or why some ideas, products, or systems thrive while others don't.
Make high-quality product decisions by working through root causes, classifying reversibility, journaling the decision, structuring the problem, synthesizing recommendations, and defining decision rights. Use when making a tradeoff, classifying reversibility, or running a structured decision audit.
Manage what flows upward: commit to a launch date the right way, write the exec update or status note, do the weekly optics block, or contain a pointless process imposed from above. Use when the user says "I need to give a date", "they're asking when it ships", "I have to write the exec update", "I keep putting off status updates", "leadership wants this template filled in", or any deliverable aimed at execs, GTM, or skip-levels. Produces a two-date plan, a finished optics artifact, or a containment setup. Source: Shreyas Doshi corpus + The Prince / 48 Laws of Power.
Transforms a messy problem into a McKinsey-style issue tree (Why / What / How shape, auto-detected) and produces the matching deliverable — testable hypotheses for diagnostic problems, sequenced execution plans for compositional/roadmap problems, or ranked options for solution-search problems. Use when the user has an unstructured business, product, or organizational problem they want to decompose rigorously, says things like "structure this problem", "build me an issue tree", "find the root cause", "what does producing X require", "options for X", "decompose this", "produce a roadmap for", "why is X happening", or "how might we achieve X". Detects tree shape from input and confirms with user. Interactive — interviews when input is thin, processes directly when input is rich.
Turn vague intangibles into quantified decision inputs by chaining clarification, decomposition, value-of-information analysis, and small-sample measurement into a single structured workflow. Use when defining KPIs, deciding what to measure, or designing ROI analysis on intangibles.
Analyzes a list of items using the MECE principle, determining mutual exclusivity and collective exhaustiveness, and creates a logical tree representing the structure. Use when you need to organize list items into a MECE analysis and logical tree.
Helps prepare for an effective meeting by generating a suggested agenda, key questions, purpose statement, and process based on the provided meeting description. Use when you need to create an agenda for a meeting.
Run high-impact meetings — surface hidden agendas before, apply influence principles during, and capture structured summaries after. Use when preparing a meeting agenda, summarizing a meeting, or preparing influence tactics.
Transforms scattered meeting plans into focused stakeholder outcomes. Use when preparing for or deciding whether to have a meeting with cross-functional partners or peers to clarify purpose, politics, and outcomes.
Generates a list of difficult questions that stakeholders might ask during a challenging meeting. Use when preparing for a confrontational and skeptical audience to ensure thorough preparation.
Use when you have a meeting transcript or notes and need a structured, skimmable summary in the *IDEAS* format — Insights, Decisions, Engagements, Actions, Summary — with an owner and a date on every action. Also /meeting Step 3. Not for reconstructing a work conversation's flow and open threads (`transcript-insights`), JTBD analysis of a customer interview (`interview-insights`), or extracting structured requirements (`requirements-from-talk`).
Use when you're stuck in a stale frame on a problem and want a fresh angle by borrowing structure from an unrelated domain — a *metaphor* that transfers a mechanism, not a mood, into concrete moves the literal frame missed. Not for reframing the problem statement directly (`lateral-thinking`), generating idea volume on a topic (`brainstorm-genius`), or structured analysis toward a recommendation (`structure-problem`).
Diagnose why a metric dropped using a rigorous, stepwise decomposition method. Use when you need to confirm if the drop is real, investigate potential causes, and determine next steps based on the data findings.
Provides targeted affirmations and insightful questions to reframe user concerns in an empowering, self-esteem-building way. Use when you need to help users shift their perspective and feel more confident and capable in facing their challenges.
Converts a transcript/spec/conversation into a focused remote Miro workshop that produces a concrete decision or plan within a specified time limit. Use when you need to organize an effective remote workshop from transcripts and specs.
Converts research into actionable strategies that can create a durable competitive moat for an application. Use when the user needs to convert research into durable competitive moats.
Produces comprehensive discussion guides for customer interviews based on a given topic. Use when gathering insights to guide feature development, adhering to principles from 'The Mom Test' and 'Continuous Discovery Habits'.
Helps product managers maintain a motivation journal to track and analyze what truly energizes them. Use when you need to reflect on your motivations and energy levels in your work.
This skill uses Motivational Interviewing techniques to build intrinsic motivation. Use when aiming to resolve ambivalence and strengthen motivation for change through conversation.
Co-creates a Market Requirements Document by eliciting inputs, reasoning transparently, and drafting a crisp, decision-ready document. Use when you need to generate a market requirements document from strategic market inputs.
Review any product document from 7 cross-functional perspectives — Engineering, Design, Executive, Legal, UX Research, Devil's Advocate, and Customer Voice — with framework-grounded feedback and Socratic questioning. Use when reviewing a PRD, strategy doc, roadmap, or design from multiple stakeholder perspectives.
Produces a rigorous competitor analysis using Michael Porter’s four-component model and synthesizes strategic implications. Use when you need in-depth analysis of a competitor's objectives, current strategy, assumptions, and capabilities.
Develops 10 highly specific niche definitions from user input for products or creative endeavors. Use when analyzing user input to create precise market niches.
Analyzes user transcripts to surface needs across three horizons—Now, Next, Later—grounding every claim in evidence from the transcript, creating a vision/roadmap. Use when you need to turn interviews into a structured Now/Next/Later roadmap based on user needs and priorities.
Use when you have NPS scores and open-text feedback and want a prioritized set of CX initiatives — detractor and promoter comments split, themed with honest counts and verbatim quotes, then turned into ranked initiatives. Not for general survey open-text (`survey-to-actions`), defining the metric itself (`success-metric`), or the full measurement workflow (`measure`).
Helps surface the most obvious stakeholder objections before they derail a product, arming product managers with precise counter-moves. Use when you need to anticipate and prepare for stakeholder objections using the MOO approach.
Generates creative and offbeat questions, particularly 'why' questions, about a given topic. These questions are imaginative, thought-provoking, and sometimes humorous, involving unexpected comparisons, absurd scenarios, or playful twists on common concepts. Use when you need to stimulate unconventional thinking or discussions about a specific topic.
Use when a product's onboarding needs redesigning around the user's *transformation* — who they are before, who they become after, and the smallest step that makes them feel the change — with every current step audited as serving the user or serving the product. Fires on "our onboarding leaks users" or "redesign our first-run experience." Not for locating the activation metric (`aha-moment`), mapping the full journey (`journey-map`), or general flow friction (`friction-reduce`).
Map product opportunities systematically — from structured OST intake through opportunity tree construction, optional MECE refinement, to selecting one prioritized target opportunity. Use when mapping product opportunities, building an opportunity solution tree, or selecting initiatives to pursue.
Serves as a PM alignment coach, providing specific, honest, and actionable feedback based on a behavioral framework. Use when you want to reflect on your performance as a PM, get coaching, or understand your blind spots.
Transforms interview data into an Opportunity Solution Tree, organizing it by moments in time with clear parent-child relationships. Use when you have interview transcripts or story snippets and need to structure them into a clear, actionable framework.
This skill facilitates the selection of one target opportunity from an Opportunity Solution Tree. Use when choosing a distinct, solvable opportunity independent of other factors.
This skill functions as an Intake Orchestrator to gather inputs for building a Teresa Torres–style Opportunity Solution Tree (OST). Use when you need to efficiently extract or elicit required variables for OST construction.
Applies Teresa Torres's four-factor framework to compare and rank opportunities on an Opportunity Solution Tree. Use when selecting a target opportunity to explore first from a mapped opportunity space.
Use when a requirements list has everything marked "must-have" and the PM needs it forced into P0/P1/P2 — P0 meaning *launch blocker*, tested, not claimed. Fires on "prioritize these requirements," "what's actually P0 here," or pre-launch scope fights. Not for pricing one incoming scope request (`scope-defense`) or ranking discovery opportunities (`ost-prioritize`).
Use when someone says "competitor X just shipped Y — we need it" and the PM must call it: match, differentiate, leapfrog, or skip. The hinge is whether the feature is *table stakes* — proven by lost deals and churn, not by its existence. Not for a full competitor teardown (`netmba-competitor-analysis`), building moats (`moats`), or counter-positioning strategy (`disruption-what-ifs`).
Analyzes product decisions from the perspective of a specific user persona based on anthropological research. Use when considering how a group relates to a certain topic or product decision.
Decide whether a workplace fight is worth political capital, and if so, design the move. Use when the user says "should I fight this", "should I escalate", "should I push back on this decision", "this process/strategy is broken and I want to fix it", "I want to go over someone's head", "how do I take this on", or is contemplating any deliberate contest: escalation, open disagreement with a decision, a move against a rival or an exec, or a campaign to change something. Produces a GO/NO-GO with capital budget; if GO, a designed move or consolidated strike plan. Source: Shreyas Doshi corpus + The Prince / 48 Laws of Power.
Use when a company's growth options need the Pioneer-Migrator-Settler map — the current *portfolio* placed on it first, the imbalance read, then growth ideas generated to fill the gap. Fires on "are we too red-ocean," "PMS map," or Blue Ocean portfolio reviews. Not for the growth model and its constraint (`growth-strategy`), counter-positioning ideation (`disruption-what-ifs`), or SWOT-derived moves (`swot-moves`).
PM coaching grounded in what designers and engineers actually say about their best product managers. Run situation retrospectives, reveal how your team sees you, stress-test yourself in adversarial roleplay, audit past decisions, and surface the blind spots you can't see from the inside. Use when the user wants to debrief a situation, audit a decision, do an adversarial roleplay, or scan blind spots.
Assists in preparing for PM interviews by generating practice questions, providing answer guidance, and offering a framework for interview preparation. Use when you need to master the PM interview process from resume submission to job offer.
Build a custom agent for the user's harness — decide if it even earns a subagent, then write the agent file, wire its tools/MCP, set its cadence, and drop it in an upgrade-safe home. Use when the user wants to create, author, or scaffold their own agent or subagent, says 'make my own agent', 'build me an agent', or types /agent-builder.
Capture explicit source material or a confirmed PM update into project memory after preview and confirmation. Use when the user wants to save a decision, risk, or PM update to project memory, or says '/capture-memory' or 'remember this'.
Run the opt-in daily context drip loop manually — ask one high-signal question, process the answer, or skip/snooze/stop. Use when the user wants to run the opt-in daily context question loop, answer a pending question, or says '/daily-drip'.
Send feedback to the pm-os creator. Works with or without setup complete. Use when the user wants to send feedback to the pm-os creator, share what's broken, or says '/feedback'.
Search across all Knowledge folders and surface the best matching frameworks for any PM topic. Use when the user wants to find a framework, asks 'what framework should I use', or says '/framework'.
Manage PM OS project folders — create (including nested parent/child), list, switch, activate (multi-active .current), or archive. Use when the user wants to create, list, switch, or archive a PM OS project folder, or says '/project'.
Find and invoke the right PM skill for any task from the 243 skills in PM OS. Use when the user wants to find the right PM skill for a task, browse skills by topic, or says '/skill'.
Onboard the user — fill Context files using web search and structured questions, then deliver a personalised first-workflow recommendation. Use when the user wants to onboard, set up their PM OS Context files, or says '/start'.
Guide the user through sharing a testimonial about pm-os. Four questions, then you write it for them. Use when the user wants to give a testimonial about pm-os or says '/testimonial'.
Route orphaned Work artifacts into project folders and keep Context files in sync with your latest work. Use when the user wants to sync Context with Work, tidy up orphaned artifacts, route files into project folders, or says '/tidy' or 'clean up'.
Upgrade an existing pm-os workspace to a newer version, preserving Context, Work, and customizations. Tool-aware — refuses if the wrong ZIP is downloaded. Use when the user wants to upgrade an existing pm-os workspace to a newer version, or says '/upgrade' or '/pm-upgrade'.
Orient on current PM OS state — read all Context files, scan every active project from .current, build cascading recall packets, surface user-memory, and recommend a next action. Use when the user wants to orient on current state, asks 'where am I', wants a recommended next action, or says '/status' or '/pm-status'.
Translates PM inputs into concrete design requirements and identifies gaps needing clarification. Use when extracting design constraints from product management context.
Creates Geoffrey Moore–style positioning statements from competitive analysis and value proposition. Use when crafting a concise, falsifiable statement prioritizing outcomes over features.
This skill analyzes relationships and influence levels of meeting attendees to provide insights for strategic planning and communication. Use when you need to map power dynamics before a meeting to understand formal hierarchies, informal power indicators, alliances, conflicts, and each attendee's stake in the meeting's outcome.
Develops a transition strategy to move users from low-frequency to high-frequency use cases for a given product. Use when creating a plan to increase user engagement.
Build a complete PRD end-to-end — from raw inputs (transcript, design, research) through use cases, user stories, and acceptance criteria to a drafted PRD reviewed by 9 specialised reviewers (2 PRD-specific personas + 7 cross-functional). Use when you need a full PRD, not just a one-shot draft.
This skill drafts comprehensive PRDs based on product information and assumptions. Use when you have partial product information and need to create a detailed PRD, making informed assumptions where necessary, and ensuring the document is thorough and leaves no room for ambiguity.
This skill generates detailed and comprehensive Product Requirements Documents (PRDs) from industry and feature specifications. Use when you need to create a PRD that leverages industry expertise and includes essential sections like Executive Summary, Problem Statement, and Key Features, ensuring all questions are answered for designers and engineers.
Prep for an upcoming meeting, 1:1, exec review, or hard conversation. Use when the user says "prep me for this meeting", "I'm walking into a conversation with X", "I have a review with my VP in an hour", "how do I pitch this to the team", "help me get ready for this 1:1", or names an upcoming interaction with a stakeholder, exec, engineer, or designer that carries tension or stakes. Produces a read on the actors, a stance, opening moves, and what not to do. Source: Shreyas Doshi org-navigation corpus + The Prince / 48 Laws of Power.
Use when you need the full narrative prose for a persuasive presentation — a three-arc story built from raw material (transcripts, notes, a brief) that ends in a specific buy-in ask. Not for planning the deck for an audience first (`strategic-deck`), a slide-by-slide outline (`problem-deck`), or scripting a product demo (`demo-narrative`).
Creates visionary press releases from product vision using Amazon’s Working Backwards method. Use when needing to produce a credible press release announcing a product launch, ensuring clarity, specificity, and proof are maintained.
Use when you need to turn a problem and a recommendation into a slide-by-slide storyline — question-title slides where each answers the one before, building to the ask (Minto/Pyramid + What/So What/Now What). Not for arranging content you already have (`what-so-what-deck`), writing the narrative prose (`presentation-narrative`), or planning depth and tone for an audience (`strategic-deck`).
Reorients teams from premature solution mode back to rigorous problem definition and user job alignment. Use when a team jumps to solutions without properly defining the problem, to ensure a clear understanding of the user needs and job-to-be-done.
Creates a comprehensive Problem Framing Canvas based on the provided session context to help stakeholders understand the core problem from a user's perspective. Use when analyzing a conversation transcript to frame the problem statement.
Produces a rigorous list of assumptions underlying a product strategy, covering desirability, feasibility, viability, and usability. Use when you have a core problem, product description, and target user information to generate clear, testable, and impact-aware assumptions.
Use when a problem or opportunity area needs *product concepts* — each stated as problem + mechanism + differentiation, with technology nouns banned so the concept can't hide behind a buzzword. Fires on "product ideas for X," "what could we build here." Not for topic ideation (`brainstorm-genius`), ideation inside hard constraints (`constrained-ideas`), or question-driven startup ideation (`startup-ideas`).
Evaluates product designs and provides actionable improvement suggestions based on context and screenshots. Use when assessing UI/UX designs, reviewing mockups, providing design feedback, or evaluating product interfaces against stated goals and metrics.
Formulates structured product hypotheses from product problems. Use when required to create a hypothesis for a product experiment by identifying the experiment goal, drafting a hypothesis statement, checking for specificity, developing a measurement plan, validating and refining, and framing the hypothesis narratively.
Use when product context needs shaping into a structured strategy document through the seven-part template — Objective, Users, *Superpowers*, Vision, Pillars, Impact, Roadmap — where each section must build on the previous ones. Also /strategy Step 1b, taking the crux and competitor analysis as input. Not for diagnosing the strategy problem itself (`strategy-kernel`), backcasting from an end state (`limit-strategy`), or the full strategy workflow (`/strategy`).
Use when a project brief needs turning into a schedule with a *critical path* — tasks, estimates, milestones, risks, and the ambiguities that will blow the timeline if left unasked. Fires on "plan this project" or "build a timeline from this brief." Not for organizing an existing task list (`task-list-to-plan`), sequencing a to-do dump (`task-sequence`), or prioritizing feedback into a release (`v2-plan`).
Synthesizes user research and market data into proto-persona profiles. Use when making early product decisions require understanding user pains, goals, and behaviors.
Restructures complex text into clear pyramid structures for improved logic and clarity. Use when you need to optimize communication by transforming lengthy or complex text into a more digestible format.
This skill assists product managers in preparing for and running effective product refinement sessions. Use when you need to understand problems deeply, determine solution requirements, build shared team understanding, and define clear success criteria.
Sequences unstructured items into a reinforcing feedback loop. Use when needing to arrange items in a logical order where each preceding item facilitates the next, creating a logical flow.
Creates clear requirements from a design asset, analyzing the provided image to generate structured requirements that will guide the development team. Use when you have a design asset and need to produce user stories, requirements, and acceptance criteria based on its visual elements and functionalities.
Transforms a conversation transcript into a well-structured list of requirements, using McKinsey-style issue trees and MECE principles to organize information systematically. Use when you have a conversation transcript and need to extract clear, actionable requirements from it.
Use when stakeholders have handed in *conflicting* requirements and the PM needs one unified list — "sales wants X, engineering wants not-X," multi-stakeholder PRD input, or /prd Step 2. Many conflicts dissolve once each side's underlying goal is named; the rest get decided, not averaged. Not for scoring options on a matrix (`tradeoff-matrix`) or deciding whether to fight at all (`pick-your-battles`).
Transforms vague problems and proposed solutions into crisp, actionable research briefs. Use when analyzing potential risks and guiding the research process to provide valuable insights for decision-making.
Use when you have a decision to make and want to frame it as a specific, researchable *decision question* — sized by how reversible and high-impact the call is — so research is attached to a decision instead of run for its own sake. Not for planning the study itself (`research-brief`), turning a hunch into a research plan (`intuition-to-research`), or synthesizing findings into insights (`research-synthesis`).
Use when a PM is about to reuse old research and needs to know what has *decayed* — "we did interviews 18 months ago, can we still trust them?", pre-kickoff checks on an old study, or challenges to a decision resting on aging findings. Not for synthesizing research (`research-synthesis`) or planning new research from a hunch (`intuition-to-research`).
Use when a PM has *scattered* research inputs — interview notes, support tickets, NPS comments, analytics, Slack anecdotes — and needs them merged into a few evidenced insights that answer specific product questions. Also fires on "what is all this feedback telling us?". Not for a single interview transcript (`interview-insights`), one conversation (`transcript-insights`), or survey-only data (`survey-to-actions`).
Transform raw interview transcripts into a tested feature hypothesis — from transcript cleanup through JTBD extraction, clustering, hypothesis formation, and experiment design. Use when synthesizing user interviews, deriving jobs-to-be-done, or turning research into feature hypotheses.
Triage and respond to a fresh workplace incident: a slipped date, a missed dependency, an elaborate excuse, a snarky or passive-aggressive comment, negative stakeholder feedback, brewing drama, a colleague who feels steamrolled, or ongoing friction with a difficult person. Use when the user says "this just happened", "X just told me...", "the date slipped", "I just got bad feedback", "someone is being difficult", "I'm being baited", or describes any live incident needing a response. Produces a categorized incident, an immediate response with exact scripts, and a forward-motion next step. Source: Shreyas Doshi corpus + 48 Laws of Power.
Tailors a resume to highlight the most relevant experience for a specific job, making it impossible to say no in the recruitment process. Use when you need to transform your resume into an interview-winning application that matches the job description perfectly.
Analyzes product managers' resumes and creates personalized career development plans. Use when analyzing a resume to identify skill gaps for advancement and develop a detailed skill development plan.
Ranks assumptions using pairwise comparisons with a QuickSort algorithm to prioritize risky assumptions for rapid validation. Use when avoiding arbitrary scoring and forcing explicit tradeoff decisions.
This skill estimates the median of any population with 93.75% confidence using just 5 random samples. Use when you need a quick estimate with limited data, cannot measure an entire large population, or face time/budget constraints that prevent larger samples.
This skill constructs, critiques, and audits arguments using the complete methodology from Weston's 'A Rulebook for Arguments'. Use when building a position, stress-testing logic, identifying fallacies, writing argumentative essays, or preparing for debate.
Use when a team is stuck reacting and needs a plan built from four views of the situation — current state, the projected *mess* if nothing changes, the ideal future, and what of that ideal can start today. Fires on "where is this heading," "help me plan out of this situation," or adaptive-planning requests. Not for disruption ideation (`disruption-what-ifs`), SWOT move generation (`swot-moves`), or a delivery plan from a task list (`project-plan`).
Use when a mid-project "can we just add one more thing" request lands and the PM needs its *cost* made visible before anyone says yes — quantified effort, what it displaces, and decision options with named consequences. Not for prioritizing a whole requirements list (`p0-p1-p2`), visualizing agreed tradeoffs (`tradeoff-matrix`), or deciding whether to fight the requester (`pick-your-battles`).
Diagnose a business's competitive advantages by analyzing which of the 7 Powers it has, which are emerging, and which are absent, then provide concrete playbooks to acquire missing Powers. Use when you need to map benefits to barriers, emphasize phase fit, and test each Power using falsifiable checks to score confidence levels and trends.
Reframing software features or projects using Ryan Singer's Shape Up methodology. Use when transforming vague ideas into well-shaped work ready for development teams, with emphasis on establishing constraints and preventing scope creep.
Use this methodology when collaboratively shaping a solution with the user - iterating on problem definition (requirements) and solution options (shapes).
This skill provides a debrief of a project manager's recent situation, mapping their behavior against the PM excellence framework to identify strengths and areas for improvement. Use when you want feedback on specific behaviors in meetings, conflicts, decisions, conversations, or feature launches.
Develops a comprehensive learning system for mastering a specific skill using the Skill Acquisition Protocol framework. Use when needing detailed recommendations for rapid skill development, including practice routines, resources, and measurement criteria.
Open a visual HTML catalog of all 243 PM OS skills — 14 categories under 5 themes, free-text search, and a workflow showcase, in one screen. Use when the user wants to browse, discover, or get an overview of available skills, or asks "what skills are available", "show me everything I can do", "what can PM OS do", "how do I use this", "list all skills", "explore the skills", "browse the skill library", or "what's in this thing".
This skill provides expert learning coach guidance to help individuals master complex skills rapidly. Use when you need a structured approach to break down a complex skill, practice deliberately, and follow a roadmap to mastery, including overcoming obstacles and staying motivated.
This skill applies the DSSS framework to turn vague goals into measurable performance in a skill. Use when transforming a skill from a vague goal to a ruthless mastery plan.
Rewrites provided content to be clear and easy to skim using explicit signposting language. Use when transforming messy content into well-structured writing.
Use when a long, meandering Slack thread needs to become a clear summary — the decisions, the action items with owners, and what's still open — read for *signal* against the reader's role and why they're catching up. Not for an IDEAS-format meeting summary (`meeting-summary`), reconstructing a work conversation's flow (`transcript-insights`), or pulling structured requirements from a discussion (`requirements-from-talk`).
Engages in extremely thorough, self-questioning reasoning, mirroring human stream-of-consciousness thinking. Use when you need to explore a question or problem in great depth, following principles of exploration over conclusion, depth of reasoning, thinking process, and persistence.
Identifies flawed solutions from customer problem analysis. Use when highlighting the importance of careful problem analysis and solution design.
Develops a SQL query based on specific requirements and data tables, optimizing for fast execution, readability, and documentation. Use when tasked with creating optimized SQL queries from requirements and data tables.
Use when a coding task needs one clean *mode* held without mixing — Staff Engineer mode for planning and architecture (no code), or Intern mode for precise, scoped implementation (no re-architecting). Not for producing a technical architecture brief from a PRD (`tech-arch-brief`), finding the application's shape or archetype (`eng-shape`), or translating a technical plan for business stakeholders (`tech-to-business`).
Navigate stakeholder complexity end-to-end — from power mapping and risk review through message framing, challenging meeting prep, difficult conversations, and executive presence review. Use when mapping power dynamics, planning influence strategy, or navigating organizational politics.
Produces a Power–Interest grid with names, captures informal influence, and proposes a concrete engagement plan for stakeholders. Use when you need to analyze and strategize on the power, interest, and influence of stakeholders in an initiative.
Identifies political risks and objections in a Feature/PRD and recommends mitigations before broad circulation. Use when you need to review a product requirement document or feature description for potential stakeholder risks and politics.
Converts vague work experiences into compelling STAR (Situation, Task, Action, Result) stories for product managers. Use when the user needs to convert work experiences into compelling STAR stories for PMs.
Generates startup ideas based on user responses to a set of questions, creating innovative software product concepts that address the user's needs and pain points. Use when you have user responses and need to conceptualize software solutions that could be considered a bargain at $30 per month.
Use when you need to write a status update that gets read and acted on — one status line, wins/next/risks/asks, sized to the audience and *skimmable* so the first three lines carry the point. Not for critiquing an existing update (`exec-update-review`), building a presentation deck (`problem-deck`), or choosing the week's priorities (`weekly-top-3`).
Use when you need to plan a presentation for a specific audience and time slot before building any slides — decide the depth, tone, data-vs-narrative balance, and the SCQA spine the deck will hang on. Not for writing the narrative prose (`presentation-narrative`), structuring slides from a problem (`problem-deck`), or reading the room politically (`prep-the-room`).
Extracts and structures critical context for building a Strategy Kernel Canvas, focusing on History, Diagnosis, and Guiding Policy sections. Use when you need to inform the strategy development process with structured information from a product manager's input.
This skill enables the creation of a compelling product strategy review from draft documents and context. Use when preparing for a product review and needing to analyze and improve a draft, ensuring it includes a compelling punchline, addresses customer pain points, and proactively covers likely executive questions.
Use when a messy problem needs a clear recommendation and you do NOT need a full issue tree — a top-down (deductive) and bottom-up (inductive) pass that *converge* on one answer, delivered answer-first. Also /decisions Step 5, taking the MECE option tree and causal map as input and returning a Pyramid-Principle recommendation. Not for building the issue tree itself (`mckinsey-issue-tree`), a MECE decomposition (`mece-tree`), root-cause diagnosis alone (`causal-tree`), or framing the problem before analysis (`problem-framing-canvas`).
Use when a design or product goal is vague — "improve onboarding," "make search better" — and the PM needs one primary metric with a baseline, a target, and *guardrails* before work starts. Not for the full measurement workflow (`/measure`), event-schema design (`tracking-schema`), estimating a feature's impact (`impact-sizing`), or designing the experiment (`experiment-design`).
Identify your personal superpower, a unique strength or ability that comes naturally and sets you apart from others. Use when you need to conduct a step-by-step interview to gather information about your experiences, skills, and qualities, and provide an assessment of your superpower, its manifestations, examples, potential drawbacks, and confidence level in the assessment.
Use when a pile of open-ended survey responses needs turning into *pain points* with honest counts, verbatim quotes, and concrete action items. Fires on "analyze these survey results" or an exported CSV of free-text answers. Not for mixed-source research (`research-synthesis`), support tickets (`tickets-to-improvements`), or NPS programs (`nps-to-cx-plan`).
Generates combinations of strategic moves across all SWOT pairings, expressed as solution-space patterns. Use when you need to produce strategic move patterns for Growth leverage, Defensive advantage, Capability building, Protective actions, Focus & trade-offs, and Market shaping from a given SWOT analysis.
Use when you have an existing list of tasks and need it turned into a sequenced plan — ordered by *dependency*, with the missing tasks surfaced, contingencies for the risky ones, and go/no-go milestones. Not for planning from a brief with a critical path (`project-plan`), ordering an unstructured to-do dump (`task-sequence`), or turning feedback into a release plan (`v2-plan`).
Creates structured task sequences from unorganized to-do lists. Use when helping users organize tasks by initial dumping, affinitizing, unpacking, creating interrelationship diagrams, and engaging in dialogue to clarify and sequence tasks effectively.
Generates an outside-in perspective on how a PM is perceived by their team, particularly designers and engineers. Use when you want to gain insights into your team's view of your performance and behavior.
Use when you have a PRD and need a Technical Architecture Brief — system context, component architecture, tech-stack rationale, and risk mitigation — where every architecture *trade-off* names the requirement that drives it and the condition that would reverse it. Not for finding the application's shape or archetype (`eng-shape`), translating a decided technical plan for stakeholders (`tech-to-business`), or writing the PRD itself (`prd-draft`).
Analyzes technology announcements to uncover strategic implications and new opportunities. Use when a new technology, feature, or capability is announced and you need to understand its broader impact on your business or product.
Use when you need to translate a technical explanation for a non-technical stakeholder so they can make *the decision* in front of them — jargon stripped, an analogy where it helps, risks preserved, and their likely questions answered. Not for producing the technical architecture itself (`tech-arch-brief`), presenting a deck to leadership (`problem-deck`), or writing a status update (`status-update`).
Transforms support tickets into actionable product improvements. Use when analyzing support tickets and user complaints to identify trends, patterns, and areas for improvement to generate product insights.
Procedural detail for the tidy operation — full algorithm for reviewing Work artifacts, routing orphaned files into project folders, and updating Context files. Called as supporting documentation by the user-facing tidy skill. Use when the tidy orchestrator needs the complete step-by-step procedure.
Use when a stakeholder decision is stuck on a conflict and you want to dissolve it with Theory of Constraints — trace symptoms to a root cause (Effect-Cause-Effect), surface the conflict and the assumption holding it (the Evaporating Cloud), then break that assumption. Not for a general root-cause tree (`causal-tree`), a MECE decomposition (`mece-tree`), or converging a messy problem to a recommendation (`structure-problem`).
Use when you need to distill a stretch of completed work — todo list, calendar, shipped items — into the top 5 wins stated as outcomes, for a brag doc, perf review input, or end-of-week reflection. Not for planning the coming week (`weekly-top-3`), the weekly report to others (`status-update`), or interview-ready narratives (`star-stories`).
Use when you have a UI or feature and metrics you want to measure, and need the analytics *events* and their schemas to instrument — each event tied to a real measurement question, with the properties needed to actually compute the metric. Not for defining what to measure (`success-metric`), querying data you already collect (`sql-from-spec`), or a broad product analytics plan (`analytics-tracking`).
Use when you need to communicate a feature request's trade-off visually — place it on a priority×effort *2×2* against real comparisons so stakeholders see why it's worth pursuing, deferring, or rejecting. Not for prioritizing a whole requirements list (`p0-p1-p2`), pricing one scope-change request against a commitment (`scope-defense`), or ranking discovery opportunities (`ost-prioritize`).
Cleans up raw interview transcripts to improve readability while maintaining the original meaning and speaker's voice. Use when the user needs to clean up raw interview transcripts.
Use when a conversation transcript — a long meeting, a sprawling Slack thread, a call recording — needs *reconstruction*: who said what, how the discussion branched, what got committed, and what's still dangling. Fires on "what happened in this conversation" or "pull the decisions and actions out of this." Not for an IDEAS-format meeting summary (`meeting-summary`), customer-interview analysis (`interview-insights`), or extracting requirements (`requirements-from-talk`).
Classifies decisions as reversible or permanent from first principles. Use when the user needs to classify decisions as reversible or permanent from first principles.
Translates user stories and design mockups into clear, testable acceptance criteria for UI. Use when creating specific, measurable specifications covering all UI states, breakpoints, and edge cases to enable systematic QA validation.
Converts UI screenshots into structured JSON descriptions by analyzing and detailing all visual elements, their relationships, and any text content present in the image. Use when the user needs to convert UI screenshots into structured JSON descriptions.
Generates comprehensive and insightful use cases from user input to guide product development and strategy. Use when you need to create use cases and corresponding use case maps based on any given input.
Transforms research and broad ideas into well-defined, testable use cases. Use when needing to define use cases for PRDs, articulate specific use cases for startups, or validate problem-solution fit before building based on Alistair Cockburn's methodology.
Use when a persona is buzzwords — "Sarah, 34, tech-savvy marketer" — and the PM needs it upgraded into an actionable profile: real *tasks*, constraints, and scenarios, with every claim either grounded in data or flagged as assumed. Not for building a first persona from research (`proto-persona`) or emotional/behavioral mapping (`create-empathy-maps`).
Breaks down initiative requirements into user stories. Use when tasked with creating user stories from an initiative's context, functionality description, and a specific user story template.
Identifies edge cases and scenarios for a new product or feature based on the product brief. Use when you need to create a comprehensive list of potential user interactions, edge cases, and scenarios, along with the expected behavior for each.
This skill reviews and corrects product manager's requirements that contain incorrect or imprecise UX terminology. Use when there is a need to ensure that the UX terminology used in product requirements is accurate and professional.
Use when a product has launched, feedback has piled up, and the PM needs a prioritized v2 plan — *themes* scored with one framework and sequenced into phases. Fires on "what should v2 be?" or "turn this feedback into a roadmap." Not for planning how to collect post-launch feedback (`feedback-loop`), answering research questions (`research-synthesis`), or support tickets alone (`tickets-to-improvements`).
This skill conducts a value chain analysis for a specific product or service to understand key elements that generate profits and revenue. Use when you need to identify core value generators and potential vulnerabilities in a business model by breaking down the value chain from end-user needs to core value generators.
Calculates the economic value of reducing uncertainty before making decisions. Use when deciding whether to gather more data or act now, prioritizing which uncertainties to measure first, or any decision where information costs money and time.
Generates diverse outputs by prompting for a probability distribution instead of a single response. Use when the task requires genuine diversity in creative writing, brainstorming, synthetic data generation, persona/dialogue simulation, or open-ended QA with multiple valid answers.
Use when a product, offering, doc, or flow is bloated and you want to improve it by *subtraction* — name the one core purpose, then cut every element that doesn't serve it. Not for cutting steps from a specific multi-step flow (`friction-reduce`), deciding what makes a release (`p0-p1-p2`), or pricing a proposed scope addition (`scope-defense`).
Classifies files and modules into Leaf (safe to vibe), Branch (caution), or Trunk (hands off) based on dependency isolation, stability, and external verifiability. Use when identifying safe areas in a codebase for AI modification without human review.
Converts a broad company vision or mission statement into tangible, measurable Objectives and Key Results (OKRs) for the upcoming quarter. Use when you need to create a set of OKRs that align with the company's vision and provide clear, actionable targets.
Use when a PM or design lead holds a vision deck and needs it *bridged* to this quarter's concrete work — themes turned into operational design principles, elements sorted by what's actionable now, and vague vision words pinned down. Not for writing OKRs from a vision (`vision-to-okrs`), a roadmap from user interviews (`now-next-later`), or the strategy itself (`strategy-kernel`).
Use when the week ahead is a pile of meetings, threads, and half-started projects and you need to triage it into the 3 priorities that define success — plus protected time to do them and a decision on what deliberately doesn't happen. Not for reviewing what you accomplished (`top-5-wins`), writing the weekly report (`status-update`), or roadmap horizons (`now-next-later`).
Use when you already have the content — findings, data, notes — and need to arrange it into a presentable flow, surfacing which of What / So What / Now What is missing. Not for deriving a storyline from a problem (`problem-deck`), writing narrative prose (`presentation-narrative`), or planning depth and tone for an audience (`strategic-deck`).
Converts competitive analysis into a positioning strategy and unique value proposition. Use when you have a competitive analysis and need to develop a clear market positioning and value proposition for your product or service.
Converts product ideas into detailed sketch descriptions for wireframes. Use when needing to illustrate flows, affordances, user journeys, and reduce friction at various touchpoints based on product ideas and additional details provided.
Works backwards from a product assumption to identify an easy signal for validation. Use when needing to derive an efficient signal to validate a single product assumption early in the development process.
Use when you're building a PM work sample — a take-home, portfolio piece, or interview presentation — that has to show how you think and be *specific* to the company you're applying to. Not for writing the résumé (`resume`), preparing interview answers (`pm-interview`), building behavioral stories (`star-stories`), or drafting a real PRD (`prd-draft`).
Represents messy work as durable obligations, workflow building blocks, fragments, AI/automation insertion points, and exception queues. Use when analyzing interviews, messy notes, customer research, operational workflows, PM workflows, vertical SaaS opportunities, AI insertion points, automation opportunities, durable obligations, fragmented work, hated execution burden, or determining where AI should fit into an existing workflow.
Design engaging, high-impact workshop activities tailored to specific problems and participant parameters while honoring constraints like time, participant count, roles, and platform. Use when you need to generate distinct activity variants optimized for the inputs, including a step-by-step timeline that sums exactly to the stated duration, tailored facilitation mechanics, and logistics.
Get every skill above, plus 11 guided workflows, 12 review subagents, and 6 live MCP connectors — installed in your Claude Code or Claude Cowork in minutes.
One-time license. Instant download via Polar.
$99 one-time · Instant Polar download