recommendation-canvas
Evaluate an AI product idea across outcomes, hypotheses, risks, and positioning
Install / Use
npx skills add deanpeters/Product-Manager-Skills --skill recommendation-canvasInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
DesignSupported Platforms
Tags
Our assessment of recommendation-canvas
recommendation-canvas scores 93/100 on our quality scale, 43rd of 260 Design skills we index (top 17%).
Its SKILL.md is 15 KB long, well organised into 59 sections with 14 code examples: a thorough specification that gives an agent plenty to work with.
With 7,063 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 3 months ago, so recommendation-canvas is actively maintained.
- Our last check on 2026-10-26 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-27. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
recommendation-canvas compared with similar skills
All 4 of these similar skills score higher than recommendation-canvas; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| recommendation-canvas (this skill)by deanpeters | 93 | 7.1k | 3mo ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install recommendation-canvas?
- Run
npx skills add deanpeters/Product-Manager-Skills --skill recommendation-canvas. The install tabs above show the steps for each supported agent. - Which AI agents does recommendation-canvas work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is recommendation-canvas safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is recommendation-canvas still maintained?
- The repository was last updated about 3 months ago, so recommendation-canvas is actively maintained.
Skill content
View source on GitHubname: recommendation-canvas argument-hint: "[AI product idea]" description: Evaluate an AI product idea across outcomes, hypotheses, risks, and positioning. Use when deciding whether an AI solution deserves investment or recommendation. intent: >- Evaluate and propose AI product solutions using a structured canvas that assesses business outcomes, customer outcomes, problem framing, solution hypotheses, positioning, risks, and value justification. Use this to build a comprehensive, defensible recommendation for stakeholders and decision-makers—especially when proposing AI-powered features or products that carry higher uncertainty and risk. type: component theme: validation-experiments best_for:
- "Deciding whether an AI product idea deserves real investment"
- "Surfacing the risks and hypotheses behind an AI feature request"
- "Comparing AI solution options on outcomes rather than novelty" scenarios:
- "Leadership wants an AI feature and I need to evaluate whether it's worth building"
- "I have three AI solution options and need to compare them on outcomes and risk" estimated_time: "30-45 min"
Purpose
Evaluate and propose AI product solutions using a structured canvas that assesses business outcomes, customer outcomes, problem framing, solution hypotheses, positioning, risks, and value justification. Use this to build a comprehensive, defensible recommendation for stakeholders and decision-makers—especially when proposing AI-powered features or products that carry higher uncertainty and risk.
This is not a feature spec—it's a strategic proposal that articulates why this AI solution is worth building, what assumptions need validating, and how you'll measure success.
Input
Works best with: The AI product or feature idea being evaluated. Also useful: Target customer, expected business outcome, known risks, and who the recommendation must convince.
Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.
Arriving empty-handed? That works too. The skill asks for the idea and the decision-maker, then works through the canvas boxes.
Example invocation: Recommendation canvas: AI-suggested reorder quantities for warehouse managers — VP Ops wants a go/no-go next month.
Key Concepts
The Recommendation Canvas Framework
Created for Dean Peters' Productside "AI Innovation for Product Managers" class, the canvas synthesizes multiple PM frameworks into one strategic view:
Core Components:
- Business Outcome: What's in it for the business?
- Product Outcome: What's in it for the customer?
- Problem Statement: Persona-centric problem framing
- Solution Hypothesis: If/then hypothesis with experiments
- Positioning Statement: Value prop and differentiation
- Assumptions & Unknowns: What could invalidate this?
- PESTEL Risks: Political, Economic, Social, Technological, Environmental, Legal
- Value Justification: Why this is worth doing
- Success Metrics: SMART metrics to measure impact
- What's Next: Strategic next steps
Why This Works
- Outcome-driven: Forces clarity on business AND customer value
- Hypothesis-centric: Treats solution as a bet to validate, not a commitment
- Risk-explicit: Makes assumptions and risks visible upfront
- Executive-friendly: Comprehensive but structured for C-level review
- AI-appropriate: Especially useful for AI features with high uncertainty
Anti-Patterns (What This Is NOT)
- Not a PRD: This is strategic framing, not detailed requirements
- Not a business case (yet): It informs the business case but needs validation first
- Not a feature list: Focus on outcomes, not capabilities
When to Use This
- Proposing a new AI-powered product or feature
- Pitching to execs or securing budget/sponsorship
- Evaluating whether an AI solution is worth pursuing
- Aligning cross-functional stakeholders (product, engineering, data science, business)
- After completing initial discovery (you need context to fill this out)
When NOT to Use This
- For trivial features (don't over-engineer small tweaks)
- Before any discovery work (you need user research and problem validation first)
- As a replacement for experimentation (canvas informs experiments, not vice versa)
Application
Use template.md for the full fill-in structure.
Step 1: Gather Context
Before filling out the canvas, ensure you have:
- Problem understanding: User research, pain points (reference
skills/problem-statement/SKILL.md) - Persona clarity: Who experiences the problem? (reference
skills/proto-persona/SKILL.md) - Market context: Competitive landscape, category positioning
- Business constraints: Budget, timelines, strategic priorities
If missing context: Run discovery work first. This canvas synthesizes insights—it doesn't create them.
Step 2: Define Outcomes
Business Outcome
What's in it for the business? Use this format:
- [Direction] [Metric] [Outcome] [Context] [Acceptance Criteria]
## Business Outcome
- [e.g., "Reduce by 25% the churn of existing customers using our existing product"]
Example:
- "Increase by 15% the monthly recurring revenue from enterprise customers within 12 months"
Quality checks:
- Measurable: Can you track this metric?
- Time-bound: Within what timeframe?
- Ambitious but realistic: Not "10x revenue in 1 month"
Product Outcome
What's in it for the customer? Use this format:
- [Direction] [Metric] [Outcome] [Context from persona's POV] [Acceptance Criteria]
## Product Outcome
- [e.g., "Increase the speed of finding patients when I know the inclusion and exclusion criteria"]
Example:
- "Reduce by 60% the time spent manually processing invoices for small business owners"
Quality checks:
- Customer-centric: Written from user perspective ("I," not "we")
- Outcome, not feature: "Reduce time spent" not "Use AI automation"
Step 3: Frame the Problem
Use the problem framing narrative from skills/problem-statement/SKILL.md:
## The Problem Statement
### Problem Statement Narrative
- [Persona description: 2-3 sentences telling the persona's story from their POV]
- [Example: "Sarah is a freelance designer managing 10 clients. She spends 8 hours/month manually tracking invoices and chasing late payments. By the time she follows up, some clients have already moved to other designers, costing her revenue and damaging relationships."]
Quality checks:
- Empathetic: Does this sound like the user's voice?
- Specific: Not "users want better tools" but "Sarah spends 8 hours/month..."
- Validated: Based on real user research, not assumptions
Step 4: Define the Solution Hypothesis
Hypothesis Statement
Use the epic hypothesis format from skills/epic-hypothesis/SKILL.md:
## Solution Hypothesis
### Hypothesis Statement
**If we** [action or solution on behalf of target persona]
**for** [target persona]
**Then we will** [attain or achieve desirable outcome]
Example:
- "If we provide AI-powered invoice reminders that auto-send at optimal times for freelance designers, then we will reduce time spent on payment follow-ups by 70%"
Tiny Acts of Discovery
Define lightweight experiments to validate the hypothesis:
### Tiny Acts of Discovery
**We will test our assumption by:**
- [Experiment 1: Prototype AI reminder system and test with 5 freelancers]
- [Experiment 2: A/B test manual vs. AI-timed reminders for 20 users]
- [Experiment 3: Survey users on perceived value after 2 weeks]
Quality checks:
- Fast: Days/weeks, not months
- Cheap: Prototypes, concierge tests, not full builds
- Falsifiable: Could prove you wrong
Proof-of-Life
Define validation measures:
### Proof-of-Life
**We know our hypothesis is valid if within** [timeframe]
**we observe:**
- [Quantitative outcome: e.g., "80% of users send reminders via the AI system"]
- [Qualitative outcome: e.g., "8 out of 10 users report saving 5+ hours/month"]
Step 5: Define Positioning
Use the positioning statement format from skills/positioning-statement/SKILL.md:
## Positioning Statement
### Value Proposition
**For** [target customer/user persona]
**that need** [statement of underserved need]
[product name]
**is a** [product category]
**that** [statement of benefit, focusing on outcomes]
### Differentiation Statement
**Unlike** [primary competitor or competitive arena]
[product name]
**provides** [unique differentiation, focusing on outcomes]
Step 6: Document Assumptions & Unknowns
## Assumptions & Unknowns
- **[Assumption 1]** - [Description, e.g., "We assume users will trust AI-generated reminders"]
- **[Assumption 2]** - [Description, e.g., "We assume payment timing optimization increases response rates"]
- **[Unknown 1]** - [Description, e.g., "We don't know if users prefer email or SMS reminders"]
Quality checks:
- Explicit: Make hidden assumptions visible
- Testable: Each assumption can be validated via experiments
Step 7: Identify PESTEL Risks
Risks to Investigate (High Priority)
## Issues/Risks to Investigate
- **Political:** [e.g., "Regulatory changes to AI-generated communications"]
- **Economic:** [e.g., "Economic downturn reduces willingness to pay for premium features"]
- **Social:** [e.g., "Users may perceive AI reminders as impersonal or pushy"]
- **Technological:** [e.g., "AI model accuracy may degrade over time without retraining"]
- **Environmental:** [e.g., "Energy costs of AI processing"]
- **Legal:** [e.g., "GDPR compliance for storing customer email patterns"]
Risks to Monitor (Lower Priority)
## Issues/Risks to Monitor
- **Political:** [e.g., "Potential AI regulation in EU markets"]
- **Economic:** [e.g., "Exchange rate fluctuations affecting international customers"]
- **Social:** [e.g., "Changing norms around automated communication"]
- **Technological:** [e.g., "Emerging AI competitors with better models"]
- **Environmental:** [e.g., "Carbon footprint concerns from stakeholders"]
- **Legal:** [e.g., "Future data privacy laws"]
Step 8: Justify the Value
## Value Justification
### Is this Valuable?
- [Absolutely yes / Yes with caveats / No with suggested alternatives / Absolutely NO!]
### Solution Justification
<!-- Write these to convince C-level executives -->
We think this is a valuable idea. Here's why:
1. **[Justification 1]** - [Description, e.g., "Addresses the #1 pain point for our target segment"]
2. **[Justification 2]** - [Description, e.g., "Differentiates us from competitors who only offer manual reminders"]
3. **[Justification 3]** - [Description, e.g., "Low technical risk—leverages existing AI infrastructure"]
Step 9: Define Success Metrics
Use SMART metrics (Specific, Measurable, Attainable, Relevant, Time-Bound):
## Success Metrics
1. **[Metric 1]** - [e.g., "80% of active users adopt AI reminders within 3 months"]
2. **[Metric 2]** - [e.g., "Average time spent on payment follow-ups decreases by 50% within 6 months"]
3. **[Metric 3]** - [e.g., "Net Promoter Score for invoicing feature increases from 6 to 8 within 6 months"]
Step 10: Define Next Steps
## What's Next
1. **[Next step 1]** - [e.g., "Run 2-week prototype test with 10 beta users"]
2. **[Next step 2]** - [e.g., "Build lightweight AI model for reminder timing optimization"]
3. **[Next step 3]** - [e.g., "Conduct legal review of GDPR implications"]
4. **[Next step 4]** - [e.g., "Present findings to exec team for go/no-go decision"]
5. **[Next step 5
Truncated for display — read the full file on GitHub.
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
