ai-product-strategy-mapping
A framework to assess and integrate AI into your product strategy by mapping core customer problems to AI capabilities. Use this when your industry is facing a major technology shift, when prioritizing an AI roadmap, or when deciding between augmenting existing features vs. building new AI-first solutions.
Best use case
ai-product-strategy-mapping is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
A framework to assess and integrate AI into your product strategy by mapping core customer problems to AI capabilities. Use this when your industry is facing a major technology shift, when prioritizing an AI roadmap, or when deciding between augmenting existing features vs. building new AI-first solutions.
Teams using ai-product-strategy-mapping should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ai-product-strategy-mapping/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ai-product-strategy-mapping Compares
| Feature / Agent | ai-product-strategy-mapping | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
A framework to assess and integrate AI into your product strategy by mapping core customer problems to AI capabilities. Use this when your industry is facing a major technology shift, when prioritizing an AI roadmap, or when deciding between augmenting existing features vs. building new AI-first solutions.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
AI Agent for Product Research
Browse AI agent skills for product research, competitive analysis, customer discovery, and structured product decision support.
SKILL.md Source
# AI Product Strategy Mapping The "Meteor Framework" is a method for radically rethinking your product in the face of the AI shift. Rather than treating AI as a "bolt-on" feature, this framework forces you to evaluate whether your core value proposition is in the path of the "AI meteor" and determine if your product should be augmented or entirely replaced by AI-driven workflows. ## The Strategy Workflow ### 1. Define the Core Premise Before looking at the technology, return to first principles. Strip away your current UI and features. * Identify the core problem your product solves. * Define why people use it and what specific value they derive. * Ask: "What is the job the customer is hiring us to do?" ### 2. Map AI Capabilities to the Problem Evaluate your core premise against the specific technical strengths of Large Language Models (LLMs). Determine if AI can perform the following tasks better than your current manual or rule-based workflows: * **Synthesis:** Summarizing text, scanning images, or parsing data. * **Generation:** Writing text, code, or creating multimedia. * **Reasoning:** Answering complex queries or making deductions based on data. * **Action:** Taking real-world steps (e.g., "Change my flight," "Refund this customer"). ### 3. Determine the Integration Model Decide how the AI will interact with your existing product structure. * **Replacement:** The AI does the job entirely (e.g., an AI bot answering a support ticket instead of a human). * **Augmentation:** The AI acts as a "copilot" or assistant to the user (e.g., suggesting a reply for a support agent to edit). * **Vertical Specialization:** Determine if you need a specialized LLM for your specific industry data or if building on top of general models (OpenAI, Anthropic) is sufficient. ### 4. Implement via Generalist Teams Avoid creating a siloed "AI Team." Instead: * Embed machine learning experts into existing product squads. * Train generalist PMs and Designers to understand AI capabilities. * Focus on the user experience of AI interjections (e.g., "How and when should the assistant suggest an answer?"). ## Examples **Example 1: Customer Support (Intercom's "Fin")** * **Core Premise:** Customers need fast, accurate answers to support questions. * **AI Mapping:** LLMs can scan a knowledge base and reason through a solution. * **Application:** Transition from "Conversational Support" (human-to-human) to "AI-First Support" where the bot is the first line of defense. * **Output:** An AI chatbot that resolves 50-70% of inbound queries without human intervention. **Example 2: Data Reporting & Visualization** * **Core Premise:** Users need to understand their business performance data to make decisions. * **AI Mapping:** LLMs can query databases and summarize trends using natural language. * **Application:** Move away from complex dashboard-building UIs (Tableau-style) to a "Single Box" interface. * **Output:** A natural language interface where a user asks, "Who was our top salesman in January?" and receives an immediate answer instead of a chart. ## Common Pitfalls to Avoid * **The "Bolt-On" Mistake:** Adding a "summarize" button to an old workflow rather than rethinking if the workflow is still necessary. AI should be foundational, not an accessory. * **The Sunk Cost Trap:** Protecting old "Table Stakes" features (like complex manual reporting) that AI has rendered obsolete. If AI can do it better, be willing to "bet the farm" on the new version. * **Waiting for Certainty:** Treating AI like a hype cycle (e.g., Crypto/Web3). AI is a "before/after" technology shift; waiting for the market to settle will leave you behind. * **Over-specializing the Team:** Hiring only ML specialists and keeping them separate from the product. This prevents the "product sense" from being applied to the AI's capabilities. * **Ignoring the "Story":** Building great AI tech but failing to explain *why* it’s better for the customer. Ensure your "Product-Market-Story Fit" accounts for the AI’s value.
Related Skills
android-workflow-production
Generate GitHub Actions workflows for production deployment with staged rollout
android-product-shaping
This skill is used to turn Android app ideas into small, well-bounded product slices with clear value, ready for UX and implementation.
amazon-product-search-recommender
When the user wants to search for specific products on Amazon within budget constraints and generate structured recommendations. This skill navigates to Amazon.com, performs targeted searches using specific criteria (price range, material, color), browses search results, extracts product details (title, price, store/brand, URL), and compiles recommendations into a structured JSON format. Triggers include requests for product recommendations, shopping assistance, budget-constrained searches, or when users need to find specific items on Amazon with detailed specifications.
ai-native-product-refounding
A framework for transitioning from incremental SaaS development to an AI-native product strategy. Use this skill when you need to "refound" an existing product for the AI era, accelerate shipping velocity for AI features, or upskill a product team to be more hands-on with LLM primitives.
agile-product-owner
Agile product ownership toolkit for Senior Product Owner including INVEST-compliant user story generation, sprint planning, backlog management, and velocity tracking. Use for story writing, sprint planning, stakeholder communication, and agile ceremonies.
agent-product-manager
Expert product manager specializing in product strategy, user-centric development, and business outcomes. Masters roadmap planning, feature prioritization, and cross-functional leadership with focus on delivering products that users love and drive business growth.
adhd-productivity
ADHD-optimized productivity techniques and interventions. Invoke when user shows signs of task abandonment, context switching, or needs focus assistance.
argument-mapping
Reconstruct, visualize, and analyze argument structure. Use for: argument reconstruction, premise identification, inference evaluation, finding hidden assumptions, visualizing debates, Toulmin model analysis. Triggers: 'argument structure', 'premises', 'conclusion', 'inference', 'reconstruct', 'map the argument', 'Toulmin', 'argument diagram', 'validity', 'soundness', 'implicit premise', 'hidden assumption', 'logical structure'.
apple-productivity
Access macOS productivity apps (Calendar, Contacts, Mail, Messages, Reminders, Voice Memos). Use when user asks about calendar events, contacts, emails, iMessages, reminders, or voice transcription.
frontend-react-testing-strategy
Standardized guidelines and patterns for Frontend React Testing Strategy.
production-dockerfile
Generate production-ready Dockerfiles with multi-stage builds, security best practices, and optimization. Use when containerizing Python applications for production deployment.
pricing-strategy
Design pricing, packaging, and monetization strategies based on value, customer willingness to pay, and growth objectives.