product-discovery
Use when validating product opportunities, mapping assumptions, planning discovery sprints, or testing problem-solution fit before committing delivery resources.
What this skill does
# Product Discovery Run structured discovery to identify high-value opportunities and de-risk product bets. ## When To Use Use this skill for: - Opportunity Solution Tree facilitation - Assumption mapping and test planning - Problem validation interviews and evidence synthesis - Solution validation with prototypes/experiments - Discovery sprint planning and outputs ## Core Discovery Workflow 1. Define desired outcome - Set one measurable outcome to improve. - Establish baseline and target horizon. 2. Build Opportunity Solution Tree (OST) - Outcome -> opportunities -> solution ideas -> experiments - Keep opportunities grounded in user evidence, not internal opinions. 3. Map assumptions - Identify desirability, viability, feasibility, and usability assumptions. - Score assumptions by risk and certainty. Use: ```bash python3 scripts/assumption_mapper.py assumptions.csv ``` 4. Validate the problem - Conduct interviews and behavior analysis. - Confirm frequency, severity, and willingness to solve. - Reject weak opportunities early. 5. Validate the solution - Prototype before building. - Run concept, usability, and value tests. - Measure behavior, not only stated preference. 6. Plan discovery sprint - 1-2 week cycle with explicit hypotheses - Daily evidence reviews - End with decision: proceed, pivot, or stop ## Opportunity Solution Tree (Teresa Torres) Structure: - Outcome: metric you want to move - Opportunities: unmet customer needs/pains - Solutions: candidate interventions - Experiments: fastest learning actions Quality checks: - At least 3 distinct opportunities before converging. - At least 2 experiments per top opportunity. - Tie every branch to evidence source. ## Assumption Mapping Assumption categories: - Desirability: users want this - Viability: business value exists - Feasibility: team can build/operate it - Usability: users can successfully use it Prioritization rule: - High risk + low certainty assumptions are tested first. ## Problem Validation Techniques - Problem interviews focused on current behavior - Journey friction mapping - Support ticket and sales-call synthesis - Behavioral analytics triangulation Evidence threshold examples: - Same pain repeated across multiple target users - Observable workaround behavior - Measurable cost of current pain ## Solution Validation Techniques - Concept tests (value proposition comprehension) - Prototype usability tests (task success/time-to-complete) - Fake door or concierge tests (demand signal) - Limited beta cohorts (retention/activation signals) ## Discovery Sprint Planning Suggested 10-day structure: - Day 1-2: Outcome + opportunity framing - Day 3-4: Assumption mapping + test design - Day 5-7: Problem and solution tests - Day 8-9: Evidence synthesis + decision options - Day 10: Stakeholder decision review ## Tooling ### `scripts/assumption_mapper.py` CLI utility that: - reads assumptions from CSV or inline input - scores risk/certainty priority - emits prioritized test plan with suggested test types See `references/discovery-frameworks.md` for framework details.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.