phuryn/pm-skills
68 skills135k installs2M starsGitHub
Install
npx skills add https://github.com/phuryn/pm-skillsSkills in this repo
1Competitor AnalysisThe competitor-analysis skill conducts strategic competitive intelligence for a named product and optional market segment, identifying five direct competitors with positioning, capabilities, and differentiation gaps. Analysis steps scope the market, discover competitors via web research, gather positioning and pricing intelligence, assess strengths and weaknesses, map differentiation opportunities, and synthesize twelve to eighteen month risks. Output sections include market overview, competitive set summary, and per-competitor profiles covering company background, product strengths, weaknesses, business model, pricing, and threat assessment. Differentiation opportunities highlight unmet needs, underserved segments, jobs-to-be-done gaps, channel approaches, and partnership white space. A closing positioning recommendation advises segments to target or avoid and threats to monitor. Best practices stress multi-source validation, adjacent versus direct competitor distinction, emerging entrant awareness, and customer pain points competitors still miss. Users may supply existing research files for direct synthesis instead of fresh searches.2.6kinstalls2Business ModelMetadata Name business model Description Generate a Business Model Canvas with all 9 building blocks Use when creating a business model documenting how a business creates value or analyzing an existing business model Triggers business model canvas BMC business model how we make money You are a business model strategist designing a Business Model Canvas for ARGUMENTS Your task is to create a comprehensive Business Model Canvas that outlines how the business creates delivers and captures value Input Requirements Product or service description Target customer s and market Current business operations or assumptions Competitive context or industry dynamics The business model skill documents workflows prerequisites and usage patterns grounded in its repository SKILL md Agents should follow the documented steps respect safety and permission notes and cite only capabilities described in the source It triggers on phrases matching the skill description and integrates with the agent toolchain for the tasks outlined in the documentation2.6kinstalls3Privacy PolicyYou are an experienced data privacy and compliance specialist Your role is to help draft comprehensive clear and compliant privacy policies for digital products and services Purpose Draft a detailed privacy policy for a product or service The policy covers data types handled applicable jurisdiction and clearly marks clauses that require legal review Provide plain language explanations to ensure accessibility and transparency Important Disclaimer This is for informational purposes only and does not constitute legal advice Always have a qualified attorney specializing in data privacy law review the final policy before publication Privacy policies are legally binding documents that establish your company s responsibilities and users rights professional legal review is essential Input Arguments PRODUCT_NAME Name of the product or service PRODUCT_URL URL or description of the product optional will be researched if provided COMPANY_NAME Legal name of your company COMPANY_ADDRESS Company headquarters or registered address CONTACT_EMAIL Email for privacy inquiries e g privacy company com INFORMATION_TYPES Types of data collected e g names emails usage behavior location data payment2.4kinstalls4Brainstorm Ideas NewBrainstorm Product Ideas New Product Multi perspective ideation for initial product discovery of a new product Generates specific feature ideas from PM Designer and Engineer viewpoints You are supporting initial product discovery for a new product ARGUMENTS If the user provides files market research competitive analysis read them first Use web search to understand the market if needed Initial Discovery vs Continuous Discovery Initial Discovery focuses on vision business model and market validation you re testing whether the product should exist Continuous Discovery runs in parallel with delivery you re constantly learning and iterating on a live product This skill is for initial discovery The brainstorm ideas new agent skill provides documented workflows prerequisites triggers and safety guidance from its SKILL md source Agents load it when user requests match the description and follow step by step instructions without inventing capabilities It integrates with standard agent tooling for the tasks inputs outputs and failure modes described in the repository documentation2.3kinstalls5Create PrdYou are an experienced product manager responsible for creating a comprehensive Product Requirements Document PRD for ARGUMENTS This document will serve as the authoritative specification for your product or feature aligning stakeholders and guiding development A well structured PRD clearly communicates the what why and how of your product initiative This skill uses an 8 section template proven to communicate product vision effectively to engineers designers leadership and stakeholders 1 Gather Information If the user provides files read them carefully If they mention research URLs or customer data use web search to gather additional context and market insights 2 Think Step by Step Before writing analyze What problem are we solving Who are we solving it for How will we measure success What are our constraints and assumptions 3 Apply the PRD Template Create a document with these 8 sections2.3kinstalls6User StoriesCreate user stories following the 3 C s Card Conversation Confirmation and INVEST criteria Generates stories with descriptions design links and acceptance criteria Use when Writing user stories breaking down features into stories creating backlog items or defining acceptance criteria Arguments PRODUCT The product or system name FEATURE The new feature to break into stories DESIGN Link to design files Figma Miro etc ASSUMPTIONS Key assumptions or context 1 Analyze the feature based on provided design and context 2 Identify user roles and distinct user journeys 3 Apply 3 C s framework Card Simple title and one liner Conversation Detailed discussion of intent Confirmation Clear acceptance criteria 4 Respect INVEST criteria Independent Negotiable Valuable Estimable Small Testable 5 Use plain language a primary school graduate can understand 6 Link to design files for visual reference 7 Output user stories in structured format Description As a user role I want to action so that benefit2.2kinstalls7Startup CanvasMetadata Name startup canvas Description Generate a Startup Canvas for a new product Combines the 9 section Product Strategy Canvas with a Business Model Cost Structure Revenue Streams Designed specifically for startups and new products Triggers startup canvas new product canvas startup strategy startup business model Startup Canvas vs Business Model Canvas vs Lean Canvas Popular approaches like Business Model Canvas Strategyzer and Lean Canvas Ash Maurya mix strategy and business model into one artifact The Startup Canvas Paweł Huryn separates them 9 strategy sections from the Product Strategy Canvas Cost Structure Revenue Streams Why not Business Model Canvas No vision why should your team wake up every day No Can t Won t test what stops competitors from copying you No trade offs what you choose NOT to do creates focus No key metrics how do you know the strategy is working Key Partnerships and Key Resources are rarely useful for early stage products Why not Lean Canvas Introduces redundancy Problem overlaps with Market Segments markets are defined by2.2kinstalls8Summarize MeetingYou are an experienced product manager responsible for creating clear actionable meeting summaries from ARGUMENTS This skill transforms raw meeting transcripts into structured accessible summaries that keep teams aligned and accountable Meeting summaries are how knowledge spreads and accountability stays clear in product teams A well structured summary captures decisions key points and action items in language everyone can understand regardless of who attended 1 Gather the Meeting Content If the user provides a meeting transcript recording or notes file read them thoroughly If they mention a meeting that needs context use web search to find any related materials or background documents 2 Think Step by Step Who attended and what were their roles What was the main topic or agenda What decisions were made What are the next steps and who owns them Are there open questions or blockers 3 Extract Key Information Identify main discussion topics Note decisions made during the meeting Flag any disagreements or concerns Determine action items with owners and due dates2.2kinstalls9Product NameThe product-name skill helps developers and product teams brainstorm distinctive product names aligned to brand values and target audience positioning. Given company and product context, it proposes five names each with rationale explaining value reflection and audience appeal, brand architecture fit, memorability and competitive differentiation, and brief domain or trademark availability notes. Prioritization criteria favor easy pronunciation and spelling, distinctiveness from competitors, alignment with brand tone, relevance to core value proposition, and registrability. Tips recommend sharing brand guidelines, target audience preferences, competitor names to avoid, naming conventions, value proposition details, and geographic or language constraints. Triggers include product name, name ideas, brand name, naming, what to call, and product naming requests. Use when naming a new product or feature, rebranding, exploring pre-launch name options, or testing candidates against brand guidelines before committing to positioning and domain registration.2.2kinstalls10Product StrategyThe product-strategy skill. Create a comprehensive product strategy using the 9-section Product Strategy Canvas - vision, segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility. Use when building a product strategy, creating a strategic plan, or defining product direction. Covers vision, market segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility. - **Triggers**: product strategy, strategy canvas, strategic plan, product strategy document ## Instructions You are an experienced product strategist developing a comprehensive product strategy for $ARGUMENTS. Your task is to create a detailed Product Strategy Canvas that outlines how the product will compete, win, and grow in the market. Market Segments - Market defined by people's problems (not demographics) - Jobs to Be Done (JTBD), desired outcomes, constraints - Who is our first segment?. Relative Costs - Do we optimize for low cost (like Southwest Airlines)?. - Or do we emphasize unique value (like Starbucks)?.2.2kinstalls11Gtm StrategyCreate a go-to-market strategy covering marketing channels, messaging, success metrics, and launch timeline. Use when planning a product launch, creating a GTM plan from scratch, or defining a launch strategy for a new market. --- name: gtm-strategy description: "Create a go-to-market strategy covering marketing channels, messaging, success metrics, and launch timeline. Use when planning a product launch, creating a GTM plan from scratch, or defining a launch strategy for a new market." --- # GTM Strategy ## Overview Create a comprehensive go-to-market strategy for a product launch. This skill covers marketing channels, messaging development, success metrics definition, and launch planning. ## When to Use - Planning a product launch - Creating a GTM plan from scratch - Defining a launch strategy for a new market - Developing product-to-market fit strategy - Preparing a product go-live roadmap ## How It Works ### Step 1: Gather Research Data The system will help you load and analyze early research about your product and target market.2.2kinstalls12Monetization StrategyThe monetization-strategy skill. Brainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments. Use when exploring revenue models, evaluating pricing strategies, or deciding how to monetize a product. Use when exploring revenue models, pricing strategies, or business model options. - **Triggers**: monetization strategy, revenue model, pricing strategy, how to monetize, make money ## Instructions You are an experienced business model strategist brainstorming monetization strategies for $ARGUMENTS. Your task is to develop 3-5 distinct monetization approaches that could work for the product or feature, evaluate fit with the target market, and outline low-effort validation experiments. Strategy Name & Description - What is the monetization model?. - How does it work for this product?. How It Works - Revenue model and pricing mechanics - Value exchange between company and customer - Payment frequency and transaction size - Lifecycle and retention mechanisms ### 3.2.2kinstalls13Sentiment AnalysisAnalyze user feedback data to identify segments with sentiment scores, JTBD, and product satisfaction insights. Use when analyzing user feedback at scale, running sentiment analysis on reviews or surveys, or identifying satisfaction patterns. --- name: sentiment-analysis description: "Analyze user feedback data to identify segments with sentiment scores, JTBD, and product satisfaction insights. Use when analyzing user feedback at scale, running sentiment analysis on reviews or surveys, or identifying satisfaction patterns." --- # Sentiment Analysis ## Purpose Analyze large-scale user feedback data to identify market segments, measure satisfaction, and uncover product improvement opportunities. This skill synthesizes feedback into actionable insights organized by user segment, sentiment, and impact. ## Instructions You are an expert user researcher and feedback analyst specializing in qualitative data synthesis and sentiment analysis at scale. ### Input Your task is to analyze user feedback data for **$ARGUMENTS** and identify market segments with associated sentiment insights.2.1kinstalls14Value PropositionThe value-proposition skill. Design a detailed value proposition using a 6-part JTBD template - Who, Why, What before, How, What after, Alternatives. Use when creating a value proposition, analyzing customer value delivery, or articulating why customers should choose your product. Includes practical examples for designing compelling customer value. - **Triggers**: value proposition, value prop, customer value, JTBD value, value map ## Instructions You are a product strategist designing a clear value proposition for $ARGUMENTS. Your task is to develop a comprehensive value proposition that articulates the customer value delivered by the product. Who** - Who is this value proposition for?. - What customer segment are we addressing?. - What are their characteristics and constraints?. The workflow follows the source SKILL.md contract with progressive reference loading, clear trigger phrases, and practical steps developers can apply directly in agent sessions.2.1kinstalls15Swot AnalysisPerform a detailed SWOT analysis - strengths, weaknesses, opportunities, and threats with actionable recommendations. Use when doing strategic assessment, competitive analysis, or evaluating a product or business position. The swot-analysis skill documents workflows and patterns from the repository SKILL.md. --- name: swot-analysis description: "Perform a detailed SWOT analysis - strengths, weaknesses, opportunities, and threats with actionable recommendations. Use when doing strategic assessment, competitive analysis, or evaluating a product or business position." --- # SWOT Analysis ## Metadata - **Name**: swot-analysis - **Description**: Perform a detailed SWOT analysis for a product. Identifies strengths, weaknesses, opportunities, and threats with actionable recommendations. - **Triggers**: SWOT analysis, strengths weaknesses, SWOT matrix, strategic assessment ## Instructions You are a strategic analyst conducting a SWOT analysis for $ARGUMENTS. Your task is to thoroughly evaluate the internal and external factors that will impact product success and competitive positioning. ## Input Requirements - Product description and current state - Competitive landscape and market c.2.1kinstalls16Brainstorm Ideas ExistingBrainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio. The brainstorm-ideas-existing skill documents workflows and patterns from the repository SKILL.md. --- name: brainstorm-ideas-existing description: "Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio." --- ## Brainstorm Product Ideas (Existing Product) Multi-perspective ideation for continuous product discovery. Generates ideas from PM, Designer, and Engineer viewpoints, then prioritizes the best five. ### Context You are supporting a product trio performing continuous product discovery for **$ARGUMENTS**. If the user provides files (research data, opportunity trees, personas), read them first. If they mention a product URL, use web search to understand the product.2.1kinstalls17Ideal Customer ProfileThis skill synthesizes customer research data into an Ideal Customer Profile (ICP) definition built on four framework components: demographics, behaviors, jobs to be done (JTBD), and needs and pain points. Developers use it when analyzing product-market fit survey responses, customer interview transcripts, trial user behavior, churn analysis, or win/loss data to determine which customers are most likely to find value, retain, and expand. It works through six steps: gather customer data, segment by value (highest LTV, lowest churn, fastest time-to-value), profile demographics, identify buying and adoption behaviors, define functional, emotional, and social jobs, and document pain points with before and after states. Input is passed via $ARGUMENTS as research data, usage analytics, or sales activity. Output is a full ICP definition with firmographic and behavioral profiles, JTBD mapping, quantified impact metrics, disqualification criteria, and go-to-market implications, based on Clayton Christensen's Jobs to Be Done theory.2.1kinstalls18Grammar CheckThe grammar-check skill "Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft." It covers $TEXT : The text to review. Key workflows include note the objective: Is this marketing copy, technical documentation, a presentation, an email, social media content?. Developers invoke grammar-check when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.2.1kinstalls19Metrics DashboardDefine and design a product metrics dashboard with key metrics, data sources, visualization types, and alert thresholds. Use when creating a metrics dashboard, defining KPIs, setting up product analytics, or building a data monitoring plan. The metrics-dashboard skill documents workflows and patterns from the repository SKILL.md. --- name: metrics-dashboard description: "Define and design a product metrics dashboard with key metrics, data sources, visualization types, and alert thresholds. Use when creating a metrics dashboard, defining KPIs, setting up product analytics, or building a data monitoring plan." --- ## Product Metrics Dashboard Design a comprehensive product metrics dashboard with the right metrics, visualizations, and alert thresholds. ### Context You are designing a metrics dashboard for **$ARGUMENTS**. If the user provides files (existing dashboards, analytics data, OKRs, or strategy docs), read them first. ### Domain Context **Metrics vs KPIs vs NSM**: Metrics = all measurable things. KPIs = a few key quantitative metrics tracked over a longer period.2.1kinstalls20Release NotesGenerate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped. The release-notes skill documents workflows and patterns from the repository SKILL.md. --- name: release-notes description: "Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped." --- ## Release Notes Generator Transform technical tickets, PRDs, or internal changelogs into polished, user-facing release notes. ### Context You are writing release notes for **$ARGUMENTS**. If the user provides files (JIRA exports, Linear tickets, PRDs, Git logs, or internal changelogs), read them first. If they mention a product URL, use web search to understand the product and audience. **Gather raw material**: Read all provided tickets, changelogs, or descriptions.2.1kinstalls21User PersonasThe user-personas skill "Create refined user personas from research data - 3 personas with JTBD, pains, gains, and unexpected insights. Use when building personas from survey data, creating user profiles from research, or segmenting users for product decisions." It covers data Collection : Read and review all provided research data and documents. Key workflows include pattern Recognition : Identify recurring characteristics, goals, pain points, and behaviors across users. Developers invoke user-personas when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.2.1kinstalls22Pre MortemThe pre-mortem skill "Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers real problems , Paper Tigers overblown concerns , and Elephants unspoken worries , then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong." It covers imagine the product launches in 14 days. Key workflows include now imagine it fails - customers don't adopt it, revenue targets miss, reputation takes a hit. Developers invoke pre-mortem when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.2.1kinstalls23Customer Journey MapThe customer-journey-map skill "Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Use when mapping the customer experience, identifying friction points, improving onboarding, or visualizing the user journey." It covers define the persona : Who is traveling this journey? Use a specific persona with JTBD, not a generic user.. Key workflows include map the journey stages adapt to the product :. Developers invoke customer-journey-map when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.2kinstalls24Pricing StrategyThe pricing-strategy skill "Analyze and design pricing strategies including pricing models, competitive pricing analysis, willingness-to-pay estimation, and price elasticity. Use when setting prices, evaluating pricing models, preparing for a pricing change, or comparing freemium vs paid approaches." It covers understand the value delivered :. Key workflows include what is the core value proposition?. Developers invoke pricing-strategy when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.2kinstalls25Market SizingThe market-sizing skill "Estimate market size using TAM, SAM, and SOM with top-down and bottom-up approaches. Use when sizing a market opportunity, estimating addressable market, preparing for investor pitches, or evaluating market entry." It covers market Definition : Define the market boundaries - what problem space, which customer segments, what geography or constraints apply. Key workflows include top-Down Estimation : Start from total industry size and narrow to the relevant slice. Developers invoke market-sizing when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.2kinstalls26Lean CanvasThe lean-canvas skill "Generate a Lean Canvas with problem, solution, metrics, cost structure, UVP, unfair advantage, channels, segments, and revenue. Use when exploring a lean startup canvas, testing a business hypothesis, or modeling a new venture." It covers description : Generate a Lean Canvas business model with detailed sections for problem, solution, metrics, cost structure, UVP, unfair advantage, channels, segments, and revenue.. Key workflows include triggers : lean canvas, startup canvas, lean model, business hypothesis. Developers invoke lean-canvas when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.2kinstalls27Positioning IdeasThe positioning-ideas skill "Brainstorm product positioning ideas differentiated from competitors. Identifies top competitors and generates positioning statements with rationale. Use when developing product positioning, differentiating from competitors, or crafting brand positioning strategy." It covers developing product positioning strategy. Key workflows include differentiating from competitors. - Developing product positioning strategy - Differentiating from competitors - Crafting brand positioning statements - Identifying market positioning gaps - Triggers: positioning, brand positioning, differentiation, how to position, positioning statement Developers invoke positioning-ideas when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.2kinstalls28Marketing IdeasThe marketing-ideas skill "Generate 5 creative, cost-effective marketing ideas with channels, messaging, and engagement rationale. Use when brainstorming marketing campaigns, planning product promotion, or looking for creative marketing tactics." It covers brainstorming marketing campaigns. Key workflows include planning product promotion strategies. - Brainstorming marketing campaigns - Planning product promotion strategies - Exploring creative marketing approaches - Building growth initiatives - Triggers: marketing ideas, promote product, marketing campaign, creative marketing, growth ideas Developers invoke marketing-ideas when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.2kinstalls29Brainstorm OkrsThe brainstorm-okrs skill "Brainstorm team-level OKRs aligned with company objectives - qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs." It covers objective Why, What, When : Qualitative, inspirational, time-bound goal. Typically quarterly. Should be SMART.. Key workflows include key Results How much : Quantitative metrics typically 3 and their expected values.. Developers invoke brainstorm-okrs when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.2kinstalls30Review ResumeThe review-resume skill "Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact." It covers $RESUME : The resume text or content to review. Key workflows include $JOB_POSTING : Optional The job posting or target role description for tailoring feedback. Developers invoke review-resume when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.2kinstalls31Product VisionThe product-vision skill "Brainstorm an inspiring, achievable, and emotional product vision that motivates teams and aligns stakeholders. Use when defining or refining a product vision, creating a vision statement, or aligning the team around a shared direction." It covers name : product-vision. Key workflows include triggers : product vision, vision statement, create vision, inspiring vision, north star vision. Developers invoke product-vision when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.2kinstalls32Opportunity Solution TreeThe Opportunity Solution Tree (OST) is a visual framework from Teresa Torres' Continuous Discovery Habits that structures product discovery by connecting measurable outcomes to customer opportunities, multiple solution approaches, and fast experiments. It prevents premature commitment to solutions by forcing teams to first map the opportunity space using customer research. The OST has four levels: desired outcome (top), opportunities (customer needs prioritized by Importance × (1-Satisfaction)), solutions (3+ options per opportunity generated by PM-Designer-Engineer trios), and experiments (assumption-testing validations). Key practices include maintaining one outcome per tree, framing opportunities as problems not features, generating competing solutions before deciding, and updating the tree weekly as learning accumulates from interviews and experiments.2kinstalls33Test ScenariosThe test-scenarios skill "Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation." It covers $PRODUCT : The product or system name. Key workflows include $USER_STORY : The user story to test title and acceptance criteria. Developers invoke test-scenarios when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.2kinstalls34Ab Test AnalysisA/B Test Analysis evaluates experiment results through statistical significance testing, sample size validation, and confidence interval calculations. It translates raw test data into actionable product decisions by checking primary metrics, guardrail metrics, and practical business impact. The skill validates test setup (sample power, duration, randomization), calculates relative lift and p-values, interprets results against significance thresholds, and provides structured recommendations: Ship (positive significant lift), Extend (positive trend, underpowered), Stop (flat/insignificant), or Investigate (guardrail trade-offs). Designed for product managers and data analysts evaluating split tests, conversion experiments, and feature rollout decisions.2kinstalls35Cohort AnalysisCohort Analysis & Retention Explorer enables systematic examination of user engagement patterns grouped by signup period or feature launch date. The skill ingests CSV, Excel, or JSON data and performs multi-stage analysis: data validation, retention rate calculation, visualization generation, pattern identification, and research design. It produces retention heatmaps, adoption curves, anomaly detection, and actionable follow-up research recommendations including targeted user interviews and A/B test suggestions. Includes optional Python script generation for reproducible ongoing analysis using pandas and numpy.2kinstalls36Market SegmentsThe market-segments skill helps with Identify 3-5 potential customer segments with demographics, JTBD, and product fit analysis. Use when exploring market segments, identifying target audiences, evaluating new markets, or learning how to segment a market. Key workflows include Market Segments; Purpose; Instructions; Input. Documented capabilities cover Clear, memorable segment identifier; Size estimate (% of total market or absolute numbers if data available); Growth trajectory and market dynamics; Core characteristics (age, role, company size, industry, geography, etc.); Decision-maker profiles if B2B. Agents should invoke it when users ask about market segments or mention triggers defined in the skill frontmatter. Follow the SKILL.md steps, reference files, and output formats rather than improvising outside documented scope. ## Instructions You are a strategic market research expert skilled in market segmentation, customer profiling, and total addressable market (TAM) analysis. ### Input Your task is to identify and analyze potential customer segments for **$ARGUMENTS**. If research data, market studies, customer databases, or existing segmentation documents are provided, read a.2kinstalls37Prioritize FeaturesThe prioritize-features skill helps with Prioritize a backlog of feature ideas based on impact, effort, risk, and strategic alignment with top 5 recommendations. Use when prioritizing a feature backlog, making scope decisions, or ranking product ideas. Key workflows include Prioritize Feature Backlog; Context; Domain Context; Instructions. Documented capabilities cover **Impact**: How much does it move the needle on desired outcomes? Consider Opportunity Score if customer data is available.; **Effort**: How much development, design, and coordination is required?; **Risk**: How much uncertainty exists? What assumptions need testing?; **Strategic alignment**: How well does it fit the product vision and current goals?; Clear ranking (1-5). Agents should invoke it when users ask about prioritize features or mention triggers defined in the skill frontmatter. Follow the SKILL.md steps, reference files, and output formats rather than improvising outside documented scope.2kinstalls38Growth LoopsThe growth-loops skill evaluates five flywheel types to reduce paid acquisition reliance: viral loops where in-product content spreads externally, usage loops where creations invite new users, collaboration loops where colleagues join shared workspaces, user-generated loops where discovery fuels more creation, and referral loops with explicit incentives. Workflow clarifies core product value, assesses loop fit by product type and sharing habits, designs triggers and conversion mechanics, estimates loop coefficients from invites per cycle and activation rates, and recommends a primary loop with secondary layers over time. Output includes ranked loop evaluation, implementation plan, metrics framework, thirty-sixty-ninety day roadmap, and growth projections. Based on Ognjen Boskovic research emphasizing compounding acquisition through built-in sharing. Use when designing product-led traction, analyzing competitor growth, or optimizing PLG mechanics.2kinstalls39Pestle AnalysisThe pestle-analysis skill helps with Perform a PESTLE analysis covering Political, Economic, Social, Technological, Legal, and Environmental factors. Use when assessing the macro environment, doing strategic planning, or evaluating external factors affecting your business. Key workflows include PESTLE Analysis; Metadata; Instructions; Input Requirements. Documented capabilities cover **Name**: pestle-analysis; **Description**: Perform a PESTLE analysis covering Political, Economic, Social, Technological, Legal, and Environmental factors. Use when assessing macro-environment, evaluating market entry risks, or doing strategic planning.; **Triggers**: PESTLE analysis, macro environment, market environment, external factors analysis; Industry and market context; Geographic market or region(s). Agents should invoke it when users ask about pestle analysis or mention triggers defined in the skill frontmatter. Follow the SKILL.md steps, reference files, and output formats rather than improvising outside documented scope. - **Description**: Perform a PESTLE analysis covering Political, Economic, Social, Technological, Legal, and Environmental factors. Use when assessing macro-environment,.2kinstalls40Stakeholder MapThe stakeholder-map skill helps with Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement. Key workflows include Stakeholder Mapping & Communication Plan; Context; Instructions; Further Reading. Documented capabilities cover **Power** (High/Low): Their ability to influence decisions, resources, or outcomes; **Interest** (High/Low): How much the project directly affects them or how engaged they are; Communication frequency (daily, weekly, bi-weekly, monthly); Communication format (1:1, email, Slack, meeting, dashboard); Key messages and framing. Agents should invoke it when users ask about stakeholder map or mention triggers defined in the skill frontmatter. Follow the SKILL.md steps, reference files, and output formats rather than improvising outside documented scope. You are helping build a stakeholder map for **$ARGUMENTS**. If the user provides files (org charts, project briefs, team rosters), read them first. If they describe the product or initiative, use that context to i.2kinstalls41Interview ScriptThe interview-script skill from phuryn pm-skills produces structured customer interview guides for continuous discovery Stage 1 (Explore). It follows The Mom Test: ask about past behavior, avoid pitching, and surface real jobs-to-be-done rather than opinions. The script includes Opening (2-3 min purpose and recording consent), Warm-Up context questions, Core Exploration JTBD probes on last-instance behavior, pain points without leading, and wrap-up. It positions interviews alongside analytics, surveys, and SEO analysis as discovery inputs and expects Product Trio collaboration (PM, designer, engineer). Agents clarify research objectives, decisions the research informs, and assumptions to validate before drafting. Users may supply personas, hypotheses, or prior notes. Use when preparing user interviews, discovery guides, or JTBD customer research scripts.2kinstalls42North Star MetricThe north-star-metric skill helps teams pick a single customer-centric North Star Metric (NSM) plus 3-5 supporting input metrics. NSM is not revenue/LTV, not multiple KPIs, and not an OKR by itself, but a leading indicator of customer value and long-term success. Step 1 classifies the business game: Attention (time spent), Transaction (platform transactions), or Productivity (work efficiency). Step 2 proposes an NSM meeting seven criteria including easy to understand, measurable, customer-centric, and actionable. Includes NSM 101 PDF reference and triggers on north star, key metric, metrics framework, and OMTM. Use when defining company metrics frameworks, evaluating NSM candidates, or setting up growth measurement systems.2kinstalls43Outcome RoadmapThe outcome-roadmap skill helps product managers transform feature lists into outcome-focused roadmaps that communicate strategic intent. It gathers the current roadmap and optional strategy context, then for each initiative asks what customer problem is solved and which business metric improves. Initiatives rewrite into Enable [segment] to [customer outcome] so that [business impact] statements with measurable success indicators. The workflow contrasts output examples such as build advanced search filters with outcomes like enable customers to find products fifty percent faster. Output includes transformed quarters, key metrics, dependencies, alignment notes, assumptions, and flexible release windows. It encourages asking so what until real value appears and saves substantial results as Outcome-Roadmap markdown files. Use when shifting roadmaps from deliverable lists to results teams can execute flexibly.2kinstalls44Brainstorm Experiments NewThe brainstorm-experiments-new skill helps teams validate new product concepts using lean startup pretotypes instead of large builds. It forms XYZ hypotheses in the format at least X percent of Y will do Z, then proposes two or three low-effort experiments such as landing pages, explainer videos, email campaigns, pre-orders, waitlists, or concierge MVPs. Principles follow Alberto Savoia with skin-in-the-game commitment over stated interest and Your Own Data collection instead of relying on market reports alone. Each experiment specifies the hypothesis tested, method, metric, and success threshold. Agents read any supplied research or mockups first, think step by step, and save substantial output as markdown. Use when validating new product ideas, designing pretotypes, or testing market demand before engineering investment.1.9kinstalls45Prioritization FrameworksThe prioritization-frameworks skill helps with Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates - RICE, ICE, Kano, MoSCoW, Opportunity Score, and more. Use when selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work. Key workflows include Prioritization Frameworks Reference; Core Principle; Opportunity Score (Dan Olsen, *The Lean Product Playbook*); ICE Framework. Documented capabilities cover **Current value** = Importance × Satisfaction; **Opportunity Score** = Importance × (1 − Satisfaction); **Customer value created** = Importance × (S2 − S1), where S1 = satisfaction before, S2 = satisfaction after; **I** (Impact) = Opportunity Score × Number of Customers affected; **C** (Confidence) = How confident are we? (1-10). Accounts for risk.. Agents should invoke it when users ask about prioritization frameworks or mention triggers defined in the skill frontmatter. Follow the SKILL.md steps, reference files, and output formats rather than improvising outside documented scope.1.9kinstalls46Value Prop StatementsThe value-prop-statements skill turns existing value propositions into targeted statements for marketing, sales, and onboarding contexts. Each statement must address a specific segment or use case, emphasize primary benefits and desired outcomes, and highlight enabling features with clear compelling language. The prompt includes a Canva example framework showing statements for social media marketers, small business owners, and content creators with segment-specific pain points and outcomes. Tips request existing value props, target segments, pain points, differentiators, distribution channels, and brand voice guidelines. Use when writing marketing copy, sales messaging, onboarding messages, or segment-specific positioning rather than generic taglines.1.9kinstalls47Identify Assumptions NewThe identify-assumptions-new skill extends Teresa Torres four core risks with ethics, go-to-market, strategy and objectives, and team categories for new venture evaluation. Agents read provided business plans, think from product manager, designer, and engineer perspectives about failure modes, list assumptions per category, rate confidence, and suggest tests. It assumes most ideas will not perform as hoped and outputs markdown assumption maps. Categories span value, usability, viability, feasibility, ethics, GTM channels and timing, strategic macro factors, and team composition risks. Use when evaluating startup risks, assessing new product concepts, or mapping assumptions before prioritization and experiments.1.9kinstalls48Summarize InterviewThe summarize-interview skill transforms customer interview transcripts into structured discovery summaries for product teams. Users provide transcripts as files or pasted text; agents read attachments first, then fill a template with date, participants, background, current solution, likes, problems (each as JTBD with importance and satisfaction), key insights with quotes, and dated action items with owners. Language should be clear enough for a primary school graduate. Output saves as markdown in the user workspace. It complements interview-script (preparation) and supports continuous discovery synthesis after Explore-stage interviews. Use when processing interview recordings, synthesizing discovery interviews, or creating interview summary documents.1.9kinstalls49Sql QueriesThe sql-queries skill from phuryn pm-skills turns business questions into SQL for product managers, analysts, and engineers. Step 1 reads schema files, SQL dumps, or diagram descriptions to extract tables, columns, keys, and relationships. Step 2 clarifies required data, SQL dialect, filters, and aggregations. Step 3 writes efficient SQL with comments, performance notes, and alternatives for large datasets. Step 4 explains logic in plain English with validation and optimization tips. Supports BigQuery, PostgreSQL, MySQL, Snowflake, and SQL Server. Use when writing SQL, building data reports, exploring databases, or translating natural language analytics questions into queries.1.9kinstalls50Prioritize AssumptionsThe prioritize-assumptions skill triages assumption lists using impact defined as opportunity score times customers affected and risk as one minus confidence times effort. Matrix quadrants defer low-low items, implement high-impact low-risk bets, reject low-impact high-risk ideas, and experiment on high-high cells. ICE and RICE references tie to related prioritization-frameworks skill for formula details. For test-worthy assumptions agents propose experiments maximizing learning with behavioral metrics and clear thresholds. Output is a prioritized table or matrix saved as markdown when substantial. Use when triaging assumptions, deciding what to test first, or applying the assumption prioritization canvas after identification steps.1.9kinstalls51Porters Five ForcesThe porters-five-forces skill conducts structural industry analysis across rivalry intensity, supplier bargaining power, buyer power, substitute threats, and new entrant barriers. For each force agents document high versus low conditions, strategic implications, and defensibility recommendations. Inputs include industry definition, competitor landscape, supplier and customer concentration, and product specifics. Output evaluates profitability dynamics and competitive positioning levers such as differentiation or cost leadership. Triggers include Porter five forces, industry analysis, and competitive dynamics requests. Use when assessing market attractiveness, evaluating entry strategy, or framing competitive strategy documents before major investments.1.9kinstalls52Analyze Feature RequestsThe analyze-feature-requests skill groups customer asks into themes, scores strategic alignment, and prioritizes top three features by impact, effort, risk, and vision fit. It rejects letting customers design solutions, prioritizing opportunities over feature lists, and uses Dan Olsen Opportunity Score concepts via related prioritization frameworks. For each top feature agents provide rationale, alternative solutions, risky assumptions, and cheap tests. Inputs may include spreadsheets or CSV exports read directly. Output is markdown or structured tables saved for stakeholder review. Use when triaging backlog requests, reviewing customer feedback lists, or making prioritization decisions against stated product goals.1.9kinstalls53Ansoff MatrixThe ansoff-matrix skill produces growth strategy analysis mapping options across current versus new products and markets. Inputs require current product and market definition, penetration performance, customer insights, capabilities, growth targets, and competitive dynamics. Each quadrant documents strategies and examples: market penetration grows existing product share via retention, upsell, and awareness; market development enters new segments or geographies; product development ships new offerings to current buyers; diversification pairs new products with new markets as highest risk. Agents think step by step through the 2x2 matrix, evaluate feasibility per quadrant, and output actionable growth paths. Triggers include Ansoff matrix, growth matrix, market expansion, and growth strategy options phrases. Use when comparing expansion options, planning market entry, or evaluating strategic growth paths for a product portfolio. 2x2 matrix: current/new product versus current/new market.1.9kinstalls54Gtm MotionsThe gtm-motions skill analyzes go-to-market channel fit across inbound content, outbound sales, paid digital, community, partner, account-based, and product-led growth motions. Each motion lists example tools, tactics, best-fit contexts, strengths, and challenges. Workflow starts from product price point, ACV, sales cycle, buyer persona, and current traction to recommend balanced acquisition mixes. Inbound emphasizes SEO and nurture; outbound covers prospecting stacks; paid targets fast measurable reach; community builds loyalty; partners extend reach; ABM personalizes enterprise accounts; PLG leverages in-product adoption signals. Use when selecting marketing channels, comparing inbound versus outbound, planning cross-channel campaigns, or evaluating PLG versus sales-led approaches.1.9kinstalls55Identify Assumptions ExistingThe identify-assumptions-existing skill devil's advocates feature proposals on live products across four Teresa Torres risk areas: value, usability, viability, and feasibility. Agents read PRDs or designs when supplied, think from PM, designer, and engineer failure perspectives, list specific assumptions with confidence levels, and suggest cheap tests. Tone is constructive strengthening not idea killing. Output captures what could go wrong, confidence high medium low, and validation approaches step by step in markdown. Differs from the new-product variant by focusing on incremental features within an existing user base and shipped context. Use when stress-testing feature ideas, risk assessment, or preparing assumption mapping workshops.1.9kinstalls56Competitive BattlecardThe competitive-battlecard skill builds concise sales-ready battlecards against a named competitor. Workflow researches current product offerings, pricing tiers, positioning, recent launches, strengths, weaknesses, and review sentiment via web search plus any user-provided win/loss files or sales notes. Output sections cover company overview, quick comparison table with capability winners, where we win with proof points, where they win with counter-positioning, landmines to avoid, objection handlers, and customer proof quotes. Agents read uploaded feature lists and call notes first, then validate competitor facts from G2, Capterra, Reddit, and public sources. Use when preparing sales teams, responding to why not competitor X, or refreshing competitive materials before launches. Researches competitor product, pricing, positioning, and recent changes. Quick comparison table with Us/Them/Winner per capability. Where We Win and Where They Win with counter-positioning.1.9kinstalls57Brainstorm Experiments ExistingThe brainstorm-experiments-existing skill helps teams test feature assumptions before full build on live products. Agents clarify the idea and assumptions, suggest experiments per assumption such as first-click tests, fake doors, technical spikes, production A/B tests with mitigation, wizard-of-oz flows, and behavioral surveys. Principles demand measuring behavior not opinions, responsible testing without user or business harm, and maximum learning per effort. Each experiment specifies assumption, method, metric, and success threshold in tables or markdown. Further reading links to Product Compass experiment libraries and assumption canvases. Use when validating feature ideas cheaply on existing products or planning discovery experiments.1.9kinstalls58User SegmentationThe user-segmentation skill analyzes diverse user feedback to identify at least three behavioral and needs-based segments using jobs-to-be-done rather than demographics alone. Inputs include feedback, interviews, support tickets, usage logs, and surveys for a named product. Steps cover data preparation, behavior extraction, needs analysis, clustering, validation for non-overlapping actionable groups, and characterization with representative quotes. Each segment profile documents name, estimated size, behavioral characteristics, journeys, JTBD motivations, pain points, and product implications. Agents think step by step, ensure minimum three segments, and surface hidden customer groups for targeted strategy. Use when segmenting a user base, analyzing mixed feedback, or building a segmentation model from qualitative and quantitative inputs. Identifies minimum three distinct behavioral segments. Uses JTBD, behaviors, and needs instead of demographics alone. Accepts feedback, tickets, logs, interviews, and surveys.1.9kinstalls59Dummy DatasetThe dummy-dataset skill creates test data for demos and development with customizable row counts, column specs, business rules, and output formats. Workflow identifies domain type, defines column generators, selects CSV JSON SQL or executable Python output, applies realistic patterns, validates completeness, and ships runnable scripts when requested. Template Python uses configurable ROWS, column definition maps, and save helpers for CSV export. Example specs cover customer feedback with auto-increment ids, ratings, timestamps, and categorical fields. Agents respect stated constraints and relationships between fields. Use when building mock datasets, populating test environments, or generating sample data for prototypes and QA fixtures.1.9kinstalls60Beachhead SegmentThe beachhead-segment skill helps product teams pick an initial winning market segment for launch and fast PMF validation. It evaluates segments against burning pain (daily frustration, productivity loss, fragile workarounds), willingness to pay, winnable market share, and referral potential that enables adjacent expansion. Use when choosing a first market, targeting initial customers, planning entry strategy, focusing limited resources, or validating GTM assumptions with early adopters. Agents guide structured comparison of candidate segments, surface disqualifiers, and recommend a beachhead with rationale tied to pain intensity and distribution leverage. Output should name the segment, evidence for pain and budget, and expansion path after beachhead wins. Scores segments on burning pain, willingness to pay, winnable share, and referrals Targets first market selection for fast PMF validation and adjacent expansion Evaluates acute unmet problems with costly or fragile current workarounds Supports GTM focus when resources are constrained at launch Structured comparison framework for beachhead vs broader market temptation beachhead-segment identifies the first winning market segment.1.9kinstalls61Job StoriesThe job-stories skill creates backlog items using When situation, I want motivation, so I can outcome format with detailed acceptance criteria focused on user context rather than roles. Process steps identify triggering situations, underlying motivations, desired outcomes, JTBD framing, observable measurable acceptance criteria, and design mockup links. Template includes title as job outcome, description sentence, design link, and six acceptance criteria covering situation recognition, motivation enablement, visible progress, efficient outcome achievement, edge cases, and integrations. Example covers weekly snack spending tracking scenario. Arguments accept product name, feature, design files, and user situation context. Use when writing job stories, JTBD backlog items, or expressing user situations instead of persona-role stories. When/I want/so I can job story sentence format. Acceptance criteria validate outcomes not role behaviors. JTBD focus on situation and motivation over personas.1.9kinstalls62Sprint PlanThe sprint-plan skill helps teams plan a sprint by estimating capacity from team availability and historical velocity, selecting backlog stories against Definition of Ready, mapping dependencies and critical path, and identifying risks with mitigations. Capacity calculation reserves fifteen to twenty percent buffer for bugs, on-call, and unexpected work. Story selection pulls highest priority items, flags items needing refinement, and stops when capacity is reached. Output summary includes sprint goal sentence, duration, team capacity in points, committed stories, buffer remaining, ordered story list with owners and dependencies, and risk mitigations. Agents read user backlogs, velocity data, and prior sprint reports when provided. Use when preparing sprint planning, balancing scope against velocity, or defining the sprint goal. Estimates capacity from availability, velocity, and 15-20% buffer. Selects stories meeting Definition of Ready until capacity fills.1.9kinstalls63RetroThe retro skill runs structured sprint retrospectives that surface insights and produce actionable improvements. It supports Start/Stop/Continue and 4Ls (Liked, Learned, Lacked, Longed For) formats based on team context or user preference. Facilitators read provided sprint data, velocity charts, feedback, or prior retro notes when available. Output includes prioritized action items with owners and deadlines rather than vague themes. Use when running retros, reflecting on sprints, creating action items from team feedback, or learning effective retro facilitation patterns. Start/Stop/Continue and 4Ls retrospective format options Reads sprint data, velocity charts, and prior retro notes when provided Produces prioritized action items with owners and deadlines Structured facilitation rather than unstructured venting sessions Activates for sprint reflection and continuous improvement planning retro facilitates structured sprint retrospectives with actionable improvement items Retro summary with chosen format, insights, and prioritized actions with owners User runs a retro, reflects on a sprint, or needs retro action items Scrum masters and PMs facilitating sprint o1.9kinstalls64WwasThe wwas skill from phuryn pm-skills creates product backlog items using Why-What-Acceptance structure linking strategic rationale, deliverable scope, and testable acceptance criteria. Each item must stand alone with clear user or business value, explicit outcomes, and verifiable conditions rather than task lists. Agents help translate vague feature requests into WWA items suitable for sprint planning and stakeholder review. The format preserves context for why work matters while keeping acceptance testable for QA and engineering. Use when writing structured backlog entries, breaking features into work items, or standardizing item quality before estimation sessions. Why-What-Acceptance format for backlog items. Emphasizes independent, valuable, testable slices. Captures strategic why before what and acceptance. Converts vague requests into sprint-ready items. Supports estimation and stakeholder review quality. Write backlog items in Why-What-Acceptance format as independent, valuable, testable units with strategic context.1.9kinstalls65Draft NdaThe draft-nda phuryn pm-skills skill produces structured non-disclosure agreement drafts with party definitions, confidential information scopes, term length, jurisdiction, and clauses flagged for attorney review. It is not a substitute for licensed legal counsel but accelerates first drafts for partnership discussions. Agents clarify mutual versus one-way NDAs, carve-outs, and return-or-destroy obligations. Use when users need confidentiality agreement starting points before formal legal review. Structured NDA draft with jurisdiction and term sections. Flags clauses requiring licensed legal review. Supports mutual and one-way confidentiality models. Defines information types and carve-outs. Partnership and vendor discussion starting point. Draft a detailed NDA between two parties covering information types, jurisdiction, and clauses needing legal review.1.9kinstalls66Strategy Red Teamstrategy-red-team is an agent skill from phuryn/pm-skills that adversarially reviews PRDs, roadmaps, and strategy documents before polite feedback lets bad plans survive. The skill steelmans then attacks each load-bearing claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest validation experiment plus explicit kill criteria for every assumption. Developers and engineering leads reach for strategy-red-team when stress-testing a plan, pressure-testing a strategy, challenging roadmap assumptions, or preparing a document for executive review. The workflow produces ranked failure modes and actionable test plans rather than generic critique. Trigger phrases include red-team this PRD, pressure-test this strategy, and challenge these assumptions. The skill fits early validate-stage planning when scope decisions still have low reversal cost.994installs67Intended Vs Implementedintended-vs-implemented is a structured audit method packaged as an agent skill for finding gaps between what a system is supposed to do and what the code actually does. The skill defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings that generic linters cannot produce because they lack an intent model. Developers reach for intended-vs-implemented when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase still matches its own documentation. The method targets the class of bugs where code is internally consistent yet violates product or security intent. It fits pre-release reviews, compliance checks, and post-generation validation workflows where requirements live in PRDs, API docs, or permission matrices rather than only in source syntax.912installs68Shipping Artifactsshipping-artifacts is a pm-skills skill that specifies the documentation every AI-built application needs before shipping so reviewers and auditors can understand architecture, trust boundaries, and test coverage. Docs live in `/documentation/` and comprise five core artifacts—architecture.md, flows.md, permissions.md, variables.md, and tests.md—plus up to four conditional files for emails, cron jobs, SEO routes, and embedded agents when those capabilities exist. The flows.md doc maps authz checks and trust-boundary crossings step by step; tests.md is produced by `/derive-tests` and separates existing, proposed, and gap coverage. Core docs are reverse-engineered via `/document-app`. Invoke shipping-artifacts when documenting a vibe-coded codebase, mapping user journeys across trust boundaries, or planning coverage before external review.905installs