docs(19): create phase plan — 3 plans in 3 waves

.planning/ROADMAP.md

@@ -413,9 +413,16 @@ Plans:
   3. Signer assignment in the template editor accepts role labels ("Buyer", "Seller", "Agent") rather than email addresses — role strings are stored in the `signerEmail` slot and the editor does not reject them as invalid emails
   4. Agent can set a text hint on any text field — the hint is stored in the template and is visible as a placeholder label in the editor
   5. Agent can click Save and the current field layout (with role labels and text hints) is persisted to `document_templates.signatureFields` — a subsequent page reload shows the saved state
-**Plans**: TBD
+**Plans**: 3 plans
+
+Plans:
+- [ ] 19-01-PLAN.md — FieldPlacer/PdfViewer prop abstraction (onPersist, fieldsUrl, fileUrl), three template API routes (file, fields, ai-prepare), PortalNav Templates link
+- [ ] 19-02-PLAN.md — Templates list page with create modal, template editor page (TemplatePageClient + TemplatePanel with roles, AI, save)
+- [ ] 19-03-PLAN.md — Full Phase 19 human verification checkpoint (9-step E2E browser test)
 **UI hint**: yes
 
+
+
 ### Phase 20: Apply Template and Portal Nav
 **Goal**: Agent can start any new client document from a saved template — all fields are pre-loaded with fresh IDs, roles map to real signer emails, text hints appear as quick-fill suggestions — and "Templates" is a top-level portal destination
 **Depends on**: Phase 19