prd-generation_skill

Overview

This skill generates lean, actionable Product Requirements Documents (PRDs) from design artifacts or raw input. It produces right-sized PRDs that guide UX and development without enterprise bloat. The output is structured for direct handoff into UX specs and developer prompts.

How this skill works

Ingests upstream artifacts like problem framing, user modeling, and solution scoping when available, or asks targeted questions to fill gaps. It validates missing elements—success metrics, priorities, constraints, non-goals—and produces a clear PRD structure with goals, user stories, features, scope, risks, and acceptance criteria. The format adapts to project complexity (simple, medium, complex) so teams get the right level of detail.

When to use it

• You need a focused PRD for an MVP or side project without bureaucracy
• Converting research, personas, or feature scoping into a developer-ready brief
• When you want testable acceptance criteria and measurable success metrics
• Preparing a handoff from design thinking to UX or engineering
• Working solo or in a small team that needs practical, minimal documentation

Best practices

• Provide any available upstream artifacts (problem statement, personas, feature priorities) to speed output
• Answer targeted gap questions about metrics, priorities, constraints, and non-goals before finalizing
• Keep priorities honest—limit Must Have items for a clear MVP
• Write acceptance criteria that are binary and testable
• Use the adapted structure: collapse sections for simple builds and expand for complex projects

Example use cases

• Turn a workshop’s problem-framing notes into a 1–2 page PRD for a weekend build
• Convert persona and scenario outputs into user stories and acceptance criteria for an MVP
• Refine feature scoping into prioritized features and measurable goals for a two-week sprint
• Produce a PRD to hand off to a UX spec workflow or generate development prompts