
deanpeters/product-manager-skills
47 skills60.2k installs233k starsGitHub
Install
npx skills add https://github.com/deanpeters/product-manager-skillsSkills in this repo
1Prd DevelopmentPRD Development is a structured agent workflow for product managers and solo builders who need to convert messy discovery—notes, Slack, interview takeaways—into a cohesive Product Requirements Document. It walks you through problem framing, user research synthesis, solution definition, and measurable success criteria so engineers and agents share one definition of done. Use it when a major feature or initiative is approved in principle but still lives in people's heads, when you have finished a discovery sprint and need a handoff artifact, or when you want to avoid ambiguity, scope creep, and rebuilds caused by missing acceptance criteria. The skill is intermediate in depth: it assumes you already have some discovery material and need document structure rather than blank-slate brainstorming. Outputs are stakeholder-alignable PRDs suitable as the source of truth before implementation planning or coding begins.2.3kinstalls2User StoryThis user-story skill from the product-manager-skills collection is example-driven procedural knowledge for solo builders who act as their own PM. It shows what a strong story looks like—specific persona, concrete action, motivated outcome—and a deliberately bad story so agents avoid "improve login" vagueness. Acceptance criteria use Given/When/Then with a single primary path QA can execute. Use it while scoping a feature in Validate or while breaking work into tickets in Build, before you ask an agent to implement. It does not replace discovery interviews or analytics; it tightens how requirements read so implementation and test plans do not drift.2.2kinstalls3Roadmap PlanningRoadmap Planning is a product-management skill for solo founders and small teams who must align engineering work with retention, expansion, and technical constraints without a full PMO. It walks through gathering business goals and customer problems, writing epics with testable hypotheses and effort estimates, prioritizing with frameworks such as RICE (with room for strategic overrides), sequencing quarters around dependencies like data-pipeline upgrades, and communicating a clear story to executives and customers. The bundled SaaS example shows churn and enterprise targets driving Q1 onboarding and SSO versus deferred mobile and reporting work. Use it during annual or quarterly planning when you need one coherent roadmap instead of a scattered backlog. It complements prioritization-advisor-style guidance referenced in the examples and produces artifacts teams can publish internally and externally.2kinstalls4Company ResearchCompany Research is a product-manager agent skill that guides you through building a rigorous company profile for competitive and strategic decisions. It starts from a clear research objective and key questions, then fills in basics, history, leadership quotes, and product-strategy signals—illustrated with a detailed Stripe example covering payments infrastructure, developer experience, and platform expansion. Solo founders use it when they need more than a Wikipedia skim: credible narrative, executive voice, and hooks for differentiation before validation or GTM work. The output is markdown you can drop into notion, a PRD, or an investor memo. It does not scrape the web by itself; your agent still gathers sources, while the skill enforces structure and depth so research stays comparable across competitors.1.7kinstalls5Product Strategy SessionProduct Strategy Session is an agent skill for solo builders and small PM teams who need a repeatable strategy ritual instead of ad-hoc roadmap slides. It walks you through positioning and proto-personas, sharpens a measurable problem statement, explores opportunities on an opportunity-solution tree, ranks initiatives with frameworks like RICE, and packages narrative for executives—with room to add validation experiments before build. The bundled example (SaaS onboarding retention) shows how drop-off metrics, JTBD, and epic scores become a concrete Q1/Q2 plan. Use it when you have traction signals or a live product but lack alignment on what to fix first, who it is for, and how you will prove impact. It pairs naturally with other product-manager-skills canvases referenced inside the session (positioning workshop, problem framing, OST, prioritization advisor) so the agent does not skip framing steps.1.6kinstalls6Prioritization AdvisorPrioritization-advisor is an interactive agent skill for product managers and solo founders who need a defensible way to rank competing work without constantly switching methodologies. It walks through adaptive questions about where the product is in its lifecycle, how the team decides, and what stakeholders expect, then recommends a single prioritization framework such as RICE, ICE, or value/effort with practical rollout notes for that context. Use it when roadmap arguments stall on which model to use, when a new stage makes your old spreadsheet feel wrong, or when you want to avoid applying a data-heavy scorecard to strategic bets. The output is a clear framework choice plus implementation guidance, not a ranked backlog by itself—ideal for validate and build planning before you lock sprints or write implementation plans.1.4kinstalls7User Story MappingUser Story Mapping is a product-management agent skill that helps solo builders and indie PMs visualize the end-to-end user journey before they over-build. You anchor work on a persona and segment, lay out the backbone narrative and major activities, then drill into steps that become stories you can prioritize into releases. The bundled example—freelance invoicing from negotiation through payment follow-up—shows how to connect admin pain points to concrete backlog slices. Use it when you have a problem space but unclear MVP boundaries, when stakeholders need a shared picture of the flow, or when you are replacing spreadsheets with something your coding agent can extend into specs and tickets. It pairs naturally with validation and early build planning; it does not replace quantitative discovery, competitive research, or technical architecture decisions.1.4kinstalls8Jobs To Be Donejobs-to-be-done is a product-manager skill that helps solo and indie builders analyze what customers are trying to accomplish—not just which features they ask for—using a Jobs-to-be-Done (JTBD) lens. The bundled examples walk through functional jobs (coordination, tracking, blockers), social jobs (credibility with stakeholders), and emotional jobs (confidence, reduced stress), then map pains such as tool silos, manual reporting hours, and dependency blindness against gains like automated updates, faster onboarding, and calendar-friendly integrations. Use it when you are exploring an idea, narrowing validation scope, or writing PM artifacts and need a disciplined way to connect problems to measurable outcomes. It does not replace user interviews or analytics, but it gives your agent a repeatable template so positioning, MVP scope, and later growth messaging stay anchored in real jobs rather than feature checklists.1.4kinstalls9Customer Journey MapCustomer Journey Map is an agent skill from the Product Manager Skills library that guides you through building a stage-by-stage map of what your persona does, where they interact with your product, and what you want them to achieve next. Solo and indie builders install it when they need more than a feature list—they need a shared picture of awareness through loyalty before writing landing copy, onboarding, or distribution plans. The skill emphasizes concrete rows for customer actions and touchpoints aligned to objectives like activation and repeat usage. It pairs naturally with discovery and scoping work in Validate, audience and competitor research in Idea, and lifecycle thinking in Grow, without requiring a dedicated analytics stack. Output is a markdown journey map you can reuse in specs, investor narratives, and content calendars.1.3kinstalls10Saas Revenue Growth MetricsSaaS Revenue Growth Metrics is an agent skill that walks solo builders and indie PMs through a monthly SaaS health snapshot: starting and ending MRR, component breakdowns, ARPA and ARPU, logo and revenue churn, net revenue retention, and Quick Ratio. The SKILL content is anchored in a realistic mid-market example (200 accounts, 20k users) so you can mirror the same formulas against your own spreadsheet or billing export without hiring a finance analyst. Use it when you are past prototype and need to sanity-check whether growth is mostly new logos, expansion, or masking churn—especially before fundraising conversations, pricing experiments, or retention initiatives. It does not connect to Stripe or your data warehouse; you supply numbers and the skill enforces consistent definitions and narrative analysis. For Prism’s audience shipping B2B SaaS with Claude Code or Cursor, it turns ad-hoc “how are we doing?” chats into comparable, citable metric language aligned with standard SaaS operating reviews.1.3kinstalls11StoryboardStoryboard is a product-manager skill that packages a proven six-frame narrative template for solo and indie builders who need to communicate value faster than a long PRD. Instead of abstract personas, you write sequential scenes: introduce the user in context, articulate the recurring pain, dramatize a failure moment with real stakes, show how they find your product, land the aha payoff, and close with measurable life-after outcomes. The bundled SmartInvoice example demonstrates how hours saved, payment rates, and emotional relief translate into concrete frames. Use it when you are validating scope, aligning an agent on landing copy, or preparing launch storytelling—so every downstream artifact shares one coherent journey rather than disconnected features.1.3kinstalls12Discovery Interview PrepDiscovery Interview Prep is an interactive agent skill for product managers and solo founders who need credible customer learning before they commit engineering time. It guides you through adaptive questions about why you are interviewing, which segment matters, what constraints you face (time, access, channels), and which discovery method fits—problem validation, churn forensics, or new-idea tests. The flow is tuned for real indie constraints: five enterprise churn interviews in 90 days, a two-week validation sprint with cold email only, or diagnosing why activation on a core feature stalled. You leave with a structured interview plan and sharper questions designed to surface past behavior and pains, not compliments. It pairs naturally with validation and scope work when findings need to become a hypothesis or MVP cut. Install it when discovery feels improvised or when every conversation starts to sound the same.1.3kinstalls13User Story SplittingUser-story-splitting is an agent skill for product-minded solo builders who need epics and large stories broken into independently deliverable backlog items. It encodes systematic splitting—not arbitrary chopping—so each smaller story still delivers recognizable user value while cutting complexity, risk, and sprint overload. Invoke it when backlog work is too large to estimate confidently, sequence across sprints, or release on its own. The skill walks through eight proven patterns such as workflow steps, business-rule variants, data boundaries, CRUD slices, deferring polish, and spike vs implementation paths. That makes it equally useful while validating scope, grooming build-ready tasks, and planning ship cadence in one-person or tiny-team agile workflows. Output is a structured set of smaller stories ready for prioritization, pointing, and agent implementation plans without losing the original intent of the epic.1.3kinstalls14Discovery ProcessDiscovery process is a product-management agent skill that teaches solo founders how to run disciplined discovery instead of jumping from a churn metric to a feature backlog. The documented SaaS retention walkthrough moves from problem framing and a concrete problem statement through research planning—here, switch interviews with churned users—into live interviews, affinity synthesis, solution generation, lightweight experiments, and an explicit GO/NO-GO. It shows how to surface repeating pain quotes, map them to opportunity-solution trees, and validate a guided onboarding checklist with a small prototype test before writing an epic hypothesis. The skill is methodology-first: it expects you to invoke related canvases and interview prep skills as modular steps rather than one-shot brainstorming. Builders wearing the PM hat use it to de-risk scope during validate, but the same loop applies when exploring new growth bets or diagnosing lifecycle drops later in the journey.1.3kinstalls15Opportunity Solution TreeOpportunity Solution Tree is an agent skill that guides solo builders and indie PMs through Teresa Torres–style discovery: start from a real stakeholder or customer problem, articulate one measurable outcome, enumerate competing opportunities with evidence, let you pick the highest-leverage branch, then propose solutions each tied to a falsifiable experiment. It is for anyone who receives requests like “we need better retention features” without a clear link between churn, user behavior, and what to ship first. Use it when you need structured product thinking before writing specs, roadmaps, or implementation plans—especially when data fragments (login frequency, exit interviews, support tickets) need to become a coherent narrative. The skill matters because it prevents building the wrong feature confidently: you document why the outcome matters, why each opportunity is plausible, and how you would know a solution worked. It pairs naturally with brainstorming and writing-plans once an opportunity and experiment are chosen.1.3kinstalls16Problem Statementproblem-statement is a product-management agent skill from the deanpeters product-manager-skills set. It teaches solo builders and indie PMs how to write problem framing narratives and compress them into a single testable sentence before anyone commits engineering time. The workflow walks through persona (“I am”), goal (“trying to”), obstacle (“but”), root cause (“because”), and emotional impact (“which makes me feel”), then adds context and constraints such as time zones, toolchain integrations, or compliance limits. Worked examples—including an early Slack-style distributed-team communication pain and a deliberately bad “we need AI analytics” statement—show how solution language erodes validation. The intended use is early discovery and scope sessions: you exit with language you can reuse in landing pages, interview scripts, and prioritization debates. It pairs naturally with later planning skills once the problem is agreed, but it does not replace quantitative validation or competitive research on its own.1.3kinstalls17Business Health DiagnosticBusiness Health Diagnostic is an agent skill for solo founders and small SaaS teams who need one coherent read on company health instead of cherry-picked charts. It walks through growth, retention, efficiency, and capital together so you can spot mismatches—such as strong top-line growth with weak unit economics or heavy burn—before investors or your board do. The skill is framed as an interactive, finance-metrics session with realistic scenarios (Series A prep, cash burn vs growth) and an estimated 20–30 minute run time. Use it when you are preparing a business review, deciding what to fix first, or packaging a health scorecard for stakeholders. It does not replace your data warehouse or billing exports; you still bring the numbers, and the skill structures interpretation, prioritization, and narrative for decision-making.1.3kinstalls18Feature Investment AdvisorFeature Investment Advisor is a product-management agent skill that turns a vague “should we build this?” question into a financial decision conversation. Solo builders running SaaS side projects install it when debating paid add-ons, packaging changes, or roadmap bets without a finance partner. The skill sequences context gathering—feature summary, customer segment, MRR, ARPA, churn, margin, engineering cost—then walks revenue linkage options mirroring how experienced PMs frame investments. The bundled time-tracking example shows how to stress-test ARPU uplift against support load and delivery cost. It is intermediate complexity: you need rough business numbers, not a FP&A model. Use during Validate before writing implementation plans, and again in Build PM checkpoints when scope creeps. It outputs a reasoned go/no-go narrative and levers to model, not automated spreadsheet files unless your agent creates them from the thread.1.2kinstalls19Saas Economics Efficiency Metricssaas-economics-efficiency-metrics translates product-manager finance framing into decisions solo SaaS founders can act on without a full FP&A team. It uses concrete scenarios—such as enterprise CRM with healthy-looking LTV:CAC that still traps cash because of long sales cycles, quarterly billing, and upfront CAC—to show why ratio vanity metrics mislead board conversations and ad spend. You learn to pair gross margin, ARPU or contract structure, payment terms, and acquisition timing so payback reflects money in the bank, not spreadsheet LTV alone. Invoke it when validating pricing and GTM before a raise, when Grow initiatives need guardrails on CAC spend, or when Operate reviews show growth stalling despite "good" unit economics on slides. The skill is narrative and metric-literate rather than a spreadsheet template; bring your CAC components, contract terms, and churn assumptions. Advanced for founders new to SaaS finance; intermediate for PMs already tracking MRR and churn.1.2kinstalls20Epic Breakdown AdvisorEpic Breakdown Advisor is an interactive product-management skill that walks solo founders and indie PMs through Richard Lawrence’s complete Humanizing Work story-splitting flowchart. When a backlog item is a vague feature blob—onboarding, reporting, admin workflows—you use it to pick among nine sequential splitting patterns, produce vertical slices that still read as user stories, and judge whether a split exposes fluff you should delete instead of ship. The skill is typed interactive with explicit best-for scenarios from the SKILL.md frontmatter. It sits early in the journey at Validate/scope because right-sizing work precedes safe estimates, yet the same ritual belongs in Build/pm before sprint planning. Intermediate complexity assumes you already write epics and acceptance-oriented stories. It does not write code or auto-sync Jira; it improves the story map your agent or team will implement next.1.2kinstalls21Epic HypothesisEpic Hypothesis is a product-management skill pattern for solo and indie builders who need investor-grade rigor without a full PM team. It teaches how to write an epic-level if/then statement that names the change, the segment, and a measurable outcome, then backs it with deliberately small discovery experiments—clickable prototypes, non-functional CTAs for CTR, or concierge delivery—rather than jumping straight to a sprint. Validation measures spell out what “valid” looks like with mixed quant and qual gates so you can kill or commit before code ships. The bundled examples show a strong Google Calendar onboarding bet beside a deliberately weak dashboard epic so agents learn what specificity buys you. Use it when a feature feels strategic but unproven, when stakeholders want a thesis before tickets, or when you need one markdown artifact an agent can extend into a validate-phase roadmap.1.2kinstalls22Finance Based Pricing AdvisorFinance-Based Pricing Advisor is an agent skill for solo founders and indie SaaS builders who already have a pricing hypothesis and need numbers before committing engineering or comms. It walks through the financial impact of increases, new tiers, add-ons, and discounts using ARPU and ARPA, conversion effects, churn risk, net revenue retention, and CAC payback—so you can make an explicit ship or hold decision. The skill’s intent is narrow and useful: it is not a substitute for value-based pricing design, WTP studies, or competitive teardowns. Use it when you are about to change packaging or list prices and want supporting math and risk framing in plain language. It fits interactive back-and-forth best_for lists: evaluating raises and discounts, estimating churn and conversion risk, and deciding whether a monetization change deserves a launch. Pair outputs with customer research or experimentation if conversion and churn assumptions are still guesses.1.2kinstalls23Problem Framing Canvasproblem-framing-canvas is a product-manager agent skill that structures messy customer signals into a defensible problem statement before you commit engineering time. Solo founders use it when analytics, interviews, or support tickets show pain but the team still debates solutions. The readme walks an eight-question flow: anchor on observed behavior, classify difficulty and assumptions, name who is optimizing for whom, define who/when/consequences, benchmark adjacent markets, call out excluded users and beneficiaries of the status quo, then synthesize a refined problem statement and a How Might We line with a measurable aim. The included SaaS onboarding example models non-technical small business owners churning within 24 hours due to jargon-heavy UI—useful as a template for your own domain. It pairs naturally with later planning skills once the problem is agreed. Complexity is beginner-friendly because it is question-driven prose, not code. Confidence is high for validate and idea research even when the skill file description is empty, because the example encodes the full ritual.1.2kinstalls24Context Engineering AdvisorContext Engineering Advisor is an interactive agent skill from Dean Peters’ product-manager collection for solo builders and PMs who rely on Claude, Cursor, or Codex for real delivery work—not one-off chat. It separates context stuffing (dumping volume without structure) from context engineering (shaping what the model attends to). You work through when workflows feel bloated, brittle, or hard to steer: defining context boundaries, episodic retrieval instead of hoarding everything in one window, and tactical patterns like bounded domains plus the Research→Plan→Reset→Implement cycle. The skill fits early Validate conversations about scope and architecture, Build when designing agent rituals around specs and backlogs, Ship when review context explodes, and Operate when production debugging threads grow unbounded. It does not install code or MCP servers; it produces a clearer mental model and concrete fixes you can apply to SKILL.md chains, PRD workflows, and team prompts.1.2kinstalls25Tam Sam Som CalculatorTAM-SAM-SOM Calculator is an interactive product-manager agent skill that walks you through Total Addressable Market, Serviceable Available Market, and Serviceable Obtainable Market for a product idea. It asks context-aware questions, forces explicit assumptions and methods, and aims for citation-backed estimates rather than guesswork—useful when you pitch investors, defend a business case, or check whether the opportunity is large enough to matter. The SKILL.md frames TAM as unconstrained total demand, SAM as the slice you can serve with your model and geography, and SOM as what you can realistically capture near term. Solo founders without a PM bench can still run the same rigor before writing code. Expect a structured dialogue, not a spreadsheet dump. Pair it with competitor and audience research earlier in Idea, then reuse refined numbers in Validate pricing and Grow planning.1.2kinstalls26Proto PersonaProto-persona is an agent skill that helps solo builders and indie PMs sketch a believable target user before full user research. It walks through naming, demographics, representative quotes, pains, goals, attitudes, and buying or influence factors using a markdown-friendly template. The bundled “Manager Mike” example models how much specificity to include for a mid-market B2B SaaS director—enough to drive positioning and feature bets without pretending you ran a research panel. Use it when you have a product hypothesis but stakeholders (or you) keep debating “who is this for?” across discovery, validation workshops, build-time prioritization, and early go-to-market messaging. It does not replace interviews or analytics; it gives your agent a consistent artifact to extend into landing pages, interview guides, and backlog rationale.1.2kinstalls27Positioning StatementPositioning Statement is an agent skill for solo founders and indie PMs who need messaging discipline before they build features or run ads. It teaches the paired value-proposition and differentiation format using real Slack-era examples and a deliberately bad generic SaaS counterexample so you can see why “improve productivity for businesses” fails audits with investors, users, and your own roadmap. The skill pushes you to name a specific audience, a contextual need, a recognizable category, and a verifiable contrast versus alternatives—not buzzwords. Use it when a landing page, pitch deck, or pricing page still sounds interchangeable with ten competitors. Outputs are ready-to-edit positioning blocks you can feed into copy, validation interviews, and later launch messaging without re-arguing who the product serves.1.2kinstalls28Lean Ux CanvasLean UX Canvas is an agent skill that walks solo and indie builders through Jeff Gothelf–style lean UX framing in a single structured artifact. You articulate the business problem with evidence, define measurable business outcomes, narrow primary users, spell user outcomes, list solution options, write testable hypotheses, name the riskiest assumption, and design a minimal experiment such as wizard-of-oz tests. It is built for product managers and founders who need alignment before design or engineering commits, especially when mobile or conversion metrics expose a gap between traffic and revenue. Use it when you have anecdotal pain but no shared spec, when stakeholders disagree on what to build next, or when you want experiment-sized scope instead of a quarter-long roadmap. The skill emphasizes hypothesis-driven learning so Validate work produces learning goals, not just documentation decks.1.2kinstalls29Customer Journey Mapping WorkshopCustomer Journey Mapping Workshop guides product managers—and solo founders acting as PM—through building a journey map for a specific persona and scenario. The agent asks adaptive questions about who is traveling, what they are trying to accomplish, which phases they pass through, what they do and feel at each step, where experience breaks down, and where investment would help. The goal is a shared picture of the end-to-end experience that steers discovery toward evidenced pain points instead of assumed feature lists. Typical uses include onboarding from signup to first value, trial-to-paid conversion paths, or support journeys for churn-risk accounts. Expect an interactive, facilitated pace when combined with the workshop-facilitation pattern. Use this in Validate when you need team alignment or solo clarity before prototyping, and reuse in Grow when you revisit lifecycle or support flows after launch.1.2kinstalls30Workshop FacilitationWorkshop Facilitation is the shared protocol for interactive product-manager skills on Prism: it tells your agent how to pace a session, show progress, offer entry modes, and handle detours without losing structure. Solo builders and tiny teams use it whenever a skill should feel like a facilitated workshop rather than a wall of questions—positioning sprints, discovery kickoffs, scoring exercises, or any multi-turn flow that needs clear turns and labeled progress. The skill does not replace domain content; it is the choreography layer other workshops plug into. Expect consistent heads-ups at the start, one question per turn, recommendation blocks at forks, and visible step counters so you can pause and resume. Install it when you are authoring or running deanpeters-style interactive PM skills, or when you want your agent to emulate a human facilitator instead of dumping a full template in one reply.1.2kinstalls31User Story Mapping WorkshopUser Story Mapping Workshop is an interactive PM skill for solo founders and small teams who need a shared picture of the product before sprint planning. The agent guides you through adaptive questions about the system, actors, end-to-end workflow, and what matters most now versus later. The result is a two-dimensional story map: a horizontal backbone of user activities and tasks that tells the whole journey, plus vertical slices that define viable releases without losing narrative context. It is deliberately not a backlog dump—it's a communication and scoping framework that exposes gaps and makes tradeoffs visible. Use it when a flat issue list hides missing steps or when stakeholders need to see the big picture in one view. Pair the output with implementation planning skills once release slices are agreed.1.2kinstalls32Press ReleasePress Release is an agent skill for solo and indie builders who need credible launch copy without hiring a PR agency. It teaches the classic announcement structure—headline, dateline, intro, problem paragraph with evidence, solution with quote, and follow-on details—using a full hypothetical SmartInvoice example. Use it when you are validating positioning (working backward from the announcement) or when you are ready to distribute news about a shipped product. The skill emphasizes measurable outcomes in the headline and body so AI-search and journalists can quote you accurately. It fits SaaS, workflow tools, and content products where administrative pain or time savings is the hook. Pair it with landing-page and SEO skills after the narrative is stable.1.2kinstalls33Pestel Analysispestel-analysis is a product-manager skill that turns vague “is this market worth it?” anxiety into a written macro scan you can reuse with an AI agent. Solo and indie SaaS builders use it before locking geography, compliance story, and pricing—especially when AI, fintech, or cross-border data flows amplify political and legal risk. The bundled example walks through SmartInvoice-style AI automation in the US and EU, showing how to translate regulation and tax into concrete scope and cost assumptions rather than hand-wavy trends. Invoke it when you have a named product direction but need external reality checks across policy, economy, society, tech shifts, environment, and law. Output is a structured markdown brief you can attach to validate-phase decisions, pitch decks, or positioning for launch and growth planning without hiring a strategy consultant for a first pass.1.2kinstalls34Positioning WorkshopPositioning Workshop is an interactive agent skill that walks a product manager—or solo founder playing PM—through discovering and articulating positioning: target customer, unmet need, category, benefits, and differentiation. Use it when messaging sounds interchangeable with competitors, when sales and product disagree on who the product is for, or before you invest in a PRD, launch plan, or homepage rewrite. The skill is conversational rather than a static template; it asks adaptive questions until positioning choices feel deliberate. It sits early in the journey but pays off again at Launch and Grow when copy, pricing pages, and lifecycle campaigns must stay consistent with the same spine. Outputs are clarity and aligned language stakeholders can reuse, not automatic ad creative or code.1.2kinstalls35Finance Metrics Quickreffinance-metrics-quickref is a component agent skill that gives solo builders and indie PMs a fast SaaS finance lookup table: definitions, formulas, and benchmark ranges without long explainers. It is for the Validate through Grow phases whenever you are sanity-checking pricing, board metrics, or growth narratives and need NRR, CAC payback, Rule of 40, or churn rules in seconds. Unlike deep-dive teaching skills in the same repo, this file is explicitly a cheat sheet optimized for scan-and-apply during product or finance reviews. Use it when a stakeholder asks “what’s good for NRR?” mid-call, when you are drafting a pricing section, or when you are aligning analytics dashboards with standard SaaS definitions. It does not replace modeling spreadsheets or investor-grade models—it anchors terminology so your agent answers consistently.1.2kinstalls36Acquisition Channel AdvisorAcquisition Channel Advisor is a product-manager agent skill that helps solo founders and indie SaaS builders decide whether to scale, hold, or cut spend on a specific acquisition channel. Presented as a guided conversation, it collects channel spend, customers acquired, channel CAC, and business context such as blended CAC, LTV, ARR, and target growth rate—then walks through unit economics comparisons like a channel that is three times more efficient than blended CAC. The canonical home is Grow analytics because the output is a budget and scaling recommendation, but the same ritual applies when validating pricing assumptions, researching which channels to try first, or replanning lifecycle mix after six months of content or paid tests. It does not replace attribution tooling; it structures the judgment call so your agent does not hand-wave "scale content" without tying dollars to LTV and growth targets. Use it before increasing writer headcount, SEO contractors, or paid parallel spend.1.2kinstalls37Ai Shaped Readiness AdvisorAI-Shaped Readiness Advisor is an interactive product-manager skill that helps solo founders and small product teams stop confusing faster PRDs with a genuinely AI-shaped organization. It walks you through whether work is AI-first—automating existing tasks—or AI-shaped—redesigning how the team operates around AI capabilities. The assessment maps honesty across five essential PM competencies framed for 2026, surfaces gaps, and recommends which capability to build first instead of spraying Copilot everywhere. Estimated time is fifteen to twenty minutes. Use it when you sense tools are adopted but rituals, decision rights, and discovery loops look unchanged. On Prism it sits in Validate for scoping investments, yet the methodology applies whenever you replan strategy in Idea, tune growth experiments in Grow, or rethink operations in Operate. Deliverables are a maturity readout and a prioritized next competency, not generated code. Category is Productivity & Planning with an AI lens.1.2kinstalls38Recommendation Canvasrecommendation-canvas is an agent skill for solo builders who wear the product hat and need a single markdown artifact that defends a feature bet to themselves, cofounders, or early users. It follows a recommendation-canvas structure: product name, business and product outcomes, a concrete problem story, a falsifiable solution hypothesis, discovery experiments, and proof-of-life metrics. The catalog shelf is Validate → scope because that is when you decide what to build next and what evidence would change your mind, though the same template supports Idea-stage framing and Build-phase PM check-ins. The bundled SmartReminders example shows how freelance-invoicing pain translates into churn and MRR goals, timed AI reminders, and two-week prototype tests—useful for AEO queries about outcome-driven specs rather than feature laundry lists.1.2kinstalls39Pol Probe AdvisorPoL Probe Advisor is an interactive product-management skill that helps solo founders and indie PMs choose the right Proof of Life validation method. Instead of defaulting to the prototype you know how to build, it walks you through hypothesis, risk level, and available resources to recommend among five PoL probe types—the smallest experiment that can falsify what matters. Use it when you must eliminate a specific risk or test a narrow claim about demand, onboarding, or a speculative AI feature before committing engineering time. The skill is consultative: it does not ship code or run experiments for you; it aligns learning goals with probe mechanics so validation spend stays proportional to uncertainty. It pairs naturally with scope documents and landing-page or concierge tests in early validate work.1.1kinstalls40Skill Authoring WorkflowSkill Authoring Workflow is a meta workflow for product managers and solo maintainers of agent skill repositories. It standardizes how you convert messy workshop notes or half-finished prompts into skills that pass metadata checks and belong in the catalog structure. The process anchors on repository-native scripts for discovery, scaffolding, building, testing, and Python metadata validation—so you repeat the same gates instead of improvising each release. Invoke it when you are adding or materially updating a PM-focused skill and need confidence that frontmatter, naming, and layout match repo rules before you commit. It complements creative brainstorming or planning skills by handling the mechanical compliance path afterward. Outputs are validated SKILL.md files ready for review and merge, not automatic publication to external marketplaces.1.1kinstalls41Pol ProbePoL Probe is an agent skill from the product-manager-skills collection that teaches solo builders and indie PMs how to run Proof-of-Learning probes: small, intentional experiments that answer one product or technical question with clear evidence. Instead of debating archive versus delete in Slack for a week, you write a narrow hypothesis, pick a probe type, set a short timeline, and define pass and fail thresholds before you recruit users or spike code. The skill emphasizes disposable artifacts—when the probe teaches you something, you change the plan or drop the feature and delete the probe rather than treating the doc as permanent roadmap wallpaper. Task-focused probes suit UX clarity and consequence labeling; feasibility probes suit GenAI chains, integrations, and jargon-heavy domains where error rates matter. It fits builders shipping SaaS, agents, or APIs who already have a hunch but lack a cheap falsification step. Use it in Validate when a prototype decision is still open, in Idea when audience or demand assumptions need a quick signal, or in Build when you must de-risk an implementation path before the main sprint.1.1kinstalls42Eol MessageEOL Message is an agent skill from the product-manager toolkit that helps solo founders write credible end-of-life announcements when they must discontinue a SKU, retire legacy infrastructure, or consolidate onto a single modern product. Rather than a terse shutdown email, it models a full narrative arc—who you are as a vendor, what is ending, why the change is necessary, and what concrete improvements customers gain by migrating. The included Acme Workflows Classic example shows quantity-backed social proof, dated cutoff, and benefit bullets tied to performance and integrations, which is the tone indie SaaS operators need to reduce churn and support tickets. You invoke it when migration planning is real—not when brainstorming ideas—typically alongside engineering timelines and billing changes. Output is markdown-ready customer comms you can adapt for email, in-app banners, and changelog posts.1.1kinstalls43Director Readiness AdvisorDirector Readiness Advisor is an agent skill from the product-manager-skills collection for senior PMs who want to close the gap to Director-level expectations without guessing what interviewers and executives actually probe. The documented flow starts with situational intake—preparing, interviewing, new in role, or recalibrating—then narrows on the hardest dimension such as delegation, leading through other PMs, strategic narrative, or cross-functional influence, and anchors urgency with an interview timeline. For a common branch like preparing with a strategic narrative weakness and three to six months runway, the agent recommends concrete weekly habits such as cascading one company priority into business, portfolio, and team implications and practicing one-sentence layers out loud. Solo founders who later hire PMs can use the same framing to articulate strategy beyond execution, though the skill is optimized for IC PMs targeting Director loops rather than day-to-day shipping mechanics.1.1kinstalls44Altitude Horizon FrameworkAltitude Horizon Framework is a product-management component skill that teaches the mental model behind Director-level work: how far you zoom out across teams and systems (altitude) and how far forward you commit plans and bets (horizon). Solo builders and senior PMs on tiny teams use it when a promotion—or acting as head of product—feels stuck: scope feels too narrow, roadmaps fight each other, or strategy from above is too fuzzy to execute. The skill helps you name which transition zone is misfiring and when to apply a Cascading Context Map so downstream tasks stay aligned without rewriting the company strategy yourself. It is deliberately not a delivery checklist for code; it is leadership cognition for anyone who must translate ambiguity into sequenced product decisions across Idea through Operate. Use it before re-orging your backlog, before hiring your first PM, or when mentoring IC PMs who need a shared vocabulary for level expectations.1.1kinstalls45Executive Onboarding Playbookexecutive-onboarding-playbook structures a VP or CPO transition as a diagnostic 30-60-90 path instead of an execution sprint. It targets the common failure mode of acting before understanding—reorgs, turnover, or strategy announcements without an evidence base. Solo founders stepping into their first Head of Product hire, indie SaaS CEOs taking a CPO seat, or product leads evaluating an executive offer can use it to sequence listening tours, risk maps, and decision gates across Diagnose, Learn, and Act phases. The skill is prose-first planning for the agent to facilitate: clarifying questions for the hiring CEO, checkpoints before structural changes, and validation when you are two months in and unsure whether to move. It is not a engineering implementation skill; it outputs a defensible onboarding plan and decision criteria aligned with product leadership best practice.1.1kinstalls46Vp Cpo Readiness AdvisorVP CPO Readiness Advisor is an agent skill that guides product leaders through structured conversations when stepping into or evaluating VP Product and CPO roles. Solo founders rarely need it, but indie builders who hire product leadership or senior PMs evaluating their own leap get a scripted diagnostic: pick your situation, narrow the process stage, surface the dominant risk, then receive targeted questions and outputs such as CEO interviews before accepting an offer. It lives in Validate because the canonical shelf is scoping a high-stakes commitment—whether the role’s mandate, executive team, and strategy are coherent enough to succeed. The skill is methodology, not a hiring ATS integration; the agent asks multiple-choice style prompts and synthesizes branch-specific guidance. On Prism it helps builders who wear the PM hat during fundraising, hiring, or their own career moves find procedural rigor next to technical build skills, reducing the chance you accept a title without decision rights.1.1kinstalls47Product Sense Interview AnswerProduct Sense Interview Answer is a product-manager skills package that teaches how to answer classic product-sense prompts using a disciplined narrative: clarify scope, articulate market rationale and thesis, define a user-centric goal, segment the ecosystem, pick one segment and pain, then converge on an MVP with tradeoffs. The included YouTube improvement example demonstrates why strong answers avoid "improve everything" vagueness by committing to viewers, viewing intent, and a specific satisfaction thesis about recommendations versus intentional value. Solo builders benefit beyond interviews— the same structure sharpens validate-phase scoping when you are deciding what slice of a crowded market to build first. The skill is prose-and-pattern based without shell integrations, so it pairs naturally with brainstorming or writing-plans skills when you move from narrative scope to implementation tasks. Complexity is beginner-friendly for the example format but intermediate for applying the framework to novel products under time pressure.648installs