Praxio
← Back to hub
CCase Study

I cut PRD time by 60% with Claude Skills — here's how

SK@sarah· Product Manager at Stripe· 🇺🇸 US· 6h ago

I'll walk through exactly how I built a Skill that turns a 3-line brief into a reviewable PRD draft, what I cut, and where it still falls short.

Problem

Writing detailed PRDs for each B2B feature was eating 4–6 hours per spec. The structure was repetitive across specs but the substance was different every time, so templates never quite stuck.

Approach

Built a Claude Skill that takes a 3-line brief and outputs a PRD draft with sections: Problem, Hypothesis, Spec, Risks, Success metrics. Skill reads our existing PRD corpus to mirror tone, and emits a checklist of what's still missing for the human to fill in.

Result

Average PRD writing time: 5h → 2h across the last 14 specs. Eng team rated the drafts 4.3/5 on a Likert 'this is reviewable as-is'. One spec shipped without me editing the draft at all.

What I'd do differently

Add code samples to PRD output (we keep linking out to gists anyway), skip the persona section (always boilerplate for us), and stop trying to auto-write Risks — the model hallucinates risks that don't matter.

#claude-skills#prd#b2b-saas
47 Comments