product-planning

Plugin product-planning from marketplace modootoday in modootoday/marketplace. Commands read from the repo's manifest — 23 days ago.

Skills (13)

• customer-discovery-kit

  Build a customer discovery kit that tests named hypotheses instead of collecting compliments - an interview questionnaire in blocks (situation, tool mix, procedures and authors, operating pain, trust and security, willingness to pay, close) with each question tagged by the hypothesis it tests, a rec

• exec-decision-memo

  Write a one-page decision memo a busy decision-maker can act on - the decision needed and by when, the recommendation first, three real options compared on the same criteria with their cost of reversal, the evidence and what is assumed, the risks, and the exact approval being asked for. Use when a c

• flow-diagram-completeness-check

  Check a workflow or process flow, given as a diagram description, list of steps or arrows, for missing branches, dead ends and loops with no exit - enumerate every node and edge first, check that each decision has an edge for every outcome and each path reaches an end, list each loop with its exit c

• idea-sparring

  Spars on a rough product or feature idea instead of listing ideas - asks the few questions that would change the answer, argues against each option, and narrows to one thing to test first. Use when the user asks to brainstorm, spar on, pressure-test or "think through" an idea, or asks what to try fi

• pilot-scope-sizing

  Size one workflow as S, M or L before quoting a pilot that turns it into an AI skill - mark six criteria (where the rules live, number of rules and exceptions, evaluation cases, data and tool links, approval steps, security conditions), apply the count rule, show each mark with its evidence, and fla

• prd-writing-ko

  Write a product requirements document in Korean - problem, goal and metric, users, scope and non-goals, requirements with testable acceptance criteria, screen copy and open questions - with every assumption marked. Use when the user asks for a PRD, a planning document or a requirements specification

• prioritization-scoring

  Ranks a backlog with an explicit scoring method (RICE unless the user names another), showing each item's arithmetic, labelling every estimated input, flagging ranks too close to trust, and naming the one assumption that would change the top pick. Use when the user asks to prioritize, rank or score

• problem-framing

  Frames the problem behind a feature request or a vague goal - who is stuck, where, what evidence exists, how success would be observed, and what is out of scope - as a draft with its assumptions marked. Use when the user asks to frame a problem, write a problem statement, or work out what problem a

• project-plan-scope-and-schedule-check

  Draft and check the paperwork of a small project plan with the arithmetic shown - a charter (objective, in and out of scope, deliverables, assumptions, approvers), a work breakdown with an owner and estimate basis per task and a check that no deliverable lacks a task, a schedule check (critical path

• project-status-rollup-from-sources

  Roll up a weekly status, daily brief, completion history or epic history from several sources - chat channels, tickets, repositories, spreadsheets - stating the time window and the sources queried or unavailable, citing a link and date for every item, separating done, in progress, blocked and slippe

• requirement-to-testable-stories

  Break a feature request or technical brief into user stories whose acceptance criteria are checkable Given/When/Then statements, with vague words such as quickly, secure or easy flagged as unmeasurable and turned into a question for a value, dependencies and build order between stories, assumptions

• stakeholder-notes-to-requirements-trace

  Consolidate scattered stakeholder notes, meeting transcripts and legacy solution-centric documents into business requirements that each carry a source quote, speaker or document and date, with business needs separated from proposed solutions, conflicts and duplicates across sources recorded, and gap

• user-feedback-synthesis

  Synthesizes a batch of raw user feedback, tickets, reviews or interview notes into themes that cite the item ids behind them, ranks severity apart from frequency, escalates single severe reports, and separates what users asked for from the need behind it. For free-text survey answers it also account