Every PM has a PRD template. Most of them live in a Google Doc that gets copy-pasted, half-filled, and sent to engineering with [TBD] scattered across it.
This is a custom Claude skill that turns that process into a conversation. Tell Claude about your product, pick the sections you need, and get a properly formatted .docx back — ready to share.
How it works:
The key thing: It doesn't make up requirements. If you didn't share enough context for a section, it marks it as [PLACEHOLDER: what's needed] instead of hallucinating something plausible-sounding. That's the difference between a useful document and a dangerous one.
Sections you can include:
Executive Summary · Problem Statement · Goals & Success Metrics · Target Users · User Stories · Scope · Functional Requirements · Non-Functional Requirements · UX/Design Considerations · Technical Considerations · Dependencies · Risks & Mitigations · Release Criteria · Timeline & Milestones · Open Questions
What you get:
Built by a Senior BA who's written more PRDs than he'd like to admit. This skill encodes the patterns that actually work — not a generic template.