All authors
Claude Skills by VandanaAjayDubey111
github.com/VandanaAjayDubey111193 skills4 installs169 views
- Opportunity Solution TreeBuild an Opportunity Solution Tree (OST) to structure continuous product discovery — map one desired outcome to customer opportunities, candidate solutions, and validating experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when structuring discovery, turning research into prioritized bets, or deciding what to build next without jumping to solutions.Votes: 0GitHub stars: 3
- Outcome RoadmapTransform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.Votes: 0GitHub stars: 3
- Pci BundlePlaybook for PCI-DSS scope decisions from a product perspective — SAQ-A vs SAQ-A-EP vs SAQ-D, card-data flow architecture, tokenization, SCA / PSD2 (EU), 3DS 2.x, scope-reduction patterns.Votes: 0GitHub stars: 3
- Pestle AnalysisPerform a PESTLE analysis covering Political, Economic, Social, Technological, Legal, and Environmental factors. Use when assessing the macro environment, doing strategic planning, or evaluating external factors affecting your business.Votes: 0GitHub stars: 3
- Plg Operating ModelRun product-led growth as an integrated system, not a tactic — where the product itself acquires, activates, retains, monetizes, and spreads. Use when the user mentions "product-led growth", "PLG", "self-serve", "free trial", "freemium", "PQL", "product-qualified lead", "bottoms-up", "free-to-paid", "self-serve funnel", "time-to-value", "TTV", or asks "should we be sales-led or product-led?". Also trigger when designing a free tier, an invite-only→open launch, an in-product upgrade path, or a...Votes: 0GitHub stars: 3
- Pm AuditPlaybook for auditing PM-health across 15 dimensions (Discovery, Strategy, Prioritization, Roadmap, Specs, Metrics, Launch, Measure, Comms, Decisions, Pricing, Competitive, Feedback, AI-PM, Governance) and producing a structured report. The brain behind pm-auditor.Votes: 0GitHub stars: 3
- Pm Tech Spec ReviewReview an engineering technical spec through a PM lens — does it cover every PRD requirement, does it preserve user/UX intent, does it quietly add or drop scope, what are the product risks, what's missing for launch. Produces a priority-tagged findings list + clarifying questions for engineering. Use after eng drafts a tech spec / design doc / architecture proposal and before code lands.Votes: 0GitHub stars: 3
- Porters Five ForcesPerform Porter's Five Forces analysis — competitive rivalry, supplier power, buyer power, threat of substitutes, and threat of new entrants. Use when analyzing industry dynamics, assessing competitive forces, or evaluating market attractiveness.Votes: 0GitHub stars: 3
- Pr AuthoringPlaybook for deployment-aware pull requests — the 11-section format that turns a PR into a reviewable contract; why, decision requested, change map, review order, evidence, verification, risk, rollback. Used for the Define→build handoff and any PR a great-pm-driven project opens.Votes: 0GitHub stars: 3
- Pr ReviewPlaybook for reviewing pull requests — verdict format, verification-not-trust, severity-ranked findings with concrete fixes, risk acceptance on the record. The reviewer-side counterpart of pr-authoring.Votes: 0GitHub stars: 3
- Prd AuthoringPlaybook for writing build-ready PRDs — structure, user stories, acceptance criteria, scope vs non-goals, edge cases, and the anti-patterns that kill engineering velocity. Used by spec-writer (to author) and spec-reviewer (as the rubric).Votes: 0GitHub stars: 3
- Pre MortemImagine the initiative has already shipped and failed publicly — work backwards from the failure to identify the most likely product / PM causes BEFORE building. Forces concrete risk identification, not vague "what could go wrong" lists. Adapted from Gary Klein's MIT Sloan research; pairs with engineering's engineering-side pre-mortem.Votes: 0GitHub stars: 3
- Pricing ModelsPlaybook for choosing a pricing model, designing tiers, setting the free-vs-paid line, and estimating willingness to pay with a real method. Used by pricing-strategist.Votes: 0GitHub stars: 3
- Prioritization MethodsPlaybook for 12 proven prioritization methods. Helps prioritization-analyst pick the right method for the decision at hand — not the most familiar. Covers RICE, ICE, MoSCoW, Kano, Weighted Scoring, Value-vs-Effort, WSJF / Cost of Delay, Opportunity Solution Trees, Story Mapping, Impact Mapping, Buy-a-Feature, Eisenhower.Votes: 0GitHub stars: 3
- Product Strategy StackCascade a fixed product vision into a changing roadmap through an explicit Vision → Strategy → Bets → Roadmap stack — so strategy means "which problems we''ll solve", not "a list of features". Use when the user mentions "product strategy", "strategy stack", "product vision", "strategic bets", "DHM", "delight hard-to-copy margin-enhancing", "strategy vs roadmap", "vision to roadmap", or says "our roadmap IS our strategy" / "we have a roadmap but no strategy". Also trigger when a 0-to-1 build i...Votes: 0GitHub stars: 3
- Rag Vs Finetune DecisionThe model-capability decision tree — prompt-engineering first, then RAG for missing knowledge, then fine-tuning for missing behavior/format or cost/latency, climbing only as far as needed. Covers the cost/latency/maintenance tradeoffs of each rung and when each is the wrong choice (especially the premature-fine-tune trap). Gives the PM the framework to decide where an AI feature's knowledge and behavior should come from. Used by ai-prompt-architect and architect.Votes: 0GitHub stars: 3
- Release NotesGenerate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.Votes: 0GitHub stars: 3
- Responsible Ai GuardrailsThe product-side (not legal-side) safety playbook for shipping AI features — input/output filtering, confidence thresholds, hallucination grounding, escalation, disclosure, a red-team product checklist, and a PM-owned pre-ship safety gate. Grounded in the NIST AI RMF (Map/Measure/Manage), Google PAIR, and OWASP LLM guidance. Complements regulatory skills (ai-regulation, india-fintech, us-fintech) — those are legal; this is safety engineering.Votes: 0GitHub stars: 3
- RetroFacilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.Votes: 0GitHub stars: 3
- Skeptical TriageReusable 3-round self-challenge + arbiter pattern for stress-testing a critical PM decision before it is finalized. Filters weak reasoning and false confidence from strategy, prioritization, spec, pricing, and gate decisions.Votes: 0GitHub stars: 3
- Sprint PlanningPlan a sprint with capacity estimation, story selection against Definition of Ready, dependency mapping, and risk identification. Produces a sprint goal + committed-scope summary with a 15-20% buffer. Use when preparing sprint planning, estimating team capacity, selecting stories, or balancing scope against velocity.Votes: 0GitHub stars: 3
- Stakeholder MapBuild a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.Votes: 0GitHub stars: 3
- Storybrand MessagingClarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions "brand message", "website copy", "elevator pitch", "one-liner", "messaging isnt resonating", "brand script", "StoryBrand framework", or "customer as hero". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales collateral and marketing materials. Covers landing page copy, marketing collateral, and consistent commu...Votes: 0GitHub stars: 3
- Swot AnalysisPerform a detailed SWOT analysis — strengths, weaknesses, opportunities, and threats with actionable recommendations. Use when doing strategic assessment, competitive analysis, or evaluating a product or business position.Votes: 0GitHub stars: 3
- Ticket AuthoringPlaybook for change tickets — the format that makes a work item buildable and traceable; outcome title, why, scope, acceptance criteria, dependencies, evidence links. The upstream contract that pr-authoring's PR closes against.Votes: 0GitHub stars: 3
- Us FintechPlaybook for product decisions in US fintech — federal + state regulatory matrix, ECOA / Reg B adverse action, FCRA, MLA 36% APR cap, NMLS licensing, CFPB / OCC / state-DFI authority, PCI scope.Votes: 0GitHub stars: 3
- User ResearchPlaybook for planning and synthesizing user research — research questions, JTBD framing, interview-guide design, problem validation, and the leading-question traps to avoid. Used by user-researcher in the Discover stage.Votes: 0GitHub stars: 3
- Value Proposition CanvasDesign a sharp value proposition using a 6-part JTBD template — Who, Why (problem/JTBD), What-before, How (solution), What-after, Alternatives. Use when articulating why a customer should choose this product over substitutes, assessing product-market fit, or producing a reusable value-prop statement for marketing/sales/onboarding.Votes: 0GitHub stars: 3
- Working BackwardsAmazon's Working Backwards / PR-FAQ method — start from the customer problem and desired outcome, write the internal press release + FAQ BEFORE building. Use when defining a new product or major feature, evaluating competing ideas, aligning stakeholders, or forcing clarity on a vague concept before committing engineering resources.Votes: 0GitHub stars: 3
- Great Pm RuntimeUse when a GreatPM workflow needs to select, spawn, coordinate, or collect results from its specialist product-management roles in Codex.Votes: 0GitHub stars: 3
- AccessibilityPlaybook for product accessibility — WCAG 2.2 AA, ADA Title III (US public accommodations), Section 508 (US federal), EN 301 549 (EU), accessibility-first UX patterns, accessibility testing.Votes: 0GitHub stars: 3
- Activation Aha MomentThe statistical method for finding a product's activation/aha moment — the action that, taken early, separates retained users from churned ones (the \"kink in the retention curve\"). Distinguishes setup-moment vs aha-moment vs habit-moment, and how to find and validate the metric rather than guessing it. Used by analytics-analyst and metrics-architect.Votes: 0GitHub stars: 3
- Agent Product PatternsThe workflow-vs-agent decision and the seven Anthropic building-block patterns (augmented LLM, prompt chaining, routing, parallelization, orchestrator-workers, evaluator-optimizer, autonomous agent). Gives the PM the vocabulary and decision tree to scope an AI feature's control flow BEFORE the engineering spec exists — and the discipline to not build an agent when a workflow suffices. Used by ai-prompt-architect and architect.Votes: 0GitHub stars: 3
- Ai EvalsEval-driven product management for LLM features — error analysis, axial coding of failure modes, LLM-as-judge with TPR/TNR validation, and the continuous Analyze→Measure→Improve loop. Used when an AI feature's output quality is the product and \"did it get better?\" must be answered with evidence, not vibes. Hosted by ai-eval-engineer / metrics-architect.Votes: 0GitHub stars: 3
- Ai RegulationPlaybook for AI-specific regulation — EU AI Act (high-risk + GPAI obligations), NIST AI RMF (US voluntary), Biden EO + agency actions, state AI laws (NY LL 144, CO SB 205, etc.), sector-specific overlays.Votes: 0GitHub stars: 3
- Ai Unit EconomicsThe unit-economics model that governs whether an AI product is viable. Forces explicit cost-per-action (token + orchestration overhead), gross-margin-per-query math, the \"every feature use costs money\" mental model, the cost levers (caching, model tiering, batching, local inference), and break-even analysis. The AI extension of cost-model and pricing-models — those are general; this models per-query variable cost.Votes: 0GitHub stars: 3
- Ai Use Case ScopingThe should-this-even-be-AI gate — decide where an LLM belongs versus deterministic rules, frame error tolerance as a product decision, and climb the capability ladder (rules → prompt → RAG → fine-tune) only as far as the problem demands. Stops the \"AI everywhere\" anti-pattern before it reaches the spec. Hosted by product-strategist / ai-prompt-architect.Votes: 0GitHub stars: 3
- Ai Ux PatternsThe UX patterns that don't exist in deterministic software — confidence display, graceful failure, reversibility, human-in-the-loop, and progressive disclosure — for designing trustworthy probabilistic features. Grounded in Google PAIR (People + AI Guidebook) and Apple HIG for ML. Turns \"how should the AI feature behave when it's unsure or wrong\" from ad-hoc choices into a checklist.Votes: 0GitHub stars: 3
- Ansoff MatrixGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.Votes: 0GitHub stars: 3
- Beachhead SegmentIdentify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.Votes: 0GitHub stars: 3
- Blue Ocean StrategyCreate uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions \"blue ocean\", \"red ocean\", \"strategy canvas\", \"ERRC framework\", \"value innovation\", \"non-customers\", \"buyer utility map\", \"eliminate-reduce-raise-create\", or \"uncontested market\". Also trigger when comparing pricing strategies, exploring new market categories, finding underserved customer segments, or asking how to stop competing on price. Covers the Four Acti...Votes: 0GitHub stars: 3
- Brainstorm OkrsBrainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.Votes: 0GitHub stars: 3
- Business ModelGenerate a Business Model Canvas with all 9 building blocks. Use when creating a business model, documenting how a business creates value, or analyzing an existing business model.Votes: 0GitHub stars: 3
- Circles MethodLewis Lin's CIRCLES framework for structured product-design answers — Comprehend the situation, Identify the customer, Report customer needs, Cut through prioritization, List solutions, Evaluate trade-offs, Summarize the recommendation. Use when answering a \"design a product/feature for X\" question, structuring a product-sense decision, or making sure a design proposal didn't skip the customer or the prioritization step.Votes: 0GitHub stars: 3
- Climate MrvPlaybook for climate / carbon Measurement-Reporting-Verification — GHG Protocol Scope 1/2/3, SBTi targets, CDP disclosure, EU CBAM, EPA GHGRP, ISO 14064, double-counting prevention, attestation.Votes: 0GitHub stars: 3
- Cohort AnalysisRead retention curves and adoption trends by cohort and decide what is real signal vs noise. Use when analyzing retention by cohort, studying feature adoption over time, investigating churn, or comparing cohorts — to reach a defensible PM judgement, not just a chart.Votes: 0GitHub stars: 3
- Competitive AnalysisPlaybook for competitive teardowns, market sizing (TAM/SAM/SOM), and positioning-gap analysis. Used by market-analyst.Votes: 0GitHub stars: 3
- Competitive BattlecardCreate sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'Votes: 0GitHub stars: 3
- ConnectorsHow great-pm agents read and write external tools (Notion, Slack, Linear, Jira, analytics) through the model-agnostic connector layer — the same way on every AI platform.Votes: 0GitHub stars: 3
- Consumer PrivacyPlaybook for consumer-privacy compliance — CCPA / CPRA (California), state privacy laws (VA / CO / CT / UT / TX / others), India DPDP overlay, sensitive-data special handling, opt-out signals, do-not-sell.Votes: 0GitHub stars: 3