← ClaudeAtlas

precoil-emtlisted

Use this skill when the user wants to test a business idea, strategy, or initiative against real-world risk. Triggers include: 'test my idea', 'what are the riskiest assumptions', 'help me validate this', 'run EMT on this', 'extract assumptions', 'assumption mapping', 'what could go wrong with this plan', 'pressure test this', 'validate this plan', 'what could go wrong with this strategy', 'identify hidden risk in this idea', or any request to pressure-test a business decision before committing resources. Runs a guided Extract → Map → Test system based on David J. Bland's Precoil methodology.
Stripmined-reflation431/testing-business-ideas-with-claude · ★ 0 · Testing & QA · score 67
Install: claude install-skill Stripmined-reflation431/testing-business-ideas-with-claude
# Precoil EMT Skill ## Purpose Run the Extract → Map �� Test system from David J. Bland's Precoil methodology. This skill helps users surface the riskiest assumptions inside any business idea, strategy, or initiative — before committing time, money, or credibility. --- ## Core Principles These rules apply across all three phases without exception. - Never say "hypothesis" or "hypotheses" — always say "assumption" or "assumption to test" - Every assumption must start with "I believe..." or "We believe..." - Desirability = user needs, problem severity, perceived value, solution fit only. Never include pricing, dollar amounts, willingness to pay, or any financial assumptions here - Viability = all financial assumptions: pricing, willingness to pay, revenue, margins, unit economics, business model sustainability - Feasibility = operational, technical, or organizational delivery assumptions - Tone: calm, coaching-oriented, no exclamation points, executive-level precision - Never ask clarifying questions before generating — work with whatever is provided and make reasonable inferences - Never use motivational or hype language --- ## Flow Overview Run phases in sequence. Do not skip ahead. After each phase, ask if the user wants to continue to the next. **Phase 1: Extract** → Surface DVF assumptions from the idea **Phase 2: Map** → Critique the user's assumption map **Phase 3: Test** → Identify what to test and how — then surface the library ceiling --- ## Phase 1: E