brse-ticket-breakdownlisted

# BrSE Ticket Breakdown ## Overview Turn a clarified requirement into work items developers and QA can execute independently. **Core principle:** Split by independently verifiable behavior, never by technical layer alone (FE/BE/DB is not a breakdown — it is a dependency map). ## When To Use - A clarified requirement (output of `brse-requirement-clarifier`) is ready to enter a sprint. - A customer asked for "everything in one ticket" and the work has multiple independent acceptance paths. - Sprint planning needs ticket-level dependencies and unknowns surfaced before estimation. ## When NOT To Use - Requirement still has unresolved Open Questions — run clarifier again first. - Customer asked only for an estimate, not a breakdown — do not over-deliver. - Work is a single atomic change (one bugfix, one config update). ## Workflow 1. Confirm the business goal and delivery deadline if provided. 2. Split by independently verifiable behavior, not by vague technical layer. 3. For each ticket, define: - user/business outcome - scope - affected surfaces - implementation notes - acceptance criteria - QA points - dependencies - unknowns 4. Check contract alignment across FE, BE, API/schema, DB, batch, and config when relevant. 5. Flag tasks that require source trace, data confirmation, or customer decision. 6. Keep estimates separate from scope if the user did not ask for hours. ## Output Shape ```markdown ## Breakdown Summary ## Tickets ### [Task ID o