gap-running-destruction
openbooklet.com/s/gap-running-destructionopenbooklet.com/s/gap-running-destruction@1.0.0GET /api/v1/skills/gap-running-destructionAdversarially attacks the current register state through pre-mortem, red-team response, constraint inversion, evidence concentration analysis, and kill signal audit. Use when a gap pass requires adversarial validation of hypotheses and proposals.
Computes desired-current state deltas, quantifies component scores, and produces a ranked gap ledger. Use when evaluating hypothesis register state to determine where the largest gaps exist between desired and current conditions.
Applies the 10 decision rules, reclassifies confidence and support states, sets readiness gates, and generates execution queue entries and governor escalations. Use when gap computation and destruction are complete and decisions must be enforced.
Maps competitive landscape, identifies positioning gaps, and assesses competitor response capability for red-team input. Use when researching competition during BUILD phase 1 or feeding destruction phase.
Calculates unit economics (LTV, CAC, payback, margins) with range-based estimates, cost structure, and scenario analysis. Use when constructing unit economics hypothesis during BUILD phase 2.
Selects GTM acquisition channels, estimates per-channel CAC, designs channel mix with investment allocation, and sequences channels by phase. Constrained by ACV-channel viability from pricing and growth architecture from solutions. Produces channel strategy for unit economics hypothesis.
Designs the complete GTM plan for the hypothesis register. Sequences channels by phase with gate criteria, builds messaging framework from value proposition, sets target KPIs per phase, derives operational constraints from all hypotheses, and defines success/kill criteria. Use when constructing register section 7 (GTM Plan) during BUILD.
Develops pricing hypothesis using value-based methodology, tier architecture, and mode-specific constraints. Use when constructing unit economics during BUILD phase 2.
Designs solution architecture, selects growth model, assembles positioning, maps features to problems, and defines MVP scope. Use when constructing Solution Design section during BUILD phase 2.
Processes governor-provided expert sources into structured, tier-labeled insights that feed the hypothesis register as evidence. Use when governor provides a book, article, video, or podcast for processing.
Scores problem candidates using four-property framework (frequency, severity, breadth, alternatives' inadequacy) with compression-model elimination. Use when constructing problem hypothesis during BUILD phase 2.
Generates strategic customer segment definitions with observable filters, pain scoring, and compression-model elimination. Use when constructing segment hypothesis during BUILD phase 2.
Calculates market opportunity with TAM/SAM/SOM using dual methods and timing analysis. Use when researching market size during BUILD phase 1 or refreshing market data during CHALLENGE.
Auto-indexed from BellaBe/strategy-os
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.