How-to · Product Management · By Dean Peters (PM)

How to use PRD Development Workshop in your AI agent

Install and use the PRD Development Workshop skill in Claude Code, Cursor, Codex, Gemini CLI, OpenCode, and Windsurf — with sample prompts.

What you'll get

This skill guides product managers through creating a structured Product Requirements Document (PRD) from scratch. It orchestrates problem framing, user research synthesis, solution definition, and success metrics into a cohesive document. Instead of scattered Slack threads and incomplete notes, you get a comprehensive PRD that aligns stakeholders, provides engineering context, and serves as your source of truth—preventing ambiguity, scope creep, and miscommunication.

Step 1 — Get the skill source URL

The PRD Development Workshop skill lives at:

Step 2 — Add it to your AI agent

Copy one of these prompts and paste it into your AI tool. The agent will fetch and install the skill for you.

Claude Code

Add the agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/prd-development to my project.

Cursor

Install this agent skill: https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/prd-development

Codex

Add this skill to .codex/skills/: https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/prd-development

Gemini CLI

Add the skill at https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/prd-development to my .gemini/skills/ directory.

OpenCode

Install this agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/prd-development

Windsurf

Add this skill: https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/prd-development

Step 3 — Try these prompts

Once the skill is installed, ask your AI things like:

  • 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
  • Document requirements before development begins on a significant project
  • Create a shared source of truth that prevents scope creep and miscommunication

What this skill does

  • 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
Made byDean Peters (PM)
CategoryProduct Management