Part of Build Product Features With PM Guidance
Product & Design Blueprint
Safety checkedWrite Product Requirements With Clarity
A skill that generates structured PRDs with hypothesis, problem, solution, and metrics, asking clarifying questions first.
What problem does this solve?
Generates product requirement documents that align teams without meetings. It asks 3-5 clarifying questions before writing, follows a stage-appropriate structure (from lightweight speclets to full launch-readiness specs), and flags unknowns instead of fabricating data.
How does it work?
- Say 'write a PRD' or 'spec out [feature]'. 2. Claude asks clarifying questions about the user problem, scope, timeline, and constraints. 3. It generates a PRD in the stage you're at (kickoff, planning, solution review, or launch readiness) with hypothesis, problem, strategic fit, solution, non-goals, success metrics, and rollout plan. 4. You can ask it to review the PRD as an engineer, designer, or skeptic, or tighten it into an executive summary. Output: a 2-3 page PRD that carries your context and voice, ready to drive team discussion.
Included Skills
No skills in this group
What's required to run this?
Triggered by 'write a PRD', 'create a PRD', 'draft a PRD', 'PRD for [feature]', 'spec out [feature]', or 'one pager for [feature]'. Inherits context from CLAUDE.md including your role, product, OKRs, and terminology. Enforces a 2-page default unless you ask for more.
Key Features
Clarifying Questions
Never generates blind. Asks for user segment, data, scope, technical constraints, and timeline before drafting.
Stage-Aware Structure
Adapts the PRD to your stage: lightweight speclets for kickoff, 1-pagers for planning, full specs for solution review, detailed edge cases for launch readiness.
Evidence-Based Sections
Problem section requires customer quotes, support tickets, or usage data. Flags gaps with [NEED: data from X] instead of guessing.
Success Metrics Framework
Includes primary metric with target, secondary metrics, guardrail metrics with baselines, and rollout success criteria.
Sub-Agent Review
Review the PRD as engineer (feasibility), designer (usability), executive (strategy), skeptic (risks), or customer (value).
Tools in this Blueprint
About This Blueprint
- Industry
- Technology
More Blueprints to explore
⭐ Ask Nicely : Find your next reviewers
Pick promoters from your CRM, remove accounts with open escalations, overdue billing or a recent review, then create the G2 review campaign after you approve the list, send method and any incentive.
G2CRMSurvey or CS platform+4 moreCharlie Albuery
🤝 You Said We Did : Align your roadmap to real user feedback
Group recent G2 reviews into themes, check each theme against tickets in your work tracker, and return a ranked one-page brief that lists the themes with no ticket first.
G2Work trackerResearch repository+3 moreCharlie Albuery
👀 Wandering Eyes : Identify churn risk early
Match accounts renewing soon in your CRM to G2 buyer intent on competitors and your category, check usage, support and meetings, then rank the accounts and brief the CSM. Runs as a weekly sweep or on one named account.
G2CRMProduct usage analytics+4 moreCharlie Albuery