---
description: Natural language to professional PRD generator
---

# PRD Guide Skill

## Purpose
Convert natural language feature requests into comprehensive, AI-ready Product Requirement Documents (PRDs) that follow a standardized, high-quality structure.

## Workflow
1. **Intake & Clarification**: 
   - Accept natural language description.
   - Ask clarifying questions if the request is ambiguous (e.g., "Who is the target user?", "Are there performance constraints?").
2. **Analysis**: 
   - Break down the request into functional and non-functional requirements.
   - Identify dependencies and risks.
3. **Drafting**: 
   - Generate a structured PRD using the format below.
4. **Validation**: 
   - Self-correct against the "Validation Checklist".

## PRD Structure Template

```markdown
# [Feature Name] PRD

## 1. Executive Summary
- **Problem**: What are we solving?
- **Solution**: High-level approach.
- **Impact**: Expected business/user value.

## 2. User Stories
- As a [role], I want to [action], so that [benefit].
- Acceptance Criteria:
  - [ ] Criterion 1
  - [ ] Criterion 2

## 3. Functional Requirements
- **F-01**: Detail 1
- **F-02**: Detail 2

## 4. Technical Specifications
- **API Changes**: Endpoints to add/modify.
- **Database**: Schema changes.
- **Security**: Auth/Permissions.

## 5. Non-Functional Requirements
- Performance, Scalability, Accessibility (a11y).
```

## Validation Checklist
- [ ] Are all user stories testable?
- [ ] Are error states defined?
- [ ] Is mobile/responsive behavior defined?