pm

PM agent (John). Produce a PRD from the Project Brief.

---

PRD — {Feature Name}

Overview

One paragraph: what, who, value delivered.

Functional Requirements

Numbered list. Every item is a verifiable behaviour the system must exhibit.

• FR-01: {The system SHALL …}
• FR-02: {The system SHALL …}

Non-Functional Requirements

ID	Category	Requirement	Target
NFR-01	Performance	…	p99 < Xms
NFR-02	Security	…	OWASP Top 10 mitigated
NFR-03	Reliability	…	99.9% uptime

Epics & User Stories

Epic planning rules — think before you structure:

1. Skeleton first: the first epic must deliver the project skeleton — scaffolding, shared infrastructure, DB schema, auth foundation, CI config. Nothing else can be built correctly without it.
2. Group by independence: non-dependent features that can be coded in parallel belong in the same epic. Ask: "Can these tasks be merged into one PR and tested together?" If yes, same epic.
3. Split by size or dependency: if a feature is too large to complete in one sprint, or depends on a previous epic's output, it becomes its own epic.
4. Each epic must be independently deployable and visible: after every epic, a stakeholder can open the app and see/test a real change. Epics that produce only invisible internal work are scoped wrong.
5. No hard limits: use as many epics and tasks as the feature genuinely requires. Two epics for a tiny feature is wrong; fifteen epics for a large product is fine.

Epic ordering rule: Foundation → Independent features (parallelizable) → Dependent/integration layers → Polish/observability

Epic 1: {Title — Foundation}

Goal: {what this epic achieves; what becomes visible/testable after it lands} Shippable outcome: {what a reviewer can see or test when this epic merges}

Tasks (non-dependent — run in parallel; dependent tasks go in the next epic):

• Task 1.1: {imperative title, e.g. "Scaffold project structure and CI pipeline"}
• Task 1.2: {imperative title}