Mati's PRD Template

matis_prd_template.md

#[ID]: [Feature Name] – Product Requirements Document (PRD)

Version

• Project: edenlm.com
• Date: [YYYY-MM-DD]
• Author: [Name] (Mati, unless stated otherwise)
• Status: [Draft/Accepted/Implemented/Archived]

---

1. Purpose

[One to two paragraphs describing the feature's purpose and the problem it solves. Be specific about the user need or business opportunity being addressed.]

---

2. Goals & Success Criteria

#	Goal	Success Metric
G1	[Primary goal]	[How will you measure success?]
G2	[Secondary goal]	[How will you measure success?]
G3	[Additional goal]	[How will you measure success?]

Success must be verifiable by the AI / LLM that will be writing the code later, using tools like Codex or Cursor.

3. Non-Goals

[List what is explicitly out of scope for this feature. This helps set expectations and prevent scope creep.]

• [Non-goal 1]
• [Non-goal 2]
• [Non-goal 3]

---

4. User Stories

1. As a [user type], [description of what the user wants to accomplish and why].
2. As a [user type], [description of what the user wants to accomplish and why].
3. As a [user type], [description of what the user wants to accomplish and why].
4. As a [developer/admin], [description of what the internal user needs to accomplish].

---

5. UX & UI Requirements

[If applicable, describe the user experience and interface requirements. Delete this section if not relevant.]

• Key Principle: [Core UX principle]
• UI Component Placement: [Where should UI elements be placed?]
• UI Component Design: [Description of how the UI should look and behave]
• Default State: [What is the default state of the UI?]
• Visual Indicators: [What visual indicators are needed?]
• Accessibility: [Accessibility requirements]

---

6. Technical Requirements

6.1 Frontend

[List frontend implementation requirements]

• [Requirement 1]
• [Requirement 2]

6.2 Backend / API

[List backend and API implementation requirements]

• [Requirement 1]
• [Requirement 2]

6.3 Database

[Describe database changes, if any]

[Schema example, if applicable]

6.4 Additional Technical Components

[List any other technical components or requirements]

• [Component 1]
• [Component 2]

---

7. Security & Privacy

[Describe security and privacy considerations]

• [Security consideration 1]
• [Privacy consideration 1]

---

8. Risks & Mitigations

Risk	Likelihood	Impact	Mitigation
[Risk 1]	[Low/Medium/High]	[Low/Medium/High]	[How will this risk be mitigated?]
[Risk 2]	[Low/Medium/High]	[Low/Medium/High]	[How will this risk be mitigated?]
[Risk 3]	[Low/Medium/High]	[Low/Medium/High]	[How will this risk be mitigated?]

---

9. Open Questions

1. [Question 1]
2. [Question 2]
3. [Question 3]

---

10. Implementation Checklist

[Component/Area 1]

• [Task 1]
• [Task 2]
• [Task 3]

[Component/Area 2]

• [Task 1]
• [Task 2]
• [Task 3]

QA & Testing

• [Test 1]
• [Test 2]
• [Test 3]

Documentation

• [Documentation task 1]
• [Documentation task 2] Any new script shall be documented in README.md

---

11. Future Enhancements

[List potential future enhancements or extensions to this feature]

• [Enhancement 1]
• [Enhancement 2]
• [Enhancement 3]

---

12. Implementation Notes/Comments

[This section is for post-implementation notes. Leave blank in the initial PRD, to be filled in during/after implementation.]

Technical Challenges

[Document any significant technical challenges encountered during implementation]

Feature Scope Adjustments

[Document any scope adjustments made during implementation]

Testing Expectations (non-negotiable!)

[Specific, non-negotiable testing expectations based on implementation]

Next Steps

[Immediate next steps or dependencies]