lishix520
- 12 skills
- 0 followers
- 21 hours ago last updated
- ▌
- ▌
- ▌ Jtbd Principles · lishix520 bundleShared principles, terminology, evidence discipline, and core contracts for all Jobs-to-be-Done (JTBD) and Outcome-Driven Innovation (ODI) agent skills.
- ▌ Jtbd Job Mapper · lishix520 bundleDeconstruct a defined Core Functional Job into a chronological Universal Job Map across standard stages (define, locate, prepare, confirm, execute, monitor, modify, conclude). Use when asked to map the steps of a customer job, identify functional dependencies between steps, or uncover missing execution steps in a workflow. Do not use to write desired outcome statements, calculate opportunity scores, or recommend product strategy.
- ▌ Jtbd Job Definer · lishix520 bundleExtract, audit, or rewrite a solution-free and outcome-free Core Functional Job statement from customer quotes or candidate sentences. Use when given a proposed product feature or customer statement and asked to express the underlying functional job, audit a job statement for solution contamination, or determine if enough evidence exists to validate a job statement. Do not use to map job steps, write desired outcomes, calculate opportunity scores, or recommend product strategy.
- ▌ Jtbd Forces Analyzer · lishix520 bundleAnalyze Jobs-to-be-Done switching forces from interview excerpts, customer feedback, or structured context-explorer output. Use when asked to identify Push of the current situation, Pull of a prospective alternative, Habit of the current approach, Anxiety about switching, Big Hire or Little Hire signals, and evidence gaps in a possible customer switch. Do not use to define a Core Functional Job, predict purchase probability, score switching readiness, calculate opportunity, or recommend product strategy.
- ▌ Jtbd Context Explorer · lishix520 bundleExtract Jobs-to-be-Done context evidence from customer interviews, feedback, reviews, support tickets, or scenario descriptions. Use when asked to identify the circumstances that triggered a change, desired progress, current alternatives or workarounds, non-consumption, emotional or social signals, feature requests, constraints, competing solutions, and unanswered research questions. Do not use to define a Core Functional Job, calculate opportunity scores, or recommend product strategy.
- ▌ Jtbd Outcome Engineer · lishix520 bundleFormulate formulaic Desired Outcome Statements for a specific job map step using ODI metrics (time, likelihood, effort, cost, output). Use when given a job map step, qualitative pain point, or survey question and asked to express performance metrics, audit outcome statements, or prepare survey items for quantitative research. Do not use to calculate opportunity scores or recommend product strategy.
- ▌ Jtbd Switch Interview · lishix520 bundleInteractive interview guide and question generator for understanding why customers change behaviors, buy products, or switch solutions. Use when asked to design a customer interview, formulate non-leading follow-up questions, reconstruct a decision timeline, or avoid leading feature questions during customer discovery. Do not use to define a Core Functional Job, calculate opportunity scores, or recommend product strategy.
- ▌ Opportunity Discovery · lishix520 bundleTop-level evidence-aware orchestrator and router for product discovery. Classifies user input (product ideas, feedback, interview notes, or survey data), evaluates evidence readiness, routes to downstream skills, and outputs a Decision Brief detailing what can be concluded, what is only a hypothesis, and the smallest next validation step. Use as the primary entry point when given a new product idea, customer quote, or discovery material and asked what to validate next.
- ▌ Jtbd Growth Strategist · lishix520 bundleMap quantitative Opportunity Scores and market evidence to candidate growth strategies (differentiated, dominant, disruptive, discrete, sustaining). Use when given opportunity calculation results, segment metadata, and structured price/cost/performance evidence, and asked to evaluate strategic positioning or disconfirming evidence. Do not use to invent market evidence or recommend product strategy without required prerequisites.
- ▌ Jtbd Opportunity Calculator · lishix520 bundleCompute quantitative Outcome-Driven Innovation (ODI) Opportunity Scores from customer importance and satisfaction survey ratings. Use when given numerical survey data (1-10 scale), mean importance and satisfaction scores, or survey JSON/CSV files, and asked to compute opportunity scores, classify outcomes into opportunity tiers, or run the deterministic calculation script. Do not use to invent survey scores from qualitative text or recommend product strategy.