PRD Development Workshop vs User Story Writer — Which AI Skill Should You Use?

The short version

By Dean Peters (PM)

Turn scattered discovery notes into a clear, complete PRD that aligns your team and gets engineers building.

By Dean Peters (PM)

Turn ideas into clear user stories with testable acceptance criteria—no dev work required.

Walks you through 8 phases of PRD creation, from executive summary to user stories and success metrics
Structures your discovery insights into sections: problem statement, personas, strategic context, solution overview, and requirements
Generates a complete PRD document that engineering can act on, with acceptance criteria and scope boundaries
Captures the 'why' behind decisions so future team members understand strategic context
Provides a standard template covering problem, users, solution, metrics, dependencies, and out-of-scope items

Formats user needs using the industry-standard Mike Cohn template (As a/I want/So that)
Generates Gherkin-style acceptance criteria that define when the work is done
Ensures stories focus on user outcomes rather than just features or tasks
Provides quality checks to catch vague requirements before they reach the dev team
Includes templates and examples for writing product-ready stories quickly

You're starting a major feature or product initiative and need to align your team
You've finished discovery research and need to turn findings into an engineering-ready document
You need to document requirements before development begins on a significant project
You want to create a shared source of truth that prevents scope creep and miscommunication