jonwoods79-sys
UserAn AI OS for Product Managers. 58 skills, 40 commands, 10 plugins - built for Claude Code and any AI assistant.
Categories
Indexed Skills (42)
assumption-mapping
Map and prioritise the riskiest assumptions behind a product idea or feature before committing to building. Surfaces hidden risks across Value, Usability, Feasibility, and Viability using Cagan's Four Risks. This is a THINK skill — it gates the EXECUTE phase. Do not write a PRD until assumption mapping is complete. Use BEFORE experiment-design — this picks which assumption to test.
beachhead-segment
Identify the best first beachhead market segment — the narrowest customer group where you can win decisively before expanding. Based on Geoffrey Moore's beachhead strategy. Use before building a GTM plan or when deciding which customer to serve first.
business-model
Design or analyse a business model using the right canvas for the context — Lean Canvas (new products / startups), Business Model Canvas (established businesses), or Startup Canvas (combining strategy + business model). Each surfaces different strategic questions.
comms
Write internal communications for any audience — team updates, exec briefings, bad news, board updates, investor updates, exec presentations, and roadmaps (customer, team, exec, sales). Same principle across all modes: lead with the conclusion, support with evidence, name the ask. Trigger on: "draft stakeholder comms", "board update", "investor update", "board deck", "exec preso", "QBR", "executive presentation", "present to the board", "present to the CEO", "team update", "status update", "bad news", "roadmap", "communicate the roadmap", "customer roadmap", "internal roadmap", "exec roadmap", "roadmap update", "what's on the roadmap", "share the roadmap", "now next later", "NNL".
competitive-analysis
Analyse competitors or a competitive landscape. Two modes: scan (recurring monitoring of what changed across competitors) and teardown (deep one-off analysis of a single competitor or market using Dunford alternatives + Helmer 7 Powers). Use scan before strategy docs, after competitor announcements, or quarterly. Use teardown for a pitch, investment decision, or positioning review. Trigger on: "competitive analysis", "competitive scan", "comp teardown", "analyse this competitor", "what changed with X", "competitive landscape", "7 powers analysis", "what's their moat", "what are competitors doing", "monitor competitors".
customer-interviewing
Plan, structure, and debrief customer discovery interviews. Use whenever the user needs to conduct user research, prepare for customer interviews, analyse interview transcripts, or build a continuous discovery practice. Trigger on: "prepare for customer interviews", "help me write interview questions", "analyse this interview transcript", "how do I do discovery interviews", "continuous discovery", "weekly customer interviews", "user research plan", "what should I ask users", "interview guide". Also trigger when a user wants to understand JTBD through interviews.
customer-journey-map
Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and product opportunities. Use to understand the full customer experience beyond the product's core flow — from awareness through to advocacy or churn.
decision-memo
Write a decision memo — a structured document that captures a significant decision, its rationale, alternatives considered, and implications. Use whenever the user needs to document a one-way-door decision, align stakeholders on a choice, or get explicit sign-off on a direction. Trigger on: "write a decision memo", "decision doc", "SPADE", "DACI", "document this decision", "help me get alignment on this decision", "write up this decision", "how do I communicate this choice", "decision log". Also trigger when the user describes a significant product, technical, or strategic decision and needs to formalise it.
devils-advocate
Self-review critique for any doc before sharing (pre-share mode), or forward-looking failure analysis before a launch or major initiative (pre-launch mode). Use pre-share before sending a PRD, strategy doc, or customer outreach. Use pre-launch to surface Tigers, Paper Tigers, and Elephants with a GO/NO-GO/MODIFY verdict. Trigger on: "devils advocate", "poke holes in this", "stress test this doc", "run pre-mortem", "what kills us if", "failure analysis", "pre-mortem". Produces critique/failure-modes, NOT a go/kill verdict; for a formal gate use prd-review.
experiment-design
Design lean experiments to test product assumptions before building. Covers both lightweight pretotypes (Alberto Savoia) for testing demand, and structured experiments for testing usability and feasibility. Outputs a testable experiment with success criteria. Use AFTER assumption-mapping has identified the assumption to test.
friction-log
Write a friction log — a persona-grounded first-person walkthrough of a product experience that captures what works, what doesn't, and what needs to change. Use whenever the user wants to evaluate a product's quality from the user's perspective, audit an onboarding or key user flow, review a competitor's product, or conduct a structured UX quality review. Trigger on: "friction log", "walk the store", "product walkthrough", "UX audit", "onboarding review", "experience review", "what's broken in this flow", "review this product from a user's perspective", "competitor walkthrough". Especially useful for API and developer products.
gtm-planning
Plan a go-to-market strategy. Requires positioning to be defined before GTM is written — a GTM plan without a positioning foundation is built on sand. Includes growth motion selection (PLG/SLG/MLG), beachhead definition, channel strategy, and launch sequencing. Produces a PROCEED/CONDITIONAL/NOT READY verdict.
handoff-audit
Handoff process linter. Verifies artifact pipeline integrity and "Trio" perspectives (Design/Eng) for Discovery→Design and Design→Eng handoffs. Trigger on: "handoff audit", "readiness audit", "are we ready to hand off", "design handoff check", "eng handoff check". Distinct from launch-readiness (go/no-go launch gate) — this checks artefact/perspective readiness at a phase handoff, not launch readiness.
ideation
Generate ideas for a product area or problem. Two modes: standard (PM, Design, and Eng lenses with prioritised shortlist) and constraint (opposing extreme constraints to break incremental thinking). Use standard when you need to move from a goal to specific testable solutions. Use constraint when the team keeps generating the same ideas or is stuck in incremental thinking. Trigger on: "brainstorm ideas", "brainstorm", "ideation", "generate ideas", "constraint brainstorm", "10x ideas", "break out of incremental", "we keep coming up with the same ideas", "force new thinking".
launch-readiness
Assess whether a product, feature, or integration is ready to launch. Use whenever the user needs to confirm all dependencies are covered before going live — across product, engineering, legal, compliance, ops, support, marketing, and commercial. Trigger on: "launch readiness", "are we ready to launch", "go/no-go", "launch checklist", "pre-launch review", "what do we need before we launch", "launch gate review", "soft launch readiness", "beta readiness". Distinct from gtm-planning (strategic) — this skill is operational and launch-specific. Distinct from handoff-audit (handoff process linter) — this is the go/no-go launch gate.
lenny-lookup
Find and rank Lenny's Podcast episodes relevant to a topic or question. Returns 3–5 episodes with brief reasoning and file paths for direct reading. Trigger on: "find Lenny episodes on", "search the corpus for", "what has Lenny said about", "lenny-lookup", "look up Lenny", "search transcripts".
market-research
Structured market analysis covering macro environment and market sizing. Two modes: analysis (SWOT, PESTLE, Porter's Five Forces, Ansoff Matrix) and sizing (TAM/SAM/SOM top-down and bottom-up). Use analysis before strategy work or evaluating a new market. Use sizing for fundraising, investment decisions, or GTM planning. Trigger on: "market analysis", "market sizing", "TAM SAM SOM", "SWOT", "PESTLE", "Porter's Five Forces", "how big is this market", "is this market worth entering", "macro environment scan".
meeting-notes
Summarise a meeting transcript or notes into structured output — decisions made, action items with owners, open questions, and follow-up. Optionally saves a structured file to the repo. Works for any meeting type: planning, review, stakeholder alignment, customer call, or design critique. Trigger on: "log these meeting notes", "save this meeting", "capture this discussion", "post meeting notes", paste meeting notes or transcript.
metrics-framework
Analytics hub — four modes. Lookup: answer "how do we measure X?" from canonical definitions. Framework: define what success looks like — north star, input metrics, guardrails, OKRs. Cohort: read retention curves, diagnose PMF signal, find drop-off, recommend actions. AB Test: validity check, statistical significance, guardrails → ship/stop/extend/iterate verdict. Every framework output includes a metric quality gate. No metric without a baseline, target, and timeframe. Trigger on: "how do we measure X", "what's the formula for X", "define this metric", "write a metrics framework", "north star", "OKRs", "guardrails", "cohort analysis", "retention curve", "PMF signal", "week-N retention", "feature adoption cohort", "A/B test results", "analyse this test", "ship or stop", "statistical significance", "sample size".
okr-architect
Audit, improve, or write OKRs. Every proposed Key Result is tested against a strict outcome/task filter — tasks masquerading as KRs are identified and rewritten. Produces a scored OKR set with a mandatory quality verdict. Also supports NCT (Narratives/Commitments/Tasks) format as an OKR alternative. Trigger on: "write OKRs", "review OKRs", "OKR planning", "are these good OKRs", "audit my OKRs", "KRs are too task-based", "NCTs", "/okr-architect".
onboard
Interactive first-time setup for this Team OS. Interviews a new team on company name, team roster, Slack channels, product metrics, competitors, tools, and working style. Writes to AGENTS.md, knowledge/metrics/definitions.md, and CONNECTIONS.md.
opportunity-solution-tree
Build an Opportunity Solution Tree (OST) to visually connect a desired outcome to customer opportunities, potential solutions, and assumption tests. Based on Teresa Torres's Continuous Discovery Habits. Use to align a product team on what to work on and why.
org-os-updates
Weekly summary of what changed in the repo — new skills, modified workflows, updated knowledge, ownership changes. Designed to post to a Slack channel so the team sees the OS moving and knows what's available. Run manually or on a schedule. Trigger on: "post OS updates", "what changed in the repo this week", "org-os-updates", "summarise repo changes".
pr-faq
Write an Amazon-style Press Release / FAQ (PR/FAQ) for a new product, feature, or strategic bet. Use whenever the user needs to define a new product idea by working backwards from the customer — before committing to building it. Trigger on: "write a PR/FAQ", "press release FAQ", "working backwards", "amazon style doc", "define this product idea", "write a press release for this feature", "help me think through this from the customer's perspective", "vision doc for this product". Best used for significant new bets, new market entries, or any initiative where the team hasn't fully aligned on what success looks like from the customer's point of view.
prd-review
Review PRDs against Cagan's Four Risks (quick/deep modes), or evaluate ideas before significant investment (kill-gate mode). Produces a scored verdict and a KILL/PIVOT/PROCEED gate for ideas. Trigger on: "review this PRD", "PRD review", "check this spec", "should we build this", "kill or continue", "evaluate this idea", "is this worth pursuing". Produces a go/kill VERDICT; for open-ended critique use devils-advocate.
prd
Write a Product Requirements Document for a feature or product. Use whenever the user needs a full PRD — not a lightweight brief (use strategic-brief). Trigger on: "write a PRD", "PRD for [feature]", "product requirements document", "write up requirements", "spec this feature".
pricing-strategy
Design a pricing strategy — model selection, price points, competitive positioning, and validation experiments. Covers B2B SaaS, consumer, marketplace, and usage-based pricing. Outputs a pricing recommendation with rationale and a willingness-to-pay experiment.
prioritisation
Prioritise a backlog or set of initiatives using the right framework for the decision — RICE, ICE, WSJF, MoSCoW, Kano, or Now/Next/Later. Includes a mandatory not-doing list and a gate that prevents high-scoring items with low discovery confidence from proceeding.
product-leadership
Leadership-tier skill for heads of product. Four modes: hiring (PM interview loop, scorecard, hire/no-hire), rituals (product operating model — planning cadence, decision rights, communication norms), org-topology (org structure design against Conway's Law), coaching (PM development — diagnosis, SBI feedback, 90-day plans, performance conversations). Trigger on: "PM hiring", "interview process", "evaluate this candidate", "PM scorecard", "hire/no-hire", "PM job description", "PM levels", "product operating model", "team rituals", "planning cadence", "how do we make decisions", "we have too many meetings", "nothing is getting decided", "how should I structure my product team", "org design", "team topology", "how many PMs do I need", "PM performance review", "give feedback to my PM", "coach this PM", "PM development plan", "how do I grow my PM", "PM isn't performing", "skip-level feedback".
product-strategy
Write, critique, or structure a product strategy (default mode), or craft a product vision (vision mode). Strategy mode defines where to play, how to win, what moat to build, and what to explicitly not do — using DHM, SMT lock-ups, and Helmer's 7 Powers. Vision mode crafts an inspiring, customer-centred north star with transformed-life paragraph, exclusions, and headline test. Trigger on: "product strategy", "product vision", "north star", "vision statement", "what's our strategy".
research-synthesis
Synthesise customer interviews, research notes, support data, or transcripts into structured insights, product opportunities, and evidence-grounded personas. Produces themes, JTBD statements, an Opportunity Solution Tree, and (optionally) named personas or an ICP derived from the data. This is a THINK skill — output feeds directly into assumption-mapping and /prd. Do not proceed to execution without validated insights. Trigger on: "user personas", "create a persona", "ICP", "ideal customer profile", "who should we build for", "who is our customer", "customer profile".
retro
Facilitate or synthesise a sprint retrospective, project retrospective, or blameless post-mortem. Trigger on: "run a retro", "retrospective", "sprint retro", "post-mortem", "what went well what didn't", "synthesise these retro notes", "retro action items". Distinct from devils-advocate (forward-looking) — this is backward-looking.
review-as
Review any artefact through one or more named lenses — stakeholder review styles, reusable frameworks, or quality bars. Fans out across lenses in parallel, synthesises agreements and contradictions, and produces a scored verdict with per-lens fix lists. Gated: overall below 3.0 returns to author.
roadmap
Build or update a living product roadmap artefact (themes → outcomes → initiatives, Now/Next/Later horizons, confidence + gate metrics + dependencies). Trigger on: "build the roadmap", "update the roadmap", "create a roadmap", "roadmap for [quarter/product]", "what's our roadmap". Produces/maintains the roadmap ARTEFACT. To communicate it use comms (roadmap modes); to rank what goes on it use prioritisation.
roi-modeler
Feature-level unit economics and payback period math. Translates effort into build cost and impact into months-to-payback. Use to justify significant roadmap bets to leadership.
sprint-planning
Plan a sprint or iteration — convert a prioritised backlog into a committed, capacity-aware sprint scope with a sprint goal, explicit exclusions, and trade-off documentation. Trigger on: "sprint planning", "plan the sprint", "iteration planning", "what should we commit to", "sprint scope", "sprint goal", "capacity planning", "sprint kickoff".
strategic-brief
Write a strategic brief — a tight narrative document for stakeholder alignment or executive sign-off. Two modes: alignment (internal 1-pager for team buy-in or scoping) and exec (recommendation-first for C-suite/board approval or resourcing). Trigger on: "write a brief", "one-pager", "product brief", "summarise this idea", "pitch this internally", "get exec buy-in", "alignment brief", "brief the CEO", "strategic brief", "opportunity assessment".
summarize-interview
Summarise a single customer call — interview, discovery session, check-in, sales call, or churn conversation. Two modes: quick capture (any call type, minimal structure, fast) and full synthesis (discovery interviews — JTBD, BEAM, Forces of Progress, signal quality). Both save to knowledge/customers/interviews/ and check for an existing account summary. Trigger on: "log this customer call", "save this interview", "capture this call", "summarise this interview", "process this transcript", "what did we learn from this call", "interview notes", paste a raw transcript.
technical-spike
Design and review technical spikes. Kills infinite research loops by forcing binary questions and falsifiable success signals. Use when Engineering needs to investigate feasibility before a PRD can be finalized.
test-scenarios
Generate comprehensive test scenarios from user stories, PRDs, or feature specs — covering happy paths, edge cases, error handling, and non-functional requirements. Outputs structured test cases QA and engineers can execute directly.
user-stories
Write high-quality user stories, job stories, or acceptance criteria for a feature or product area. Use whenever the user needs to translate a product brief, PRD, or design into well-structured stories that engineering can act on. Trigger on: "write user stories", "write job stories", "acceptance criteria", "story refinement", "break this into stories", "write the tickets for this", "story mapping", "how do I write this as a story", "BDD scenarios", "given when then". Also use when existing stories are vague or incomplete and need sharpening before sprint planning.
value-proposition
Define a clear, competitive value proposition. Covers the 6-part JTBD template (who, why, what before, how, what after, why us) and Dunford's competitive alternatives — the full set of what the customer would do if this product didn't exist. Use before writing messaging, a GTM plan, or a strategic brief. Trigger on: "value proposition", "value prop", "what's our value prop", "why should customers choose us", "positioning", "how are we different", "Dunford", "competitive positioning".
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.