Claude Skills AI Suite For PM's

Idea: [Describe the product idea or feature in 2-3 sentences]

Context:
- Target user: [Who is this for?]
- Current solution: [How do users solve this today?]
- Business goal: [What outcome does this serve?]
- Team constraints: [Engineering capacity, timeline, tech stack]

Run a full Desirability / Feasibility / Viability validation.
Return: Verdict, confidence score (1-10), key risks, and recommended next step.

Market: [Describe the market or product category]

Data I have:
- Industry: [e.g., B2B SaaS for HR teams]
- Geography: [e.g., India, Southeast Asia]
- Known data points: [Any market reports, competitor revenue, user counts]

Constraints:
- Our ICP: [Define your target customer]
- Price point: [What you charge or plan to charge]

Build TAM/SAM/SOM using at least two methodologies.
Include conservative, base, and optimistic scenarios.
Return: Market size table + key assumptions + data sources to validate.

Industry: [Your product category or market]
Timeframe: [How far ahead do you need to forecast — 12, 18, or 24 months?]

Context:
- Our current product focus: [What you currently build]
- Known trends we're already tracking: [List 2-3]
- Biggest threat to our roadmap today: [What keeps you up at night]

Identify 5-7 emerging trends. For each:
- Signal strength (weak/moderate/strong)
- Time to mainstream
- Implication for our product
- Recommended bet or action

Product / Feature: [What you're launching]
Launch date: [Timeline]

Context:
- Who it's for: [ICP — role, company size, pain point]
- Core value prop: [One sentence: we help [WHO] do [WHAT] so that [OUTCOME]]
- Competitors: [2-3 alternatives users might choose instead]
- Biggest adoption risk: [What could stop users from trying it]

Build a full GTM strategy. Include:
1. Positioning statement
2. Top 3 ICPs with messaging per segment
3. Channel mix with rationale
4. 90-day launch plan
5. Success metrics with targets

Product: [What you're pricing]

Context:
- Our users: [Who they are, what they pay for today]
- Core value metric: [What we deliver — seats, outcomes, volume, time]
- Competitors: [List 3 with their pricing if known]
- Business goal: [Maximize revenue? Maximize conversion? Penetrate market?]

Run a pricing strategy analysis. Return:
1. Recommended pricing model (seat, usage, outcome-based, hybrid)
2. Tier structure (if applicable) with feature allocation
3. Price anchoring strategy
4. Key psychological principles applied
5. A/B test recommendation for validation

Our product: [Describe what you build]
Competitors to analyze: [List 2-4 by name]

For each competitor, I want to understand:
- How they position themselves (not just features)
- Who their ideal customer appears to be
- Where they are clearly strong
- Where they appear to have gaps or weaknesses
- What they're likely building next (based on signals)

Finish with:
- Top 3 strategic whitespace opportunities for us
- One positioning angle none of them own yet
- Recommended differentiation statement

[Paste interview transcript(s) here — can handle multiple at once]

Analyze these interviews and return:
1. Top 5 themes (ranked by frequency and intensity)
2. Key pain points with supporting quotes
3. Jobs to be done (what users are trying to accomplish)
4. Moments of delight (what's working)
5. Feature signals (explicit or implicit requests)
6. Recommended actions for the product team

Format as a structured brief I can share with stakeholders directly.

Source data: [Paste G2/Capterra reviews, survey responses, or interview highlights]

Our product: [What you build and who it's for]

Build 2-3 distinct buyer personas. For each include:
1. Role and seniority
2. Core goal (what success looks like for them)
3. Primary pain points (top 3)
4. How they currently solve the problem
5. What would make them choose us
6. Key objections to address
7. Best messaging angle for this persona

Format as a Notion-ready persona card.

Feature / Project: [Name]
One-line description: [What this does]

Context:
- Problem being solved: [For which user, doing what, with what pain]
- Success metrics: [How will we know this worked?]
- Constraints: [Technical, timeline, resource limits]
- Out of scope: [What this explicitly does NOT cover]
- Dependencies: [Other teams, systems, or features required]

Generate a complete PRD. Include:
1. Problem statement
2. User stories (structured as: As a [role], I want [feature] so that [outcome])
3. Functional requirements
4. Edge cases and error states
5. Acceptance criteria
6. Open questions to resolve with engineering
7. Success metrics with targets

Feature list:
[Paste your features as a numbered list — can include brief descriptions]

Context:
- User segment: [Who we're building for right now]
- Quarter goal: [What we're trying to achieve this quarter]
- Team size: [Engineering capacity in rough terms — e.g., 4 engineers]
- Timeline: [How many weeks in the sprint or quarter]

Run RICE + MoSCoW scoring for each feature.
Return:
1. Scored feature table (RICE score + MoSCoW classification)
2. Ranked top 5 to ship this sprint/quarter
3. Rationale for the top 3
4. Features to defer and why

Timeframe: [Next 2 quarters / 6 months / year]

Business goals this period:
1. [Goal 1]
2. [Goal 2]
3. [Goal 3]

Current backlog themes (rough):
[List your major themes or feature buckets]

Constraints:
- Team size: [Engineering capacity]
- Known dependencies or blockers: [List if any]
- Non-negotiables: [Anything that must ship by a specific date]

Build a strategic roadmap. Include:
1. Quarterly themes with rationale
2. Feature groupings by theme
3. Dependency flags
4. Executive summary (3-5 sentences for stakeholder communication)
5. What we're intentionally NOT doing and why

Feature brief: [Describe the feature in plain English — 3-5 sentences is enough]

User type(s): [Who will use this — list roles if multiple]
Core workflow: [What does the user do step-by-step?]
Success state: [What does "done" look like for the user?]
Known edge cases: [Any edge cases already flagged by engineering]

Generate user stories in this format:
As a [role], I want [feature/action] so that [outcome].

For each story include:
- Acceptance criteria (3-5 bullet points)
- Edge case handling
- Priority (P1/P2/P3)
- Estimated complexity (S/M/L)

Model output: [Paste model results, prediction scores, or forecast data here]

Context:
- What the model was trained to predict: [e.g., 30-day churn, conversion likelihood]
- Business context: [What decisions are we trying to make with this?]
- Current action we're taking: [What do we do today when we see these signals?]

Translate this into:
1. Plain-language summary of what the data is saying
2. Top 3 business implications
3. Recommended actions per segment or cohort
4. Metrics to track to validate our response
5. What to tell leadership in one paragraph

Company-level goals this quarter:
1. [Goal 1]
2. [Goal 2]
3. [Goal 3]

My team: [Team name and primary function — e.g., Growth PM team, 4 people]
Team mandate: [What your team is responsible for in plain English]

Build a full OKR framework for my team. Include:
1. 2-3 Objectives aligned to company goals
2. 3-5 Key Results per Objective (measurable, with targets)
3. Scoring rubric (0.0-1.0 scale with what each score means)
4. Monthly check-in template
5. Flags for OKRs that may have measurement challenges