Agent skill · product strategy · aiskillstore
prd
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
Why this skill is useful
Provides a structured approach to generating PRDs that includes specific criteria and templates not commonly found in generic documentation.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Product Requirements Document (PRD) Overview Design comprehensive, production-grade Product Requirements Documents (PRDs) that bridge the gap between business vision and technical execution. This skill works for modern software systems, ensuring that requirements are clearly defined. When to Use Use this skill when: Starting a new product or feature development cycle Translating a vague idea into a concrete technical specification Defining requirements for AI-powered features Stakeholders need a unified "source of truth" for project scope User asks to "write a PRD", "document requirements", or "plan a feature" --- Operational Workflow Phase 1: Discovery (The Interview) Before writing a single line of the PRD, you MUST interrogate the user to fill knowledge gaps. Do not assume context. Ask about: The Core Problem: Why are we building this now? Success Metrics: How do we know it worked? Constraints: Budget, tech stack, or deadline? Phase 2: Analysis & Scoping Synthesize the user's input. Identify dependencies and hidden complexities. Map out the User Flow. Define Non-Goals to protect the timeline. Phase 3: Technical Drafting Generate the document using the Strict PRD Schema below. --- PRD Quality Standards Requirements Quality Use concrete, measurable criteria. Avoid "fast", "easy", or "intuitive". --- Strict PRD Schema You MUST follow this exact structure for the output: 1. Executive Summary Problem Statement: 1-2 sentences on the pain point. Proposed Solution: 1-2 sentences on the fix. Success Criteria: 3-5 measurable KPIs. 2. User Experience & Functionality User Personas: Who is this for? User Stories: As a [user], I want to [action] so that [benefit]. Acceptance Criteria: Bulleted list of "Done" definitions for each story. Non-Goals: What are we NOT building? 3. AI System Requirements (If Applicable) Tool Requirements: What tools and APIs are needed? Evaluation Strategy: How to measure output quality and accuracy. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/prd