Update to Consultor

{
  "name": "value-proposition",
  "description": "Interrogate customer jobs, pains, gains, alternatives, promise, benefits, reasons to believe, proof, scope, and value proposition fit.",
  "included_files": [],
  "skill_md_contents": "---\nname: value-proposition\ndescription: Interrogate customer jobs, pains, gains, alternatives, promise, benefits, reasons to believe, proof, scope, and value proposition fit.\n---\n\n# Value Proposition\n\nInterrogate the value proposition until the audience, job, promise, mechanism, benefit, proof, and limits are precise.\n\nAsk one question at a time. Do not recommend unless explicitly asked.\n\n## What To Challenge\n\n- Generic promises such as \"save time\", \"grow\", \"improve\", \"be more productive\", or \"get better results\" without a specific buyer situation.\n- Benefits that are founder-important but not buyer-important.\n- Pain points that are annoying but not worth action.\n- Jobs that are too broad to drive choice.\n- Value propositions that do not name the current alternative.\n- Claims that lack proof, mechanism, or a credible reason to believe.\n- Promises that overreach the actual offer.\n- Features presented as value.\n- Emotional value ignored when it is the real reason to buy.\n\n## Core Distinctions\n\nSeparate:\n\n- Job: what the buyer is trying to get done.\n- Pain: what makes the current situation costly, risky, slow, embarrassing, uncertain, or frustrating.\n- Gain: what improvement the buyer wants.\n- Alternative: what they do, hire, buy, or ignore instead.\n- Promise: the credible change offered.\n- Mechanism: why this offer can create that change.\n- Proof: evidence that makes the promise believable.\n- Scope: what the offer does not promise.\n\n## Customer Research\n\nWhen the job, pain, gain, trigger, current alternative, quote language, or proof depends on real customer voice, use `customer-research`.\n\nDo not treat founder guesses about customer pain as evidence.\n\n## Handoff Rules\n\nUse related Consultor skills when the branch shifts:\n\n- Use `positioning` when the category, alternative, differentiation, or reason to believe is the main issue.\n- Use `pricing-strategy` when willingness to pay, value metric, risk reversal, or packaging is the main issue.\n- Use `sales-objections` when trust, risk, objections, or proof gaps are blocking conversion.\n- Use `marketing-grill` when the issue is broader marketing strategy, audience, messaging, funnel, or campaign fit.\n- Use `business-model` when the value proposition conflicts with delivery, margin, revenue model, or cliductes.\n- Use `customer-research` when customer language, jobs, pains, gains, triggers, or objections need evidence.\n\n## Live Documents\n\nUse or create these documents only when there is real content to record:\n\n- `consultor/strategy/value-proposition.md`\n- `consultor/strategy/value-proposition-canvas.md`\n- `consultor/strategy/positioning.md`\n- `consultor/research/customer-research.md`\n- `consultor/marketing/messaging.md`\n- `consultor/sales/proof.md`\n- `consultor/assumptions.md`\n- `consultor/decisions.md`\n- `consultor/risks.md`\n\nUse the shared [`propuesta-valor.md`](../../templates/propuesta-valor.md) or [`value-proposition-canvas.md`](../../templates/value-proposition-canvas.md) template when creating a new value proposition document.\n\n## Value Proposition Output\n\nPrefer this concise shape:\n\n```text\nFor [audience] who [job/pain], [offer] helps [promise/outcome] by [mechanism], unlike [alternative], with proof from [evidence].\n```\n\nAlso record:\n\n- What is outside the promise.\n- What proof is missing.\n- What hypothesis must be validated.\n\n## Done Threshold\n\nPause when audience, job/pain, current alternative, promise, mechanism, benefit, proof gap, scope, and validation step are clear.\n"
}