phuryn/pm-skills
65 skills70.7k installs802k starsGitHub
Install
npx skills add https://github.com/phuryn/pm-skillsSkills in this repo
1Competitor AnalysisCompetitor Analysis is a PM-oriented agent skill for solo builders who need a structured competitive landscape before naming features or price. You pass a product or idea ($ARGUMENTS) and optional market segment; the agent scopes the market, finds five direct competitors through research, and maps positioning, strengths, weaknesses, and differentiation opportunities. It fits early journey work when you are doing competitive research, preparing a stakeholder brief, or hunting wedge angles—not when specs are already locked. The workflow is step-by-step (scoping → identification → intelligence) and can ingest existing pricing sheets, feature matrices, or customer feedback about rivals. For indie founders wearing strategy and product hats, it turns scattered tabs into one narrative you can reuse in validate and launch messaging without hiring a research firm.1.4kinstalls2Business Modelbusiness-model is an agent skill that walks a solo builder through a complete Business Model Canvas for a product or service argument. You supply target customers, market context, and operating assumptions; the skill produces partner, activity, resource, segment, proposition, channel, relationship, revenue, and cost blocks in standard BMC layout. It fits indie founders who need a shareable one-page model for pricing experiments, pitch prep, or sanity-checking monetization before writing an implementation plan. Unlike a generic brainstorm, it enforces the nine-block framework so gaps in distribution or unit economics surface early. Use it when triggers mention business model canvas, BMC, or documenting how the business makes money.1.3kinstalls3Privacy Policyprivacy-policy is an agent skill that helps solo founders produce a first-draft privacy policy aligned to how their product actually handles data. Product managers and indie builders use it when standing up a landing page, app store listing, or SaaS signup flow and need readable documentation—not a blank template—from structured inputs like company legal name, contact email, and information types collected. The skill emphasizes transparency, jurisdiction awareness, and marking sections that require qualified counsel, which matches how small teams iterate before they can afford full legal packages. It fits early validate work when scope is still fluid and again at launch when policies must match shipped features. Outputs are starting points for attorney review, not filed compliance guarantees. Pair it with your actual data map and subprocessors list so the agent does not invent collection practices you do not perform.1.3kinstalls4Brainstorm Ideas Newbrainstorm-ideas-new is a product-management agent skill for solo founders and indie builders at the very start of a SaaS or app idea. It structures initial discovery: you describe the target segment, opportunity, and outcomes, and the agent confirms the concept then ideates fifteen concrete features—five each from PM (market fit and advantage), Designer (experience and usability), and Engineer (feasibility and architecture)—so brainstorming is not a single generic chat dump. The skill distinguishes initial discovery from continuous discovery on shipped products, which keeps it aligned with validation work before heavy build spend. Attach research or competitive notes when you have them; the agent incorporates those inputs and can search the web for market context. Use when exploring a startup concept or kicking off discovery for a net-new product, then narrow winners into scope, prototypes, or written plans in later journey steps.1.3kinstalls5Summarize MeetingSummarize Meeting is an agent skill from the pm-skills collection that converts meeting transcripts, recordings, or rough notes into crisp, shareable summaries. Solo and indie builders use it after customer discovery calls, scope negotiations, standups, and launch retros when they need one source of truth instead of scrolling a raw transcript. The workflow gathers source material, reasons about who attended and what was decided, then emits structured sections for topic, decisions, summary points, and next steps with owners. It fits the Prism journey wherever alignment and follow-through matter—especially during build and operate—without replacing a live facilitator. Install it when you repeatedly paste call transcripts into chat and want repeatable meeting minutes your agent can file next to specs and tickets.1.3kinstalls6Create PrdCreate PRD is an agent skill that acts as an experienced product manager authoring a Product Requirements Document for a named initiative. It expects you to supply the feature or product topic as arguments, optionally attach files, and lean on web search when you reference research or URLs. Before filling the template, the skill prompts structured thinking about the problem, target users, success measurement, and constraints. The output follows a proven eight-section layout spanning summary, contacts, and the remaining specification blocks called out in the skill body—problem, objectives, segments, value propositions, solution, and release planning—so downstream design and engineering share one source of truth. Solo builders use it when moving from vague idea to buildable spec, when reviewing an existing PRD for gaps, or when they need documentation that leadership can sign off on without a dedicated PM.1.3kinstalls7Product Nameproduct-name is a lightweight branding consultant skill for solo founders who need memorable names without hiring an agency workshop. You pass company and product context via $ARGUMENTS; the agent returns five candidates, each with explicit rationale tied to value proposition, audience, and architecture fit, plus practical domain and trademark considerations. It complements positioning docs from earlier idea work and feeds validate-phase landing tests where the name must survive real-user comprehension. The skill does not register trademarks or buy domains—it equips you to shortlist and debate options inside your agent session. Use when naming a new product, rebranding, or stress-testing names against brand guidelines, especially before you lock repo names, marketing URLs, or app store listings.1.2kinstalls8User StoriesUser Stories is a lightweight product-management agent skill from the pm-skills collection that turns a named feature and design context into implementable backlog items. It expects you to supply the product name, feature scope, design links, and assumptions, then walks a fixed sequence: analyze the feature, identify roles and journeys, apply the 3 C’s (Card, Conversation, Confirmation), enforce INVEST, write in accessible language, and emit a consistent story template with acceptance criteria. Solo founders use it when a Figma frame or prototype exists but Jira-ready wording does not—bridging validate-stage scoping and build-stage execution without hiring a PM. The skill does not replace discovery research; it structures what you already decided to build. Invoke it when writing user stories, breaking down features, creating backlog items, or defining acceptance criteria so agents and humans share the same definition of done.1.2kinstalls9Monetization StrategyMonetization Strategy is a product-management agent skill that runs a structured brainstorm of three to five revenue approaches for your product or feature, not a single default “charge monthly.” It asks for the offer, target segments, willingness to pay, how competitors monetize, and whether you prioritize revenue growth, user growth, or profitability. For each option it names the model, explains who pays and what they receive, surfaces fit and risk, and suggests validation experiments you can run without a full billing build. Solo and indie builders use it when Validate work is stuck on freemium versus tiered SaaS, usage-based API pricing, or services-adjacent models. It pairs naturally with competitive research from Idea and informs Grow analytics once you pick a north-star metric. The output is decision-ready narrative you can paste into a scope doc, pricing page outline, or experiment backlog rather than executable payment code.1.2kinstalls10Sentiment AnalysisSentiment Analysis is a PM-oriented agent skill that ingests real user feedback—CSVs, PDFs, surveys, reviews, or social reports—and walks through a structured research workflow. A solo builder uses it when feedback volume is too big to skim in a spreadsheet and they need defensible segments, not vibes. The agent inventories sources, identifies at least three distinct segments or personas, extracts themes and pain points per segment, and scores overall satisfaction per segment between -1 and +1. Outputs are organized around who is unhappy, why, and what product changes would move sentiment. It fits Grow analytics for ongoing voice-of-customer, but the same pass helps Idea audience discovery and Validate scope when you are still testing positioning against real quotes.1.2kinstalls11Startup CanvasStartup-canvas is a product-management skill that generates a Startup Canvas for new products: the nine strategy sections from Huryn’s Product Strategy Canvas paired with cost structure and revenue streams. Solo founders use it when a Business Model Canvas feels blurry—no vision line, weak competitive moat test, or missing metrics—and Lean Canvas problem boxes overlap segments without forcing trade-offs. The skill is invoked via triggers like startup canvas and new product strategy, and it produces a single structured artifact suitable for validation conversations, pricing hypotheses, and scope gates before implementation. It does not replace quantitative market research or automated financial modeling; it gives language and section prompts so you and your coding agent share one strategic picture. Best after you have a concept worth evaluating and before you write implementation plans or landing copy at scale.1.2kinstalls12Gtm StrategyGTM Strategy is an agent skill that walks a solo builder through creating a full go-to-market plan before or during launch. You supply product description, target segment, competitive landscape, and any validation or customer research; the workflow then pressures-tests marketing channels, shapes messaging that matches each audience, and ties the plan to measurable success criteria and a realistic launch timeline. It fits founders who already have a direction but need a single coherent document instead of scattered notes across Notion and chat. Because it consumes validate-phase research and feeds launch execution and early growth experiments, it is tagged multi-phase with launch/distribution as the primary shelf. Use it when you are planning a product launch, entering a new market, or formalizing go-live from scratch—not when you only need a one-off social post or a technical deploy checklist.1.1kinstalls13Product StrategyProduct Strategy is an agent skill that walks solo and indie builders through a nine-section Product Strategy Canvas when they need a strategic plan, strategy document, or clear product direction. It positions the agent as an experienced strategist for a product you describe, using market context, competitor insights, customer jobs-to-be-done, and company constraints to produce a coherent narrative across vision, segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility. Use it when you are past raw discovery but not yet locked into an implementation roadmap—typically after initial research and before detailed planning or prototyping. The canvas forces problem-defined segments and explicit trade-offs so your agent does not output generic mission statements. Outputs are meant to feed scope decisions, pricing conversations, and later planning skills rather than replace day-to-day PM tooling.1.1kinstalls14Release NotesRelease Notes is an agent skill that transforms technical inputs—tickets, PRDs, changelogs, or git history—into clear, engaging release notes organized by category. Solo builders and indie PMs use it when a sprint ends and they must announce what shipped without sounding like a dump of JIRA titles. The workflow gathers what changed, who it affects, and why it matters, then writes entries that lead with user benefit in one to three sentences per item, including breaking changes and deprecations when users must act. It fits the gap between engineering truth and marketing-readable updates for email, blog, changelog pages, or app store “what’s new” sections. Because it can read attached exports and optionally search the web for product context, it scales down the chore that bigger teams assign to technical writers—while still requiring you to verify accuracy against what actually deployed.1.1kinstalls15Swot AnalysisSwot-analysis is a PM agent skill that runs a full strengths-weaknesses-opportunities-threats review for a product or business line. Solo builders use it when they need discipline beyond gut feel—before committing to a niche, before a pivot, or when preparing positioning for launch and growth conversations. The skill asks for product description, competitive context, company constraints, and market dynamics, then works each quadrant with internal versus external lens and turns findings into recommendations. It is not a financial model or a survey instrument; it synthesizes what you already know into a decision-ready artifact. Because strategic assessment recurs across the journey, the skill is multi-phase even though Prism shelves it under Idea and competitors for discovery-time competitive work. Pair it with customer research or pricing skills when weaknesses touch monetization or distribution gaps.1.1kinstalls16Metrics Dashboardmetrics-dashboard is a product-management agent skill that helps solo and indie builders design a metrics dashboard before implementation. You name the product or initiative, optionally attach OKRs, strategy docs, or existing analytics, and the skill walks through metric selection grounded in Lean Analytics principles—understandable, comparative, ratio-based, and behavior-changing. It distinguishes metrics, KPIs, and a North Star Metric, and balances quantitative reporting with qualitative customer insight. The output is a concrete monitoring plan: which metrics belong on the board, where data comes from, which chart types fit each signal, and sensible alert thresholds so you catch regressions early. Use it when you are setting up product analytics, defining KPIs for a new feature, or replacing a vanity-metrics spreadsheet with something actionable. It does not replace your analytics SDK or warehouse; it gives you the spec your agent or team can implement in Mixpanel, PostHog, or internal SQL dashboards.1.1kinstalls17Brainstorm Ideas ExistingBrainstorm Ideas (Existing) is an agent skill for solo and indie builders who already have a live product and need structured feature ideation instead of ad-hoc brainstorming. It follows continuous discovery habits: a PM–Designer–Engineer trio explores an opportunity for a stated objective, segment, and outcomes, optionally grounded in uploaded research or a product URL. The workflow clarifies the opportunity, generates five ideas per role, then selects the top five for follow-up experiments. It fits early journey work when you are mapping opportunities to solutions on an Opportunity Solution Tree and expect to loop back if experiments fail. Use it when you are generating new feature ideas, brainstorming solutions for a identified opportunity, or ideating explicitly as a product trio—not when you are executing code or shipping a spec that is already locked.1.1kinstalls18Value PropositionValue Proposition is an agent skill that acts as a product strategist for solo builders who need a crisp, testable statement of customer value—not a feature list. It walks through a six-part template grounded in Jobs to Be Done: who the segment is, why the problem matters, the before state, how your product delivers change, the after state, and what customers use instead today. You bring product features, target segment pains, competitive alternatives, and any market or interview data; the skill outputs a structured narrative you can reuse on landing pages, pitch decks, and positioning docs. It sits in Validate because it de-risks build and launch work by making tradeoffs explicit. Use it when creating a value proposition, analyzing how you deliver customer value, or articulating why buyers should pick you over incumbents and DIY workarounds.1.1kinstalls19Marketing IdeasMarketing Ideas is an agent skill that acts as a lightweight product-marketing partner for solo builders who need concrete promotion options without hiring an agency. You supply product and market context; the skill returns five creative, cost-conscious campaign concepts, each broken down by primary channel (social, content, partnerships, community, email, and similar), a resonant core message, why the approach should engage the target audience, and what keeps the tactic cheap or lean. It fits early launch planning, refreshes when growth stalls, and supports validate-phase messaging experiments on landing pages. The workflow is prompt-driven rather than API-integrated, so it pairs well with brainstorming and positioning skills upstream and with distribution or content execution skills downstream. Intermediate complexity assumes you can describe your product, segment, and constraints clearly.1.1kinstalls20Ideal Customer ProfileIdeal Customer Profile is a product-management agent skill that converts research and PMF survey data into a structured ICP: demographics, behaviors, jobs-to-be-done, and needs. Solo founders use it when they must decide who actually gets value from the product—not every persona slide in a deck—before scoping an MVP, sharpening positioning, or saying no to bad-fit leads. It is procedural synthesis, not a data pipeline; you bring interviews, survey exports, or success patterns and receive a prioritizable profile for product, sales, and marketing. On Prism it shelves under Idea → audience as the primary placement, with natural reuse in Validate when scoping and in Grow when aligning lifecycle and content to the same segment. Pair it with other pm-skills when you move from “who” to roadmap or messaging artifacts.1.1kinstalls21Pricing StrategyPricing Strategy is a PM-focused agent skill for solo founders and indie builders who must decide how to charge before wiring Stripe or shipping tiers. It lives on the validate phase pricing shelf as the primary home for model selection, competitive scans, and elasticity thinking, but the same reasoning resurfaces when you adjust prices at launch or in grow. The workflow starts from your product context in $ARGUMENTS, ingests any files you attach, and can use web search for competitor pricing. You work through value delivery, alternatives, measurable outcomes, then evaluate models from flat-rate through freemium with explicit best-for guidance. That structure keeps agents from jumping straight to arbitrary monthly numbers. Use it when setting initial prices, planning a pricing change, or debating freemium versus paid. Outcomes are a defensible strategy narrative and model recommendation you can turn into landing copy, plans, and billing configuration in later phases.1.1kinstalls22User PersonasUser Personas is a product-research agent skill for solo founders who already have raw evidence—surveys, interviews, or spreadsheets—and need credible segments instead of generic “marketing Mary” cards. It instructs the agent to think step by step: ingest data, spot recurring motivations and pains, cluster users, enrich narratives, and cross-check that each persona is grounded in patterns rather than stereotypes. The output target is three distinct personas with jobs-to-be-done, pain points, desired outcomes, and non-obvious insights that can inform roadmap calls, landing copy, and validate-stage scoping. It does not replace collecting research; it compresses synthesis so you can move from messy responses to decision-ready profiles in one guided pass. Best used when you are naming a product or market in $ARGUMENTS and attaching real files or notes for the agent to analyze.1.1kinstalls23Brainstorm OkrsBrainstorm OKRs is an agent skill for solo builders and small teams who need quarterly goals that are ambitious, measurable, and aligned with company strategy. It walks you through the OKR model from Radical Focus—qualitative objectives paired with a small set of quantitative key results—and produces three alternative OKR bundles so you can compare tradeoffs before committing. The skill also clarifies how key results may reuse KPIs, how health metrics balance OKR risk, and how a North Star metric fits the stack without replacing OKRs. Use it when you are setting quarterly OKRs for the first time, realigning a team after a pivot, or teaching yourself how to write objectives that executives can actually track. It is planning prose and structure, not an integration; you bring the company context via $ARGUMENTS and approve the final set in your own doc or tracker.1.1kinstalls24Positioning IdeasPositioning Ideas is a brand-strategy agent skill from the pm-skills collection that turns rough product and market context into competitor-grounded positioning options. A solo builder installs it when they know what they want to build but cannot articulate how they differ from incumbents on a landing page, pitch deck, or pricing page. The agent acts as an experienced strategist: first it identifies and summarizes the top five competitors—their positioning angle, audience focus, emphasized differentiators, and gaps they leave open—then it produces five unique positioning ideas aimed at your stated market segment, each with rationale you can test in copy and offers. Use it while researching the category, while validating positioning before a prototype, or whenever differentiation triggers appear in chat. It does not replace customer interviews or analytics; it accelerates structured ideation so you commit to a direction with eyes open. Pair the output with scope and messaging work on your validation shelf.1.1kinstalls25Grammar Checkgrammar-check is a copyediting agent skill for solo builders who write investor updates, landing copy, docs, emails, and social posts without a human editor on retainer. You supply an objective (what the text must achieve) and the draft; the skill acts as an expert copyeditor that flags grammar, logical, and flow problems and proposes specific repairs rather than replacing your voice wholesale. Step one anchors purpose and audience—marketing versus technical, formal versus friendly—so fixes match intent. Step two systematically hunts spelling and punctuation issues, tense drift, contradictory claims, weak cause-and-effect, and choppy transitions. Use it when a draft is structurally done but not ready to publish, when English is a second language, or when agent-generated prose needs a disciplined second pass. It pairs naturally with planning and docs skills but does not replace fact-checking or legal review.1.1kinstalls26Lean CanvasLean-canvas is a Productivity & Planning agent skill for solo and indie builders who need a fast, repeatable business-model snapshot instead of a lengthy business plan. Invoked when exploring a lean startup canvas, testing a business hypothesis, or modeling a new venture, it walks the agent through problem, solution, unique value proposition, unfair advantage, customer segments, channels, revenue streams, cost structure, and key metrics. The skill expects a product or feature description, target segments, and whatever market context you already have, then outputs a comprehensive canvas aligned to standard lean methodology. It fits the Validate phase when you are deciding what to prototype or price, and remains useful in Idea when reframing opportunity after competitor research. Pair it with downstream planning or prototyping skills once hypotheses are explicit enough to test with users or landing pages.1.1kinstalls27Product VisionProduct Vision is a veteran-PM-style agent skill that brainstorms a product vision for your company and offering using workspace context you provide. Solo and indie builders use it when defining a vision for the first time, reframing after a pivot, or re-aligning stakeholders who have drifted from the north star. The skill asks how you inspire people, what you aspire to achieve, and which values you uphold, then outputs a statement that motivates teams while staying realistic about resources, market, and capabilities. It complements scope and roadmap work rather than replacing competitive research or financial modeling. Invoke it early in the journey or whenever strategy shifts and you need shared emotional meaning—not only a feature list—before committing to validate-phase scope or build-phase plans.1.1kinstalls28Ab Test Analysisab-test-analysis is an agent skill that walks solo builders through rigorous A/B test evaluation so experiment results become clear product calls instead of noisy dashboard reads. You install it when you need to check whether a test reached significance, interpret control versus variant performance, or decide whether to ship a change. The workflow starts by clarifying hypothesis, variant, primary metric, guardrails, duration, and traffic split, then stress-tests the setup with sample-size and power checks (including underpowered flags below 80% power), business-cycle duration, sample ratio mismatch, and novelty or primacy effects. It calculates conversion rates, statistical significance, and confidence intervals, optionally generating Python for the math when you attach exports. The outcome is an actionable recommendation—ship, extend the test, or stop—with reasoning tied to statistical rigor rather than vanity metrics. It fits SaaS, content, and ecommerce builders who run growth experiments without a dedicated data team.1.1kinstalls29Pre MortemPre-mortem is an agent skill that runs a structured pre-launch risk analysis on a PRD, product plan, or launch brief. A solo builder or small team installs it when they have a concrete plan but need a disciplined way to ask what would make the launch fail—adoption, revenue miss, or reputation damage—while there is still time to fix scope, messaging, or execution. The workflow gathers and reads the plan, optionally researches context, then applies a veteran-PM pre-mortem: assume failure 14 days post-launch, surface missed execution and hidden worries, and sort findings into Tigers (legitimate threats), Paper Tigers (overblown fears), and Elephants (unspoken team concerns). Outputs are prioritized by launch-blocking, fast-follow, and track so you know what must be resolved before ship versus what to monitor after. It fits Validate when stress-testing a product plan early and Ship when doing final launch prep, without replacing legal review, security audits, or quantitative forecasting.1.1kinstalls30Test ScenariosTest Scenarios is a procedural agent skill for solo and indie builders who need disciplined QA documentation instead of vague “make sure it works” notes. You supply a product name, a user story with acceptance criteria, and optional testing constraints; the skill walks through objectives, system preconditions, roles, granular interaction steps, observable outcomes, and edge cases. It fits the moment you have defined behavior to validate—whether you are tightening acceptance tests during scoping or building a test plan ahead of release. The workflow mirrors how small teams run feature validation without a dedicated QA lead: one repeatable template, one narrative per scenario, and language an agent or human tester can follow. It does not run tests or wire CI; it produces the scenario artifact that makes manual checks, UAT, and later automation design much faster.1.1kinstalls31Market SizingMarket-sizing is an agent skill that walks solo and indie builders through Total Addressable Market (TAM), Serviceable Addressable Market (SAM), and Serviceable Obtainable Market (SOM) using both top-down and bottom-up methods. You invoke it when you need credible opportunity numbers for a pitch, a go/no-go on market entry, or validation that a niche is large enough to justify shipping. The skill defines market boundaries first, then derives TAM from industry scale, cross-validates with unit economics, and scopes SAM and SOM against realistic constraints. It expects you to pass the product or segment as arguments and can ingest reports you already have while supplementing gaps with web research. Outputs emphasize growth projections and assumptions you should test next, which fits the validate phase before heavy build spend. It is planning and research oriented rather than code generation, and pairs naturally with competitor research, pricing, and roadmap skills in a PM stack.1.1kinstalls32Customer Journey MapCustomer Journey Map is a PM-oriented agent skill that walks you through building an end-to-end experience map—from first awareness through advocacy—for a specific persona and product. Solo and indie builders use it when they need to see where users feel confused, stuck, or delighted across onboarding, habitual use, churn risk, and referrals. The workflow starts by defining a concrete persona with JTBD, then adapts standard stages (awareness, consideration, acquisition, onboarding, engagement, retention, advocacy) and documents touchpoints, emotions, pain points, and opportunities at each step. It is especially valuable when you have qualitative or quantitative inputs (interviews, tickets, analytics) but no shared visual model of the journey. Output is structured enough to prioritize fixes in validate-phase landing and scope work, launch messaging, and grow-phase lifecycle experiments without replacing formal analytics or cohort studies.1.1kinstalls33Review Resumereview-resume is an agent skill that acts as an expert Product Management resume reviewer for solo builders and PMs preparing job applications, advisor roles, or investor-facing bios derived from career history. You supply resume text and optionally a job posting; the skill walks through ten best practices—structure, impact framing, keyword alignment, and tailoring—while calling out what already works and what to change with examples drawn from your document. It foregrounds the XYZ+S formula and job-specific optimization so generic PM bullets become measurable outcomes hiring teams can scan quickly. The flow is conversational but systematic: greeting and strengths first, then iterated practice-by-practice critique rather than a vague rewrite. Use it when you are validating whether your narrative matches the roles you want, before you spend cycles on outbound applications or founder recruiting. It does not replace a human coach for executive branding, but it gives indie operators a repeatable pre-flight check aligned to how PM resumes are actually screened.1.1kinstalls34Cohort AnalysisCohort Analysis is a PM and growth agent skill that ingests user cohort datasets and produces quantitative retention and engagement views for solo builders who have real usage data but lack a repeatable analysis ritual. It reads CSV, Excel, or JSON, validates structure and quality, then calculates retention curves, feature adoption by cohort, anomalies, and period-over-period shifts. When asked, it can generate pandas-based analysis scripts and visualization-oriented outputs such as retention heatmaps and line charts comparing cohort progression. The skill also bridges toward qualitative follow-ups—useful when numbers show a cliff but not why. It fits indie SaaS and mobile products post-launch, especially when you export from analytics warehouses, billing, or product DBs. It does not replace a full BI stack; it accelerates structured cohort reviews so you can decide what to fix in lifecycle, content, or product next—often after a customer journey map highlights suspected friction stages.1.1kinstalls35Stakeholder MapStakeholder Map is a PM workflow skill that builds a Power × Interest grid, assigns communication strategies per quadrant, and outputs a practical engagement plan for a named initiative. Solo founders wearing the PM hat use it when a launch, feature, or partnership touches legal, sales, or executives and ad-hoc Slack updates are no longer enough. The agent reads supplied org artifacts or infers stakeholders from the product description, then documents who to manage closely versus keep satisfied or merely informed. It fits Validate scope work before locking milestones, Launch distribution when coordinating a go-to-market, and Build pm when cross-functional dependencies risk silent blockers.1.1kinstalls36Prioritization Frameworksprioritization-frameworks is an agent skill that gives solo builders and indie PMs a single desk reference for nine established prioritization methods—including Opportunity Score, ICE, RICE, Kano, and MoSCoW—with formulas, decision cues, and templates. The SKILL.md anchors on a lean product rule: score problems and opportunities, not feature requests dressed up as solutions, which keeps Validate and early Build conversations honest when everything feels urgent. You reach for it when you are choosing how to rank roadmap items, comparing RICE versus ICE for your stage, or teaching an agent how to structure a prioritization workshop without inventing bespoke math. It is reference material rather than a gated workflow, so it pairs well with discovery notes and spec drafts across multiple journey phases. The outcome is a defensible scoring model and shared vocabulary so you commit engineering time to high-importance, low-satisfaction needs instead of loudest-customer features.1kinstalls37Market SegmentsMarket Segments is an agent skill for product-minded solo builders who need structured segmentation instead of a vague “everyone” target. It walks you through exploring the addressable market for your product idea, choosing segmentation dimensions (behavioral, demographic, firmographic, needs-based), and defining three to five distinct segments with characterization and opportunity assessment. Invoke it when you are exploring markets, evaluating new audiences, or learning how to segment before you prototype or write positioning. The skill expects you to supply a product or idea context via arguments and optionally attach research or existing segmentation notes for the agent to synthesize. Output is analysis-ready segment profiles you can feed into validation (landing copy, pricing hypotheses) and later growth work—without replacing quantitative survey work or live customer interviews.1kinstalls38Interview Scriptinterview-script helps solo founders and indie PMs prepare customer discovery that actually changes what they build. It generates a structured interview guide for research you define, grounded in The Mom Test: no leading questions, no pitching, and questions aimed at past behavior instead of hypothetical enthusiasm. The skill expects you to clarify what the team must learn, which decisions the research supports, and which assumptions need validation—then it outputs scripted sections including a short opening, warm-up, core exploration with JTBD-style probing, and wrap-up. It explicitly connects to continuous discovery’s Explore stage and recommends the Product Trio (PM, designer, engineer) work together rather than outsourcing interviews to proxies. When you attach personas, hypotheses, or briefs, the agent reads them first so questions stay tied to your product context. Use it before user calls during Idea and early Validate work when you need repeatable interview quality without hiring a research agency. Outputs are conversation-ready scripts you can run in Calendly-booked calls or hallway tests with early adopters.1kinstalls39Pestle Analysispestle-analysis is an agent skill that walks a solo builder through a full PESTLE macro-environment review for a defined industry, geography, and product context. You invoke it when external forces—not feature lists—could make or break market entry, pricing, or roadmap priorities. The skill frames the agent as a strategic analyst, lists required inputs such as region and known regulatory shifts, and works through six categories with concrete sub-questions so political incentives, economic headwinds, social trends, technology adoption, legal obligations, and environmental pressures show up in one narrative. It fits indie operators who need consultant-grade structure without a strategy deck budget, especially before validation spend or when re-checking assumptions after policy or market shocks. Output is planning-grade insight you can fold into positioning, risk registers, and go/no-go notes—not automated data feeds.1kinstalls40Brainstorm Experiments NewBrainstorm-experiments-new is a PM agent skill that designs lean startup experiments for brand-new products. When a solo builder has a concept but no traction data, the skill turns $ARGUMENTS into a clear XYZ hypothesis and two or three pretotypes—landing pages, videos, email tests, waitlists, or manual concierge delivery—that measure real interest without a full build. It fits the Validate phase when you are deciding scope and whether demand exists, and it also helps in Idea when you are comparing concepts before picking one. The workflow expects optional files such as research notes or landing mocks so the agent grounds experiments in what you already know. Complexity stays beginner-friendly: outputs are decision-ready experiment briefs, not statistical models. Use it when validating a new product idea, creating pretotypes, or testing market demand—the same triggers named in the skill frontmatter.1kinstalls41Prioritize FeaturesPrioritize Features helps solo founders and product-minded builders turn a long idea list into an ordered short list grounded in outcomes, not gut feel. You describe the product objective, success metrics, and feature candidates—or attach a backlog file—and the agent walks through confirming priorities, evaluating impact against desired outcomes, effort, risk, and strategic fit, then surfaces the top five features to pursue. The skill explicitly favors prioritizing customer problems via Opportunity Score, with ICE/RICE called out for initiative-level scoring when reach and confidence matter. It fits Validate when you must narrow MVP scope, and Build PM moments when the backlog outgrows sprint capacity. Pair with a frameworks reference skill when you need textbook definitions; this skill is the execution playbook that ends in ranked recommendations you can feed into writing-plans or implementation tasks.1kinstalls42Sql QueriesSQL Queries is an agent skill that generates optimized SQL from natural language for product managers, solo founders, and analysts who need trustworthy data pulls without hand-writing every join. It ingests schema context from files or descriptions, confirms dialect and filters, then outputs commented queries plus plain-English logic and validation hints. Use when writing SQL, building reports, exploring a database, or turning a business question into a query across BigQuery, PostgreSQL, MySQL, or Snowflake. It fits the Grow phase for analytics and recurring metrics, but also supports Build when defining metrics and Operate when investigating production data issues.1kinstalls43Growth LoopsGrowth Loops is a product-management agent skill for solo and indie builders who want traction that compounds instead of resetting every month. It walks you through five proven flywheel patterns—viral, usage, collaboration, user-generated content, and referral—so you can see which mechanism actually fits your product’s natural user behavior. The skill is meant for moments when you are designing growth into the product, trying to rely less on paid acquisition, or reverse-engineering how competitors seem to grow organically. It connects user-created value inside the app to discovery on external channels, with realistic notes on when sharing incentives and shareable artifacts are strong or weak. You do not need a growth team; you need a clear loop hypothesis you can implement in onboarding, sharing flows, and core workflows. Use it alongside positioning and roadmap work so loops reinforce what users already want to do, not gimmicks bolted on at launch.1kinstalls44Opportunity Solution TreeOpportunity Solution Tree is a journey-wide agent skill that teaches solo builders Teresa Torres’ OST framework for continuous product discovery. Instead of debating features in chat, you anchor on one desired outcome, list customer opportunities discovered through research, branch possible solutions, and attach experiments that de-risk bets before implementation. The skill explains how to phrase opportunities from the customer’s perspective and prioritize them with Dan Olsen’s Opportunity Score so you focus on important, unsatisfied needs. It is ideal whenever you are structuring discovery, mapping problems to solutions, or choosing the next slice of work—but it pays off earliest in validate and scope when the cost of building the wrong thing is highest. Indie founders wearing PM hats can use the same tree across idea research, validation prototypes, and build-phase course corrections without adopting enterprise process overhead. The output is a visual, decision-ready discovery artifact your coding agent can turn into plans, prototypes, or experiment backlogs.1kinstalls45Summarize InterviewSummarize-interview is a product-management agent skill that converts customer interview transcripts into a consistent discovery summary for a named product or initiative. Solo and indie builders use it when they have recordings or notes from discovery calls and need Jobs-to-Be-Done framing, satisfaction signals, and follow-up actions without re-reading hours of dialogue. The workflow expects you to supply the transcript (file or paste), read it end-to-end, then populate a structured template that separates what works in the current solution from concrete problems and outcomes. It emphasizes clarity over jargon so stakeholders and future-you can scan the output quickly. It fits early journey work when you are still validating who the customer is and what they hire your product to do, and it pairs naturally with broader PM skill packs on the same repo for specs and roadmaps.1kinstalls46Outcome RoadmapOutcome-roadmap is an agent skill for product managers and solo builders who still publish roadmaps as feature lists and backlogs. It walks through gathering the current roadmap (and strategy context when available), then reframes every initiative as an outcome statement: the customer problem solved, the experience change, and the business metric expected. That matches how modern product orgs avoid output theater—teams know what success looks like without being locked to a single solution shape. Use it when you are moving to outcome-based planning, preparing exec or board updates, or cleaning up a roadmap before engineering commitment. The skill is procedural PM coaching in SKILL.md form, not a template generator alone; it emphasizes thinking step by step per item. It fits SaaS and content products where roadmaps must communicate strategic intent to engineering, marketing, and leadership at once.1kinstalls47Dummy DatasetDummy-dataset is a generator skill for solo builders who need believable test data without hand-rolling hundreds of rows. You specify product context, dataset type, optional row count, columns, output format, and constraints; the agent follows a seven-step flow from domain understanding through column specs, realistic distributions, relationship rules, and final export as CSV, JSON, SQL, or a Python script you can rerun. It supports common PM and engineering fixtures—feedback tables, transactions, user profiles—and stresses valid, authentic-looking values rather than lorem ipsum placeholders. Use it while implementing APIs, dashboards, or demo environments, and again during ship-phase testing when you need repeatable seeds. The skill is procedural generation guidance in SKILL.md form, ideal for populating local databases, staging snapshots, or conference demos where schema shape must respect business logic.1kinstalls48Value Prop StatementsValue Proposition Statements is an agent skill for solo builders who already have value proposition work done and need sharp, channel-ready sentences without rewriting strategy from scratch. It generates comprehensive statements tailored to segments or use cases, each tying outcome, benefit, and capability in language suited for landing heroes, sales slides, lifecycle email, and onboarding modals. Invoke it when promotional copy feels generic, when pitch decks need parallel bullets per ICP, or when onboarding must mirror the same promise as ads. The skill does not invent positioning from zero—it amplifies structured value props into execution-ready messaging, which keeps validate and launch artifacts aligned. It is a generator-style workflow with clear creative constraints so agents produce consistent voice across touchpoints while you stay the editor on brand tone and claims.1kinstalls49North Star MetricNorth Star Metric is a product-management agent skill that walks solo and indie builders through choosing one North Star Metric and three to five supporting input metrics that form a coherent metrics constellation. It classifies which “game” your product plays—Attention, Transaction, or Productivity—and stress-tests candidates against seven criteria so the NSM stays customer-centric and predictive rather than a vanity revenue line. Use it when you are standing up a metrics framework, debating what to optimize in analytics tooling, or sanity-checking dashboards before launch. The skill clarifies common confusions (NSM is not an OKR, not multi-metric soup, not LTV-as-primary) and pairs naturally with goal-setting elsewhere via expected NSM movement. It fits early validation when scope is still fluid and again in growth and operate phases when you refine instrumentation and iteration priorities.1kinstalls50Gtm MotionsGTM Motions is a product-marketing skill that helps solo founders and indie PMs choose how to acquire customers without defaulting to a single channel. It structures seven proven motions—inbound content and SEO, outbound prospecting, paid digital, community-led growth, partner channels, account-based marketing, and product-led growth—and pairs each with representative tools and tactics. You use it when picking inbound versus outbound emphasis, deciding if PLG fits your product, or assembling a balanced GTM stack before spend ramps. The overview frames evaluation criteria so agents can recommend motions aligned with sales cycle length and buyer intent rather than trend-chasing. It is planning and research oriented: it does not execute campaigns, write ads, or configure HubSpot workflows. Pair it with landing, pricing, and analytics skills once you commit to a motion mix.1kinstalls51Identify Assumptions Newidentify-assumptions-new is an agent skill that helps solo and indie builders stress-test a new product before they code. You describe the concept, target segment, and feature idea; the skill reads any files you attach, then walks a structured workflow to list what must be true for the venture to work. It extends Teresa Torres’s four familiar product risks—Value, Usability, Viability, and Feasibility—with Ethics, Go-to-Market, Strategy & Objectives, and Team, because greenfield ideas fail as often on distribution and team fit as on UX. Instructions ask the agent to reason like a PM (demand, willingness to pay, competition), a designer (onboarding and first-run experience), and an engineer (build vs buy, scale, debt). The output is a categorized assumption map you can use to design cheap tests, narrow MVP scope, and avoid baking unvalidated bets into the backlog. Use it when evaluating startup risk, assessing a new product concept, or preparing assumption tests during validation—not as a substitute for customer interviews or quantitative experiments.1kinstalls52Porters Five ForcesPorter's Five Forces is an agent skill that walks a solo builder through Michael Porter's structural industry model: competitive rivalry, supplier bargaining power, buyer power, threat of substitutes, and threat of new entrants. You supply an industry or market definition plus context on competitors, suppliers, customers, and product specifics; the skill evaluates how those forces squeeze margins and shape strategy. It fits early journey work when you are deciding whether to enter a space, how differentiated you must be, and where pricing power might live—without replacing primary customer research or financial modeling. Use it when triggers mention Porter's five forces, competitive dynamics, or market attractiveness. Pair it with audience research and validation skills so structural analysis informs scope and pricing rather than substituting for talking to users.1kinstalls53Brainstorm Experiments Existingbrainstorm-experiments-existing is a product-management agent skill for solo founders and indie builders who already have something in market and need disciplined validation before expensive engineering. You describe the idea, assumptions, and optionally attach PRDs or assumption lists; the skill walks through clarifying what must be true, then proposes low-effort experiments per assumption—first-click tests, feature stubs, technical spikes, wizard-of-oz flows, behavioral surveys, and controlled A/B tests with explicit risk notes for production. It encodes lean experimentation: learn from what users do, protect users and the business during live tests, and avoid baking unvalidated bets into the roadmap. It is not a analytics dashboard or experiment platform; it produces an experiment design conversation you can execute with your existing stack. Use it when a feature sounds reasonable on paper but assumptions about adoption, comprehension, or technical feasibility still need cheap proof.1kinstalls54Analyze Feature RequestsAnalyze Feature Requests is a product-management agent skill for solo and indie builders who receive feature ideas from customers, support, or sales and need a disciplined way to prioritize without letting loud voices design the roadmap. You confirm the product goal, cluster requests into themes, assess strategic alignment, then rank the top options using impact, effort, and risk while keeping focus on problems rather than prescriptive solutions. It pairs with the prioritization-frameworks skill for Opportunity Score detail and templates. Use it when reviewing inbound requests, cleaning a backlog before a sprint, or preparing prioritization decisions for stakeholders. The workflow produces themed groups and a justified top-three shortlist anchored to outcomes you already care about.1kinstalls55Competitive BattlecardCompetitive Battlecard is an agent skill for solo founders and small sales motions who need a focused one-pager against a single named competitor. It instructs the agent to research the rival via web search—product, pricing, positioning, recent changes, and public sentiment—then merge that with any files you supply like win/loss notes or internal feature lists. The deliverable follows a fixed outline: company overview, a capability matrix with explicit winner columns, differentiated win themes, and material suited to objection handling in calls. Use it when a prospect names an alternative, before onboarding a part-time seller, or when refreshing positioning after a competitor launch. It does not replace full market sizing or legal competitive claims review; it accelerates consistent, research-backed talk tracks for indie SaaS and product-led builders who wear both PM and sales hats.1kinstalls56Job StoriesJob Stories is a product-management agent skill that helps solo builders and tiny teams express backlog work in Jobs-to-be-Done language instead of brittle role-centric user stories. You supply the product, feature, design references, and situational context; the skill walks through identifying triggering situations, underlying motivations, desired outcomes, and acceptance criteria that prove the outcome was achieved. That structure fits early validation when you are narrowing scope, and it remains useful during Build when breaking epics into implementable items agents or contractors can execute against linked Figma or Miro designs. The output is implementation-ready narrative plus criteria, keeping agents focused on user context rather than fictional personas.1kinstalls57User SegmentationUser Segmentation is an agent skill that analyzes diverse qualitative and behavioral inputs to surface at least three distinct customer segments grounded in jobs-to-be-done, motivations, and unmet needs. Solo builders drowning in mixed feedback—from Discord, support tickets, or early surveys—use it when demographic labels fail to explain who actually gets value from the product. The SKILL.md prescribes a five-step chain from data preparation through clustering and validation, emphasizing coherent, non-overlapping groups rather than vanity personas. It fits Grow when you refine lifecycle and positioning, and it remains valuable earlier when scoping Validate or clarifying Idea-stage audience hypotheses from the same data. Deliverables are named segments with behavioral signatures you can tie to roadmap bets and copy tests. It does not replace quantitative cohort SQL; it structures narrative and qualitative evidence for agent-assisted PM work.1kinstalls58Ansoff MatrixAnsoff Matrix is a growth-strategy agent skill that produces a structured expansion analysis for whatever business context you pass in arguments. Acting as a growth strategist, it expects you to supply current products and markets, penetration performance, customer insight, capability constraints, growth targets, timelines, and competitive dynamics—then it walks the classic 2×2 grid of market penetration, market development, product development, and diversification. Each quadrant gets evaluated with actionable strategy themes rather than generic labels, so a solo founder can compare lower-risk depth in the current market against higher-risk new-market or new-product moves. The skill fits early strategic conversations when you are weighing where the next revenue increment should come from, as well as later lifecycle moments when you are planning geographic, segment, or SKU expansion. Output is decision-ready narrative you can attach to a roadmap memo, investor update, or validate-phase scope doc, replacing one-off brainstorming with a repeatable framework consultants use for corporate strategy—scaled for indie operators who still need explicit tradeoffs between focus and diversifica1kinstalls59Identify Assumptions ExistingIdentify Assumptions (Existing Product) is an agent skill for solo builders and small PM teams who already have a product and want to pressure-test a new feature before it lands on the roadmap. You describe the product context, objective, segment, and feature idea; the skill reads any attached PRDs or designs, then works through PM, design, and engineering perspectives to list what must be true for the feature to succeed. Assumptions are bucketed into Value, Usability, Viability, and Feasibility so you can prioritize discovery, usability tests, GTM checks, and technical spikes. It fits the Validate phase when scoping incremental work, and still helps in Idea when comparing feature bets or in Build when a spec needs explicit risks written down. Outputs are structured assumption lists you can feed into experiments, PRDs, or assumption-mapping workshops—not a go/no-go verdict by itself.1kinstalls60Prioritize AssumptionsPrioritize Assumptions is a product-management agent skill from phuryn/pm-skills that triages a backlog of beliefs about your product using an Impact × Risk matrix and proposes experiments for what to test first. Solo founders install it when they have more hypotheses than runway and need a disciplined ordering instead of chasing the loudest idea. The skill integrates ICE-style thinking—impact tied to opportunity score and customer reach—and contrasts RICE when reach and impact should split explicitly, deferring formula detail to the sibling prioritization-frameworks skill. Each assumption lands in a quadrant that either defers work, green-lights implementation, demands an experiment, or keeps monitoring. It is written for $ARGUMENTS-style prompts with optional file ingestion of assumption spreadsheets or research notes. Outcomes are actionable next tests aligned with validation economics, not a full business plan.1kinstalls61Sprint PlanSprint Plan is an agent skill from the pm-skills collection that walks a solo builder or small team through a disciplined sprint planning session. You point it at your sprint context via arguments and optionally attach backlogs, velocity history, team rosters, or previous sprint reports so the agent grounds recommendations in real data. The workflow starts by translating people, PTO, meetings, and on-call into available story points or ideal hours, anchored on average velocity from the last three sprints and an explicit 15–20% buffer for unplanned work. It then pulls highest-priority backlog items only while each candidate meets Definition of Ready, stopping when capacity is full and flagging items that still need refinement. Dependency mapping sequences work across teams and surfaces external blockers, while a dedicated risk pass calls out uncertainty and mitigations before you commit. The output is a sprint plan you can hand to coding agents or teammates as the scope contract for the iteration—tighter than ad-hoc chat planning and aligned with how indie teams ship on two-week cycles.1kinstalls62RetroRetro is an agent skill that acts as a sprint retrospective facilitator for solo and indie builders who need consistent reflection without hiring a scrum master. You invoke it when closing a sprint, reviewing team or solo feedback, or turning messy input into concrete improvements. It chooses or applies one of three established formats—Start/Stop/Continue, the 4Ls, or Sailboat—then organizes whatever evidence you supply (metrics, notes, messages) into themes before drafting prioritized actions. That structure matters because ad-hoc “what went wrong?” threads rarely yield accountable follow-ups. The skill fits anyone running lightweight agile on a side project or small product team and wants repeatable retros that feed the next planning cycle rather than disappearing in chat history.1kinstalls63Beachhead Segmentbeachhead-segment helps solo founders and indie PMs choose the first market wedge where a new product can win quickly enough to learn before running out of runway. The skill frames beachhead selection as scoring candidate segments against acute pain, ability and motivation to pay, realistically winnable share, and referral dynamics that pull adjacent segments later. It expects you to interrogate whether problems are daily and expensive under DIY workarounds, whether budgets already exist for the job-to-be-done, and whether early adopters will evangelize once the wedge works. Use it when you are torn between multiple personas, planning a narrow launch, or validating go-to-market assumptions with the smallest credible customer set. The output is a defensible first segment narrative you can feed into positioning, landing copy, and prototype demos—not a broad TAM slide deck.997installs64WwasWWA is an agent skill from the pm-skills collection that guides solo builders and small teams to write product backlog items in Why-What-Acceptance format instead of vague tickets or over-specified stories. It connects each item to business and team objectives in a short Why, describes deliverable What with optional design links, and sets acceptance criteria that are verifiable without locking implementation. The eight-step process walks you through independence, negotiability, measurable value, testability, and sprint-appropriate sizing. It fits when you are breaking a feature into increments, preparing sprint planning, or communicating strategic intent to collaborators or your coding agent. For indie SaaS and API products, WWA keeps agent-assisted planning aligned with outcomes you can actually ship and validate.993installs65Draft Ndadraft-nda is an agent skill that walks you through drafting a detailed mutual Non-Disclosure Agreement between two named companies. You supply company names, addresses, representative titles, and the categories of information to be shared; the skill produces professional contract text with accessible explanations and marks areas that must be reviewed by counsel. It is aimed at indie founders and small teams who need a starting document for investor conversations, vendor pilots, contractor onboarding, or co-development talks—not a substitute for a lawyer. Because NDAs are binding, the skill repeatedly stresses attorney review before signing. Use it when you have identified the counterparty and the rough deal shape but do not yet have legal templates in place.984installs