[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M749GYEQ01FQBNR8AMQV5325":3,"skill-same:01M749GYEQ01FQBNR8AMQV5325":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M749GYEQ01FQBNR8AMQV5325","interview-script",null,"Create a structured customer interview script with JTBD probing questions, warm-up, core exploration, and wrap-up sections. Follows The Mom Test principles — no leading questions, no pitching, focus on past behavior. Use when preparing for user interviews, creating interview guides, or planning discovery research.","phuryn\u002Fpm-skills","phuryn","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7837354?v=4","01M727RY5RDZZWVRDN2X5F4B1W","Pawel Huryn","01M727RY6H19NE8H5PABTR7A59",27991,"MIT","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-product-discovery\u002Fskills\u002Finterview-script\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: interview-script\ndescription: \"Create a structured customer interview script with JTBD probing questions, warm-up, core exploration, and wrap-up sections. Follows The Mom Test principles — no leading questions, no pitching, focus on past behavior. Use when preparing for user interviews, creating interview guides, or planning discovery research.\"\n---\n\n## Customer Interview Script\n\nCreate a structured interview script that surfaces real insights, not just opinions. Follows \"The Mom Test\" principles — ask about their life, not your idea.\n\n### Domain Context\n\nCustomer interviews are one source in **Stage 1 (Explore)** of continuous discovery. Other sources: stakeholder interviews, usage analytics, data analytics, surveys, market trends, SEO\u002FSEM analysis. The PM needs direct access to users, stakeholders, engineers, and designers — \"without proxies.\" The **Product Trio** (PM + Designer + Engineer — Teresa Torres) should work together on discovery, not just the PM alone.\n\n### Context\n\nYou are preparing a customer interview script for research on **$ARGUMENTS**.\n\nIf the user provides files (personas, hypothesis lists, product briefs, or previous interview notes), read them first.\n\n### Instructions\n\n1. **Clarify research objectives**:\n   - What specific questions does the team need answered?\n   - What decisions will this research inform?\n   - What assumptions need validation?\n\n2. **Create the interview script** with these sections:\n\n   ### Opening (2-3 min)\n   - Introduce yourself and the purpose (learning, not selling)\n   - Set expectations: \"There are no right or wrong answers. We're here to learn from your experience.\"\n   - Ask permission to record (if applicable)\n   - Confirm time available\n\n   ### Warm-Up: Context & Background (5 min)\n   - \"Tell me about your role and what a typical day\u002Fweek looks like.\"\n   - \"How long have you been doing [activity related to the product area]?\"\n   - Goal: Build rapport and understand their context\n\n   ### Core Exploration: Jobs to Be Done (15-20 min)\n\n   **Current situation and behavior** (past tense, specific instances):\n   - \"Walk me through the last time you [did the thing we're exploring]. What happened?\"\n   - \"What tools or methods did you use?\"\n   - \"How long did it take? Who else was involved?\"\n\n   **Pain points and frustrations** (observe, don't lead):\n   - \"What was the hardest part about that?\"\n   - \"If you could wave a magic wand, what would change?\"\n   - \"What have you tried to solve this? What happened?\"\n\n   **Desired outcomes** (their words, not yours):\n   - \"What does 'good' look like for you in this area?\"\n   - \"How would you know if this was working well?\"\n\n   **Willingness to pay \u002F priority** (skin in the game):\n   - \"How much time\u002Fmoney do you currently spend on this?\"\n   - \"Have you looked for a better solution? What did you find?\"\n   - \"What would you give up to have this solved?\"\n\n   ### Probing Techniques\n   Use these when you hit an interesting thread:\n   - **\"Tell me more about that\"** — opens up any topic\n   - **\"Why?\"** (asked gently, 2-3 times) — gets to root causes\n   - **\"Can you give me a specific example?\"** — moves from opinions to facts\n   - **\"What happened next?\"** — follows the story\n   - **\"How did that make you feel?\"** — captures emotional intensity\n\n   ### The Mom Test Rules\n   - Ask about **their life**, not your idea\n   - Ask about **the past**, not the future (\"Would you use X?\" is useless)\n   - **Talk less, listen more** — aim for 80\u002F20 split\n   - **Never pitch** during the interview\n   - Look for **strong emotions** — they signal real pain or delight\n   - **Compliments are noise** — \"That sounds cool!\" tells you nothing\n\n   ### Wrap-Up (3-5 min)\n   - \"Is there anything I didn't ask that you think is important?\"\n   - \"Who else should I talk to about this?\"\n   - Thank them for their time\n   - Share next steps (if any)\n\n3. **Customize the script**: Adapt questions to the specific product area, persona, and research objectives. Add or remove sections based on the interview length available.\n\n4. **Include a note-taking template**:\n   ```\n   Participant: [Name \u002F ID]\n   Date: [Date]\n   Key Jobs: [What they're trying to accomplish]\n   Current Solution: [What they use today]\n   Biggest Pain: [Their #1 frustration]\n   Desired Outcome: [What success looks like]\n   Willingness to Pay: [How much they invest \u002F would invest]\n   Surprise Finding: [Something unexpected]\n   Follow-up: [Next steps]\n   ```\n\nSave as markdown. Include both the script and the note-taking template.\n\n---\n\n### Further Reading\n\n- [User Interviews: The Ultimate Guide to Research Interviews](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Finterviewing-customers-the-ultimate)\n- [Continuous Product Discovery Masterclass (CPDM)](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fcpdm) (video course)\n","## Customer Interview Script\n\nCreate a structured interview script that surfaces real insights, not just opinions. Follows \"The Mom Test\" principles — ask about their life, not your idea.\n\n### Domain Context\n\nCustomer interviews are one source in **Stage 1 (Explore)** of continuous discovery. Other sources: stakeholder interviews, usage analytics, data analytics, surveys, market trends, SEO\u002FSEM analysis. The PM needs direct access to users, stakeholders, engineers, and designers — \"without proxies.\" The **Product Trio** (PM + Designer + Engineer — Teresa Torres) should work together on discovery, not just the PM alone.\n\n### Context\n\nYou are preparing a customer interview script for research on **$ARGUMENTS**.\n\nIf the user provides files (personas, hypothesis lists, product briefs, or previous interview notes), read them first.\n\n### Instructions\n\n1. **Clarify research objectives**:\n   - What specific questions does the team need answered?\n   - What decisions will this research inform?\n   - What assumptions need validation?\n\n2. **Create the interview script** with these sections:\n\n   ### Opening (2-3 min)\n   - Introduce yourself and the purpose (learning, not selling)\n   - Set expectations: \"There are no right or wrong answers. We're here to learn from your experience.\"\n   - Ask permission to record (if applicable)\n   - Confirm time available\n\n   ### Warm-Up: Context & Background (5 min)\n   - \"Tell me about your role and what a typical day\u002Fweek looks like.\"\n   - \"How long have you been doing [activity related to the product area]?\"\n   - Goal: Build rapport and understand their context\n\n   ### Core Exploration: Jobs to Be Done (15-20 min)\n\n   **Current situation and behavior** (past tense, specific instances):\n   - \"Walk me through the last time you [did the thing we're exploring]. What happened?\"\n   - \"What tools or methods did you use?\"\n   - \"How long did it take? Who else was involved?\"\n\n   **Pain points and frustrations** (observe, don't lead):\n   - \"What was the hardest part about that?\"\n   - \"If you could wave a magic wand, what would change?\"\n   - \"What have you tried to solve this? What happened?\"\n\n   **Desired outcomes** (their words, not yours):\n   - \"What does 'good' look like for you in this area?\"\n   - \"How would you know if this was working well?\"\n\n   **Willingness to pay \u002F priority** (skin in the game):\n   - \"How much time\u002Fmoney do you currently spend on this?\"\n   - \"Have you looked for a better solution? What did you find?\"\n   - \"What would you give up to have this solved?\"\n\n   ### Probing Techniques\n   Use these when you hit an interesting thread:\n   - **\"Tell me more about that\"** — opens up any topic\n   - **\"Why?\"** (asked gently, 2-3 times) — gets to root causes\n   - **\"Can you give me a specific example?\"** — moves from opinions to facts\n   - **\"What happened next?\"** — follows the story\n   - **\"How did that make you feel?\"** — captures emotional intensity\n\n   ### The Mom Test Rules\n   - Ask about **their life**, not your idea\n   - Ask about **the past**, not the future (\"Would you use X?\" is useless)\n   - **Talk less, listen more** — aim for 80\u002F20 split\n   - **Never pitch** during the interview\n   - Look for **strong emotions** — they signal real pain or delight\n   - **Compliments are noise** — \"That sounds cool!\" tells you nothing\n\n   ### Wrap-Up (3-5 min)\n   - \"Is there anything I didn't ask that you think is important?\"\n   - \"Who else should I talk to about this?\"\n   - Thank them for their time\n   - Share next steps (if any)\n\n3. **Customize the script**: Adapt questions to the specific product area, persona, and research objectives. Add or remove sections based on the interview length available.\n\n4. **Include a note-taking template**:\n   ```\n   Participant: [Name \u002F ID]\n   Date: [Date]\n   Key Jobs: [What they're trying to accomplish]\n   Current Solution: [What they use today]\n   Biggest Pain: [Their #1 frustration]\n   Desired Outcome: [What success looks like]\n   Willingness to Pay: [How much they invest \u002F would invest]\n   Surprise Finding: [Something unexpected]\n   Follow-up: [Next steps]\n   ```\n\nSave as markdown. Include both the script and the note-taking template.\n\n---\n\n### Further Reading\n\n- [User Interviews: The Ultimate Guide to Research Interviews](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Finterviewing-customers-the-ultimate)\n- [Continuous Product Discovery Masterclass (CPDM)](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fcpdm) (video course)\n",{"name":5,"description":7},"main","9af7bfd0bc47fdad43c2eaa7a43cd13918e7aaef","pm-product-discovery\u002Fskills\u002Finterview-script",2885,"https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills","https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fpm-skills-2-red-team-ship","https:\u002F\u002Fgithub.com\u002Fphuryn","https:\u002F\u002Fwww.productcompass.pm\u002F","AI PM Coach, ex-CPO, Builder | 400K+ Follow","2026-11-09 07:10:04",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add phuryn\u002Fpm-skills --skill interview-script",{"tool":40,"command":41},"bunx","bunx skills add phuryn\u002Fpm-skills --skill interview-script",{"tool":43,"command":44},"pnpm","pnpm dlx skills add phuryn\u002Fpm-skills --skill interview-script","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-product-discovery\u002Fskills\u002Finterview-script\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M749K1XJGDQ1FA90BGD6MJ6Z","review-resume","Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-toolkit\u002Fskills\u002Freview-resume\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M749JVQ3SER9X0V501S82BRX","privacy-policy","Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-toolkit\u002Fskills\u002Fprivacy-policy\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M749JRFCNDADS61HFWMBHJJD","grammar-check","Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-toolkit\u002Fskills\u002Fgrammar-check\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M749JMXFX9KSXV4JP6J1K7QX","draft-nda","Draft a detailed Non-Disclosure Agreement between two parties covering information types, jurisdiction, and clauses needing legal review. Use when creating confidentiality agreements or preparing an NDA for a partnership.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-toolkit\u002Fskills\u002Fdraft-nda\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M749JGY34DGZ9BGFS2YCET6N","value-proposition","Design a detailed value proposition using a 6-part JTBD template — Who, Why, What before, How, What after, Alternatives. Use when creating a value proposition, analyzing customer value delivery, or articulating why customers should choose your product.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-product-strategy\u002Fskills\u002Fvalue-proposition\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M749JE27D1APC1PWWPFMF2GN","swot-analysis","Perform a detailed SWOT analysis — strengths, weaknesses, opportunities, and threats with actionable recommendations. Use when doing strategic assessment, competitive analysis, or evaluating a product or business position.","https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills\u002Fblob\u002Fmain\u002Fpm-product-strategy\u002Fskills\u002Fswot-analysis\u002FSKILL.md",[],[]]