SKILL FILE

PRD Generator with AI

Transform messy product ideas into structured PRDs that get stakeholder alignment BEFORE engineering starts building. Full requirements without the PM tax.

Download Skill File ↓

What this skill file teaches Claude

Drop one markdown file into your repo. Claude Code learns how to run this entire workflow.

1

Full structured PRD

Problem, user, success criteria, scope (in/out), assumptions, dependencies, open questions — the standard sections, filled in.

2

Pulls from upstream artefacts

Takes the product brief, persona, JTBD, interview snapshots as input — synthesises into the PRD.

3

Edge cases surfaced

Common edge cases the skill knows to ask about (auth states, empty states, error handling, localisation) — no more missing them.

4

Acceptance criteria per requirement

Each requirement gets clear acceptance criteria so QA + eng know "done."

5

Open-questions list

Honest about what's unresolved — flagged for follow-up rather than hand-waved.

What you can build with this

New feature from scratch

Got an approved brief? Generate the PRD that engineering can scope from.

Formalise verbal agreements

The product was designed in a meeting and now it needs to be written down. The skill structures the verbal into a doc.

Pre-engineering alignment

Make sure design, eng, and PM agree on scope BEFORE engineering starts.

Get the full skill file

Everything above is 80% of the skill file. Download the complete version with full implementation details, agent prompts, and ready-to-run scripts.

Common questions

A product brief (ideal), or messy notes / Slack thread / meeting transcript. The richer the input, the better the PRD. The skill will flag gaps it can't fill in.
Templates give you the sections; you still have to fill them in. The skill generates the actual content based on your input — and flags what's missing.
For substantial features, yes — the brief gets leadership sign-off cheaply. The PRD then takes the approved brief into engineering-ready spec.
For UI features, yes — paired with designs. For backend / infra features, you'll usually want the technical-spec-writer skill on top of the PRD.
3–8 pages depending on feature complexity. The skill resists ballooning by flagging when a section is too long for the value it adds.

Ready to automate?

SoloStack gives you every skill pre-installed — scraping, marketing, sales, CRM, and more. One repo. Every department.

Book a Call →