slurpyb/problem-solving

Create uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "eliminate-reduce-raise-create", or "uncontested market". Also trigger when comparing pricing strategies, exploring new market categories, finding underserved customer segments, or asking how to stop competing on price. Covers the Four Actions Framework, buyer utility map, and value-cost trade-offs. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.

Use this skill whenever the user asks for brainstorming, ideation, concept expansion, service improvement ideas, strategy options, workshop structure, or says thinking is stuck and needs more perspectives. Select and apply one or more brainstorming frameworks based on the user's goal, solo vs group setting, divergence vs convergence need, and business vs creative context. Use it even if the user does not name a framework.

Use this skill whenever the user asks to create, structure, review, or refine a business plan, new business proposal, growth strategy, GTM outline, or venture hypothesis. Build a rational, persuasive business plan with reader-specific framing and bottom-up numerical planning. Distinguish researched facts from benchmarks and estimates, use frameworks only as supporting tools, and forecast outcomes from causal drivers instead of reverse-engineering a desired result. Use it even when the user only says "事業計画", "戦略を考えたい", "新規事業を整理したい", or asks for AI agent / SaaS business planning without naming any framework.

Convene a four-voice council for ambiguous decisions, tradeoffs, and go/no-go calls. Use when multiple valid paths exist and you need structured disagreement before choosing.

Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs. mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", or "pragmatist buyers". Also trigger when a startup has early traction but struggles to grow beyond initial users, or when planning go-to-market for technical products. Covers D-Day analogy, bowling-pin strategy, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.

Solve user questions with defensible Fermi estimates using explicit assumptions, source-backed inputs, uncertainty ranges, and sensitivity analysis. Use when exact data is unavailable or too slow to collect but the user still needs a quantitative answer for counts, market size, demand, costs, revenue, capacity, timing, or operational scale. Prefer quick primary-source lookup when it exists; use Fermi estimation as fallback or cross-check when direct measurement is unavailable, stale, fragmented, or too slow. Autonomously gather accessible evidence, prefer current primary sources, and drive to a conclusion without asking for approval.

Explore complex, multi-faceted topics requiring deep understanding through a three-round iterative strategy with parallel subagents.

Apply meta-principles of software craftsmanship: DRY, orthogonality, tracer bullets, and design by contract. Use when the user mentions "best practices", "pragmatic approach", "broken windows", "tracer bullet", "software craftsmanship", "technical debt prevention", "prototype vs tracer bullet", or "code ownership". Also trigger when evaluating build-vs-buy decisions, designing estimation approaches, or choosing between reversible and irreversible architectural decisions. Covers estimation, domain languages, and reversibility. For code-level quality, see clean-code. For refactoring techniques, see refactoring-patterns.

Apply systematic problem-solving techniques for marketing challenges including campaign complexity (simplification cascades), creative blocks (collision-zone thinking), recurring campaign patterns (meta-pattern recognition), assumption constraints (inversion exercise), audience scale uncertainty (scale game), and dispatch when stuck. Techniques derived from proven problem-solving frameworks adapted for marketing execution.

Propose concrete, high-leverage product/UX improvements to increase a software project's appeal and retention. Use when asked to generate product improvement proposals, UX ideas, onboarding/doc improvements, packaging/pricing positioning suggestions grounded in repo evidence, and prioritized MVP plans (ideation only; no implementation).

Multi-agent adversarial verification with convergence loop. Two independent review agents must both pass before output ships.

Use when challenging ideas, plans, decisions, or proposals. Invoke to play devil's advocate, run a pre-mortem, red team, stress test assumptions, audit evidence quality, or find blind spots before committing. Do NOT use for building plans, making decisions, or generating solutions — this skill only challenges and critiques.

Analytical and creative thinking frameworks. First principles decomposition, iterative depth analysis, council debate with multiple perspectives, red team stress testing, brainstorming, world and threat models, and scientific method. USE WHEN first principles, decompose, challenge assumptions, iterative depth, be creative, brainstorm, council, debate, red team, stress test, devil's advocate, threat model, world model, think about, experiment, hypothesis, deep exploration, figure out, optimize, improve, weigh options, creative solutions, critique, counterarguments.