product-onboarding

Plugin product-onboarding from marketplace meerkat-product in BrunoL28/product-onboarding-skill. Commands read from the repo's manifest — 1 month ago.

Skills (20)

• company-research

  Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.

• epic-breakdown-advisor

  Break down epics into user stories with Humanizing Work split patterns. Use when a backlog item is too large to estimate, sequence, or deliver safely.

• epic-hypothesis

  Frame an epic as a falsifiable hypothesis - target user, the change you believe you will cause, the signal that confirms it, the signal that stops you, and the cheapest test. Use in delivery planning before an epic is prioritised, split, or committed to a roadmap.

• jobs-to-be-done

  Uncover the job a customer hires a product to do - the job statement, its functional, emotional and social dimensions, the four forces of progress, and the pains and gains around it. Use when a team is arguing about features before agreeing what progress the customer is trying to make, when repositi

• lean-ux-canvas

  Guide teams through Lean UX Canvas v2. Use when framing a business problem, surfacing assumptions, and defining what to learn next.

• opportunity-solution-tree

  Work backwards from a stakeholder feature request to the outcome it was meant to serve, then branch into opportunities - customer needs, pains and desires drawn from research - then candidate solutions, then the assumption tests that decide between them. Use when a request, a mandate, or a vague OKR

• pestel-analysis

  Analyze political, economic, social, technological, environmental, and legal forces. Use when external market shifts could materially affect a product, roadmap, or strategy.

• pol-probe-advisor

  Match a Proof of Life probe to the assumption it has to kill, with the kill criterion written before the probe runs. Use in Phase 2 when a Lean UX Canvas Box 7 or opportunity solution tree assumption needs the cheapest test that could stop the build.

• positioning-workshop

  Build a positioning statement plus the differentiation reasoning behind it - target customer, market category, unmet need, key benefit, primary alternative, and proof. Use when a product needs a defensible market frame before messaging, roadmap, or launch.

• prd-development

  Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.

• prioritization-advisor

  Choose the right prioritization framework for your stage and context, then score and rank the backlog with it. Covers RICE, ICE, Value vs Effort, Kano, MoSCoW, WSJF, and Opportunity Scoring, with each framework's characteristic failure mode named. Use when a backlog needs ordering, when stakeholders

• problem-statement

  Write a user-centered problem statement with who is blocked, what they are trying to do, why it matters, and how it feels. Use when framing discovery, prioritization, or a PRD.

• product-onboarding

  Onboard a brand-new product end to end, from a raw idea to a board-ready backlog, by orchestrating nineteen bundled product-management skills across six phases: Framing (positioning-workshop, jobs-to-be-done), Discovery (company-research, pestel-analysis, tam-sam-som-calculator, proto-persona, probl

• product-strategy-session

  Run the closing product strategy session over work that already exists: coherence-check positioning, problem statement, PRD, backlog and roadmap against each other, run a premortem, test whether the biggest bet is really the biggest bet, and close with a decision log of owners and dates. Use as Phas

• proto-persona

  Create a proto-persona from current research, market signals, and team knowledge. Use when you need a working customer profile before deeper validation.

• roadmap-planning

  Turn a ranked backlog into a sequenced, outcome-bearing roadmap - Now/Next/Later, theme-based, or timeline - with dependencies mapped, a walking skeleton first, capacity validated with engineering, and confidence decay stated on the artifact itself. Use when prioritization has produced an order but

• tam-sam-som-calculator

  Size a market top-down and bottom-up, reconcile the two models, and report a confidence band with every assumption named and sourced. Use in discovery when someone asks how big the opportunity is and the number has to survive an executive review.

• user-story

  Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.

• workshop-facilitation

  Supply the guided-conversation protocol for a working session - question budgets, one question at a time, three context-aware options plus Other, the standing bypasses, loop control, and timeboxing - plus the multi-participant moves a room needs: speaking order, divergence before convergence, dot vo

• write-spec

  Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.

Similar plugins