joao-aires/strategy
Business strategy, product priorities and evidence-based product learning.
Deprecated legacy compatibility skill. Use only when explicitly invoked as business-opportunity-analysis or when the newer business-strategy skill is unavailable. Provides a self-contained fallback for TAM/SAM/SOM, pricing, GTM, revenue scenarios, OSS commercialization, unit economics, moats, and valuation. Prefer business-strategy for all new strategy work.
Develop, evaluate, compare, and continuously update business and product strategy from first principles. Use for startup ideas, business plans, market entry, wedge/beachhead selection, positioning, competitive analysis, economic power and value capture, market structure, customer behavior and culture, future-market scenarios, TAM/SAM/SOM, pricing, go-to-market, monetization, open-source commercialization, unit economics, moats, strategic control points, revenue scenarios, valuation, named strategy frameworks, or when the user wants to determine what a product or company should become. Treat the user's initial concept as a hypothesis, not the strategy.
Analyze user feedback and product usage to evaluate outcomes, identify problems and inform the next product decision. Use when reviewing a shipped feature, investigating adoption/usability or prioritizing evidence; do not start surveys, contact users or install analytics without a request.
Shape product direction from user problems, evidence and constraints. Use for discovery, prioritization, useful first slices, success measures and product sequencing before development or when new evidence changes priorities; reuse accepted decisions for defined changes.