Product Requirements¶

Product Requirements Documents (PRDs) define what Loryth builds and why. Each PRD traces from personas and user stories through to technical design and implementation.

PRD Process¶

1. Draft — Author writes the PRD based on user stories and persona needs
2. Review — Stakeholders review for completeness and feasibility
3. Approved — PRD is accepted and ready for technical design
4. Implemented — All functional requirements are shipped and verified
5. Deprecated — PRD is no longer relevant (superseded or feature removed)

How PRDs Connect to Other Artifacts¶

graph LR
    V[Vision] --> P[Personas]
    P --> US[User Stories]
    US --> PRD[PRDs]
    PRD --> R[Roadmap]
    PRD --> TD[Technical Design]
    TD --> ADR[ADRs]
    TD --> Code[Implementation]

    classDef active fill:none,stroke:#1976D2,stroke-width:2px,color:#1976D2
    classDef special fill:none,stroke:#8E24AA,stroke-width:2px,color:#8E24AA

    class PRD special
    class V,P,US,R,TD,ADR,Code active

PRD Index¶

Template¶

New PRDs should follow the PRD template.