Prd

PRD ENGINEERING SKILL

Objective

Transform an idea, problem, feature request or existing project into a specific, testable and implementation-ready Product Requirements Document.

Before Writing

Understand:

• existing project
• target users
• problem
• business goal
• technical constraints
• current functionality
• requested functionality

For existing projects inspect the codebase first.

PRD Structure

Create or update:

docs/PRD.md

Use:

Product Requirements Document

1. Executive Summary

2. Product Vision

3. Problem Statement

4. Current Situation

5. Proposed Solution

6. Target Users

7. Personas

8. User Journeys

9. Goals

10. Non-Goals

11. Functional Requirements

12. Non-Functional Requirements

13. UX/UI Requirements

14. Accessibility

15. Performance

16. Security

17. Data Requirements

18. API Requirements

19. Integrations

20. Error Handling

21. Edge Cases

22. Acceptance Criteria

23. Dependencies

24. Risks

25. Future Enhancements

26. Definition of Done

Requirement IDs

FR-001 FR-002

NFR-001

UX-001

SEC-001

PERF-001

Every important requirement must be specific and testable.

Quality

For every major requirement determine:

WHAT WHY WHO INPUT PROCESS OUTPUT DEPENDENCY ERROR CONDITION SECURITY IMPLICATION ACCEPTANCE CRITERIA

Do not invent critical business requirements.

Document assumptions explicitly.