Update to Consultor

{
  "description": "Main Consultor workshop controller. Use when the user wants strategic consulting, a business idea interrogated, a workshop flow, or help choosing which Consultor skill should handle the next branch.",
  "included_files": [],
  "name": "consultor-workshop",
  "skill_md_contents": "---\nname: consultor-workshop\ndescription: Main Consultor workshop controller. Use when the user wants strategic consulting, a business idea interrogated, a workshop flow, or help choosing which Consultor skill should handle the next branch.\ncompatibility: Requires Python 3.11+ only when using the optional bundled workspace and audit helpers.\n---\n\n# Consultor Workshop\n\nRun a consulting workshop that turns fuzzy business thinking into precise decisions, hypotheses, evidence, risks, and next actions.\n\nAsk one question at a time. Do not ask clusters.\n\nDo not recommend by default. If the user explicitly asks for a recommendation, give it and then return to one question.\n\n## Workshop Flow\n\nUse this sequence as a map, not a rigid script:\n\n1. Clarify the object of consultation: business, product, offer, campaign, market, channel, sales motion, or validation plan.\n2. Identify the highest-risk unknown.\n3. Route to the relevant Consultor skill:\n   - `marketing-grill` for marketing strategy, audiences, messaging, and funnels.\n   - `resume-consultor` for resuming existing project state before asking new questions.\n   - `business-model` for revenue logic, offers, cliductes, margins, constraints, and business viability.\n   - `value-proposition` for jobs, pains, gains, promise, mechanism, proof, and scope.\n   - `customer-research` for interviews, feedback, reviews, quotes, triggers, and objections.\n   - `competitive-research` for source-backed competitors, alternatives, substitutes, pricing, and claims.\n   - `pricing-strategy` for pricing basis, packaging, tiers, discounts, margin, and price objections.\n   - `offer-design` for concrete offer structure, deliverables, boundaries, onboarding, and risk reversal.\n   - `positioning` for category, alternatives, differentiation, proof, and market perception.\n   - `go-to-market` for channels, launch sequence, distribution, acquisition, activation, retention, and growth motion.\n   - `experiment-plan` for hypotheses, tests, evidence, metrics, and decision criteria.\n   - `sales-objections` for objections, buyer risk, sales narrative, pricing friction, and proof.\n   - `landing-copy` for landing page copy structure after strategy is clear.\n   - `dafo-builder` for evidence-backed SWOT/DAFO artifacts.\n   - `canvas-builder` for Business Model Canvas / Lean Canvas artifacts.\n   - `workshop-facilitator` for explicit workshop phase control.\n   - `strategy-synthesis` for consolidating decisions, risks, open questions, and action plans.\n4. Update live documents as decisions crystallize.\n5. Stop when the current branch has enough clarity to act or validate.\n\n## Audit Script\n\nWhen starting in a project that lacks a `consultor/` workspace, initialize it before creating live documents:\n\n```bash\npython3 ../../scripts/consultor_init.py <project-root> --base-files --resume-note\n```\n\nWhen resuming a project or when the user asks for a score, risk map, unanswered questions, contradictions, or synthesis, run the local audit script before asking more questions:\n\n```bash\npython3 ../../scripts/consultor_audit.py <project-root> --mode workshop\n```\n\nResolve script paths relative to this `SKILL.md` file before running them.\n\nThe report summarizes confirmed decisions, active hypotheses, evidence, risks, open questions, experiments, immediate actions, potential contradictions, and an assumption-to-evidence-to-risk-to-experiment map.\n\n## Live Documents\n\nBefore creating documents, inspect the project for existing strategy, marketing, sales, or consulting material. Respect the structure if it is clear.\n\nIf none exists, use:\n\n```text\nconsultor/\n|-- context.md\n|-- assumptions.md\n|-- decisions.md\n|-- risks.md\n|-- strategy/\n|-- marketing/\n|-- research/\n|-- sales/\n|-- experiments/\n`-- reports/\n```\n\nCreate documents lazily. Never create empty files or empty sections.\n\nGenerated documents must be written in the user's or project's language.\n\n## Evidence Discipline\n\nLabel claims as:\n\n- Verified: checked against a source, artifact, analytics, customer evidence, or direct inspection.\n- Assumption: plausible but not verified.\n- Hypothesis: requires validation.\n\nWhen current market facts, competitors, pricing, platform behavior, laws, or benchmarks matter, verify them through official docs, primary sources, direct inspection, or web research.\n\n## Done Threshold\n\nA branch can pause when these are clear enough:\n\n- Who this is for.\n- What job, pain, or desire matters.\n- What the alternative is.\n- Why this should win.\n- What the offer or action is.\n- What evidence supports it.\n- What the main risk is.\n- What the next validation step is.\n"
}