All authors
Claude Skills by VandanaAjayDubey111
github.com/VandanaAjayDubey111193 skills4 installs169 views
- Pm GateExplicit gate approval for great-pm. Under gate-policy: explicit (great-pm's default), agents NEVER auto-close gates — only this command does. Subcommands: approve <id> | reject <id> <reason> | list | show <id>.Votes: 0GitHub stars: 3
- Pm HelpList all great-pm commands and what each does, grouped by stage / purpose.Votes: 0GitHub stars: 3
- Pm InboxShow all pending great-pm gates and decisions waiting on the human. Surfaces gate:strategy, gate:spec, and gate:launch, plus any blocked agents.Votes: 0GitHub stars: 3
- Pm LaunchKick off the Launch stage. Spawns launch-manager (rollout plan) + gtm-strategist (positioning + comms) IN PARALLEL. Outputs launch-plan + GTM-plan feeding gate:launch.Votes: 0GitHub stars: 3
- Pm LearnAuto-extract repeatable patterns, decisions, and cost outliers from the current session and append to .great-pm/lessons.md. Promotes ≥3-occurrence patterns to ~/.great-pm/decisions.md. Runs continuous-learner.Votes: 0GitHub stars: 3
- Pm MeasureKick off the Measure & Learn stage. Spawns analytics-analyst (read-out) + experiment-designer (next test). Outputs performance read-out and feeds 2–3 next questions back into Discover (the loop closes).Votes: 0GitHub stars: 3
- Pm MetricsAuthor a metrics plan BEFORE the build. Defines North Star, leading + lagging KPIs, instrumentation events, success thresholds, and baselines. Runs metrics-architect.Votes: 0GitHub stars: 3
- Pm OwnershipShow who owns what across initiatives, gates, drafts, and Beads issues. Surfaces orphaned artefacts (no owner) and over-loaded owners.Votes: 0GitHub stars: 3
- Pm PocLightweight discovery mode for \"I'm not sure this is worth investigating fully.\" Produces a 1-pager (Problem / Assumed solution / 3 risks) + pre-mortem-lite, skipping the full 6-stage loop until the PoC validates.Votes: 0GitHub stars: 3
- Pm PricingAuthor or refresh a pricing plan — 2–3 monetization models with willingness-to-pay rationale per audience. Spawns pricing-strategist.Votes: 0GitHub stars: 3
- Pm PrioritizeKick off the Prioritize stage. Spawns prioritization-analyst (RICE/WSJF/Kano/MoSCoW), then tradeoff-arbiter if conflicts surface. Outputs a ranked backlog feeding gate:strategy.Votes: 0GitHub stars: 3
- Pm PromotePromote a draft artefact (strategy / spec / launch plan / etc.) to a gate-ready Beads issue. Runs mandatory pm-reviewer pass first; PASS verdict is required to promote.Votes: 0GitHub stars: 3
- Pm ResumePick up where you left off. Reads `.great-pm/HANDOFF.md` (auto-saved by the PreCompact hook) and orients you with the next concrete step.Votes: 0GitHub stars: 3
- Pm ReviewTrigger pm-reviewer on any artefact (draft, gate package, agent output). Returns the verdict unedited. Logs to .great-pm/verdicts/.Votes: 0GitHub stars: 3
- Pm RfcWrite a product RFC (Request for Comments) on a proposed strategic direction or architectural product decision. Forces 2–3 options + costs + reversibility BEFORE you commit.Votes: 0GitHub stars: 3
- Pm RoadmapGenerate or update the product roadmap. Spawns roadmap-planner. Outputs themed roadmap (Now / Next / Later) with rationale per theme.Votes: 0GitHub stars: 3
- Pm SaveExtract lessons from this session and save them to .great-pm/lessons.md. Optional cross-project promotion to ~/.great-pm/decisions.md for patterns seen 3+ times (proposed, never auto-promoted).Votes: 0GitHub stars: 3
- Pm SpecKick off the Define stage. Spawns spec-writer (PRD) and spec-reviewer (mechanical clarity check). Outputs a PRD ready for gate:spec.Votes: 0GitHub stars: 3
- Pm StartStart a new great-pm initiative. Spawns the Discover stage (user-researcher + feedback-synthesizer + market-analyst in parallel) and runs the loop through to gate:strategy.Votes: 0GitHub stars: 3
- Pm StrategizeKick off the Strategize stage. Spawns product-strategist (lead) with optional pricing-strategist support. Reads discovery + competitive briefs, outputs a strategy doc with falsifiable bets.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 trigg...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 ...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