product-strategist
Expert product strategist for vision, strategy, and market positioning. Use when defining product vision, assessing product-market fit, sizing market opportunities (TAM/SAM/SOM), competitive positioning, or choosing between build/buy/partner. Covers business model design, monetization strategy, platform decisions, and strategic roadmap planning.
What this skill does
# Product Strategist
Strategic product leadership for companies navigating vision, market fit, and competitive positioning — from early ideation to scale.
## Philosophy
Great product strategy isn't about having all the answers. It's about **asking the right questions** and making **reversible decisions** quickly while being thoughtful about **irreversible ones**.
The best product strategies:
1. **Start with the customer problem** — Not with your solution
2. **Create optionality** — Platform thinking enables multiple futures
3. **Make trade-offs explicit** — Strategy is choosing what NOT to do
4. **Compound over time** — Each decision builds on the last
## How This Skill Works
When invoked, apply the guidelines in `rules/` organized by:
- `vision-*` — Product vision, mission, and north star metrics
- `market-*` — Product-market fit, market sizing, opportunity assessment
- `competitive-*` — Competitive positioning, moats, differentiation
- `strategy-*` — Strategic frameworks, decision making, prioritization
- `business-*` — Business models, monetization, pricing strategy
- `build-*` — Build vs buy vs partner, platform decisions
## Core Frameworks
### Product Strategy Stack
```
┌─────────────────────────┐
│ VISION │ ← Where are we going? (3-10 years)
│ "The why behind why" │
├─────────────────────────┤
│ STRATEGY │ ← How will we win? (1-3 years)
│ "The path to vision" │
├─────────────────────────┤
│ ROADMAP │ ← What are we building? (Quarters)
│ "Strategy in motion" │
├─────────────────────────┤
│ EXECUTION │ ← How are we building? (Sprints)
│ "Roadmap in action" │
└─────────────────────────┘
```
### Strategic Decision Types
| Decision Type | Reversibility | Time to Decide | Example |
|---------------|---------------|----------------|---------|
| **Type 1** | Irreversible | Take your time | Business model, platform choice |
| **Type 2** | Reversible | Decide quickly | Feature prioritization, pricing tiers |
### Product-Market Fit Spectrum
```
Level 0: Problem Fit → You've found a real problem worth solving
Level 1: Solution Fit → Your solution addresses the problem
Level 2: Product-Market Fit → Customers pull the product from you
Level 3: Scale Fit → Repeatable growth engine working
Level 4: Moat Fit → Defensible competitive advantage established
```
### Market Opportunity Framework
```
┌─────────────────────────────────────────────────────────────┐
│ TAM │
│ Total Addressable Market │
│ "Everyone who could theoretically buy" │
│ ┌───────────────────────────────────────────┐ │
│ │ SAM │ │
│ │ Serviceable Addressable Market │ │
│ │ "Those you could reach and serve" │ │
│ │ ┌─────────────────────────────┐ │ │
│ │ │ SOM │ │ │
│ │ │ Serviceable Obtainable │ │ │
│ │ │ "Realistic near-term" │ │ │
│ │ └─────────────────────────────┘ │ │
│ └───────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────┘
```
### Competitive Moat Types
| Moat Type | Description | Examples |
|-----------|-------------|----------|
| **Network Effects** | Product improves as more users join | Slack, LinkedIn |
| **Switching Costs** | Painful to leave | Salesforce, Workday |
| **Data Advantages** | Proprietary data improves product | Google, Waze |
| **Scale Economies** | Cost advantages at scale | AWS, Stripe |
| **Brand** | Trust and recognition | Apple, Notion |
| **Regulatory** | Compliance barriers | Healthcare, Finance |
### Business Model Canvas (Simplified)
```
┌──────────────────┬──────────────────┬──────────────────┐
│ VALUE PROP │ CHANNELS │ CUSTOMER │
│ What unique │ How you │ SEGMENTS │
│ value? │ reach them │ Who pays? │
├──────────────────┼──────────────────┼──────────────────┤
│ KEY RESOURCES │ KEY │ REVENUE │
│ What you need │ ACTIVITIES │ STREAMS │
│ to deliver │ What you do │ How you make │
│ │ │ money │
├──────────────────┴──────────────────┴──────────────────┤
│ COST STRUCTURE │
│ What it costs to operate │
└────────────────────────────────────────────────────────┘
```
## Platform Overview
| Strategic Question | Framework to Use | When to Apply |
|--------------------|------------------|---------------|
| **Where to play?** | Market sizing, opportunity assessment | Early stage, pivots |
| **How to win?** | Competitive positioning, moat analysis | All stages |
| **What to build?** | Build/buy/partner, platform decisions | Growth stage |
| **How to price?** | Value-based pricing, monetization | Pre-launch, repricing |
| **When to expand?** | Adjacent market analysis | Scale stage |
## Anti-Patterns
- **Vision without strategy** — Inspiring destination, no map to get there
- **Strategy without trade-offs** — If everything is a priority, nothing is
- **Copying competitors** — Being a fast follower without differentiation
- **TAM theater** — Using unrealistic market sizes to impress investors
- **Feature parity obsession** — Chasing competitors instead of customers
- **Premature scaling** — Scaling before product-market fit
- **Analysis paralysis** — Researching forever, deciding never
- **Sunk cost fallacy** — Continuing failed bets because of past investment
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.