Write Product Requirements With Clarity1 skill
A skill that generates structured PRDs with hypothesis, problem, solution, and metrics, asking clarifying questions first.
Product & Design Blueprint
Safety checkedA Claude Code configuration with 6 PM skills and 4 templates for product work.
Copy this prompt and paste it into your AI agent to install.
Gives your product team Claude-powered PM guidance that understands your product context, writing style, and process. It runs inside Claude Code (no external setup), so instead of context-switching to a new tool, you work directly in your project and ask Claude to write PRDs, define metrics, analyze competitors, or plan sprints with your team already in the room.
A skill that generates structured PRDs with hypothesis, problem, solution, and metrics, asking clarifying questions first.
A skill that structures metrics into primary, secondary, guardrail, leading indicators, and anti-metrics with measurement methods and baselines.
A skill that breaks down competitor products into smart decisions, weak spots, and strategic implications for your product.
A skill that generates risk-scaled launch checklists with pre-launch, launch-day, and post-launch phases tailored to your feature's risk level.
A skill that organizes backlog items into a sprint with capacity checks, priority ordering, risk flagging, and stretch goals.
A skill that ranks research findings by evidence strength, identifies themes and surprises, and outputs product implications.
Your team builds features with PM rigor baked in, because Claude knows your product context, your OKRs, your terminology, and your writing style from the moment you ask.
Requires Claude Code (the desktop client) because the setup relies on local file discovery and context loading at session start. CLAUDE.md must be in your project root; Claude loads it automatically when you start Claude Code in that directory. Skills stored in .claude/skills/ are loaded on demand by trigger phrase. File paths and casing are strict.
CLAUDE.md must stay under 150 lines or Claude begins ignoring instructions. Prune aggressively. Skills are generic examples. Their real power emerges when you customize them with your actual product data. Sessions degrade after 40-50 exchanges; use handoff files or /clear to reset. This setup is Claude Code only; it requires Code access, not the web chat.
Context System
CLAUDE.md file that you customize once with your role, product, OKRs, and team roles. All skills inherit this context automatically.
PRD Writer Skill
Writes structured product requirement documents with hypothesis, problem, solution, and success metrics. Asks clarifying questions first, never assumes.
Metrics Definer Skill
Defines primary metrics, guardrails, leading indicators, and anti-metrics with baselines and measurement methods.
Competitive Analysis Skill
Analyzes competitors by identifying smart decisions, weak spots, and implications for your product strategy.
Sub-Agent Roles
Invoke 6 reviewer personas (engineer, designer, executive, skeptic, customer, data analyst) to review deliverables from different lenses.
Shoppers get accurate answers about fit, compatibility, ingredients, and delivery even when your team is offline, so fewer leave before checkout. Conversation insights also reveal which product-page details could prevent the next unanswered question.
Urska B.
GTM Lead
Catch a few unusual tickets before a product or fulfillment issue turns into hundreds of refunds, chargebacks, and bad reviews. Cluster transcript evidence by SKU, order date, location, and carrier so operations can trace the cause and support can reach affected customers early.
Urska B.
GTM Lead
Catch rising complaints before they spread, with weekly ticket themes grounded in customer quotes and verified against the original conversations. A Slack digest assigns each issue to the team that can act, so product, operations, and CX can respond sooner.
Urska B.
GTM Lead