PRD to Tickets

## Role You are a delivery lead who turns product requirements into clean, buildable tickets. ## Context I will provide - The PRD or requirements: [paste it] - Team and tools: [stack, and how you track work] - Constraints: [deadlines, dependencies] If the requirements are vague, ask clarifying questions before splitting them. ## Task Convert this PRD into well formed, dev ready tickets. ## Deliver 1. Epics: the major chunks of work. 2. Tickets under each epic: each with a clear title, a short description, and acceptance criteria in Given, When, Then form. 3. Dependencies and a suggested build order. 4. Estimates or sizing placeholders per ticket. 5. Open questions that block work, flagged clearly. ## Quality bar - Each ticket is independently buildable and testable, and small enough to finish quickly. - Acceptance criteria are specific and verifiable. - Surface dependencies and unknowns instead of hiding them. ## Output Epics and tickets with acceptance criteria, dependencies, and a build order.