Update to Consultor

{
  "name": "customer-research",
  "description": "Prepare customer interviews and synthesize interviews, feedback, reviews, support notes, sales calls, and testimonials into jobs, pains, gains, triggers, objections, quotes, patterns, evidence, and hypotheses.",
  "included_files": [],
  "skill_md_contents": "---\nname: customer-research\ndescription: Prepare customer interviews and synthesize interviews, feedback, reviews, support notes, sales calls, and testimonials into jobs, pains, gains, triggers, objections, quotes, patterns, evidence, and hypotheses.\ncompatibility: Requires Python 3.11+ only when using the optional bundled extraction helper.\n---\n\n# Customer Research\n\nTurn customer voice into useful consulting evidence.\n\nAsk one question at a time when the research scope is unclear. Do not recommend unless explicitly asked.\n\n## What To Challenge\n\n- Compliments treated as demand.\n- Opinions treated as behavior.\n- Future promises treated as evidence.\n- Founder interpretation presented as customer language.\n- One loud customer treated as a segment.\n- Survey answers used where past behavior or purchase behavior is needed.\n- Personas invented without quotes, examples, triggers, or situations.\n- \"People want this\" without who, when, why now, and what they do instead.\n\n## Evidence Hierarchy\n\nPrefer stronger evidence:\n\n1. Purchase or renewal behavior.\n2. Recent past behavior.\n3. Concrete attempts to solve the problem.\n4. Repeated objections in sales/support.\n5. Specific quotes tied to a situation.\n6. Stated preference or opinion.\n7. Compliments and enthusiasm.\n\nLabel each insight:\n\n- Verified: grounded in a source, transcript, call note, review, support ticket, or behavior.\n- Assumption: plausible interpretation of available material.\n- Hypothesis: pattern that needs more research or validation.\n\n## Interview Discipline\n\nWhen preparing interviews:\n\n- Ask about recent past behavior, not imagined futures.\n- Ask for concrete examples.\n- Ask what happened before, during, and after the problem.\n- Ask what they tried instead.\n- Ask what triggered action.\n- Ask what made them hesitate.\n- Avoid pitching during discovery.\n\n## Extraction Script\n\nWhen the user provides a transcript, notes, reviews, support messages, or call text as a local file, use the extraction helper before synthesizing:\n\n```bash\npython3 ../../scripts/consultor_customer_extract.py <input-file>\n```\n\nResolve the script path relative to this `SKILL.md` file before running it.\n\nUse `--stdout` when the user wants to see the extraction in chat.\n\n## What To Extract\n\nFrom interviews, feedback, reviews, notes, or transcripts, extract:\n\n- Segment or situation.\n- Job to be done.\n- Pain.\n- Desired gain.\n- Trigger.\n- Current alternative.\n- Buying criteria.\n- Objections.\n- Exact customer quotes.\n- Evidence strength.\n- Patterns across sources.\n- Implications for value proposition, positioning, pricing, sales, or experiments.\n\n## Handoff Rules\n\nUse related Consultor skills when the branch shifts:\n\n- Use `value-proposition` when customer research clarifies job, pain, gain, promise, mechanism, or proof.\n- Use `positioning` when research changes category, alternative, differentiation, or reason to believe.\n- Use `sales-objections` when research surfaces objections, trust gaps, or risk reversal needs.\n- Use `experiment-plan` when an insight needs validation.\n- Use `pricing-strategy` when willingness to pay, budget, price objections, or value metric appear.\n\n## Live Documents\n\nUse or create these documents only when there is real content to record:\n\n- `consultor/research/customer-research.md`\n- `consultor/research/interview-guide.md`\n- `consultor/strategy/value-proposition.md`\n- `consultor/strategy/positioning.md`\n- `consultor/sales/objections.md`\n- `consultor/experiments/experiments.md`\n- `consultor/assumptions.md`\n- `consultor/risks.md`\n\nUse the shared [`customer-research.md`](../../templates/customer-research.md) or [`interview-guide.md`](../../templates/interview-guide.md) template when creating new research documents.\n\n## Output\n\nPrefer:\n\n- Patterns, not anecdotes.\n- Quotes with context.\n- Evidence labels.\n- Implications for decisions.\n- Hypotheses and next research questions.\n\n## Done Threshold\n\nPause when the target segment, research source, repeated job/pain/gain, current alternative, trigger, objection, quote evidence, and next validation step are clear.\n"
}