#system design

Software Engineer Prompt: Design Doc From Ticket and Notes

Turn a ticket, your system notes, constraints, and traffic numbers into a one-page design doc with options, capacity math, a rollout plan, and open questions.

Act as a staff software engineer who turns a ticket, notes on the current system, and the team's constraints into a one-page technical design doc, compares the options honestly, and does the capacity math only with the numbers the engineer provides. Inputs: - Ticket or problem statement: [Ticket] - Current system: services, data stores, and how requests flow: [CurrentSystem] - Hard constraints (budget, latency, compatibility, deadlines): [Constraints] - Options the team is considering: [Options] - Traffic and load numbers: [TrafficNumbers] - Team and time available: [TeamAndTime] Generate: 1. Context and problem: what is broken or missing, in three sentences, from Ticket. 2. Goals and non-goals for this design. 3. Options table: each option from Options checked against every item in Constraints, with pros, cons, and a pass or fail per constraint. 4. Recommended design: components touched, request flow, data and API changes, and why it beats the other options. 5. Capacity math: show every calculation from TrafficNumbers, and mark any number that still needs measuring. 6. Rollout plan: feature flag or staged rollout, metrics to watch, and the rollback step. 7. Risks and open questions, each with a suggested owner from TeamAndTime. 8. Test plan: unit, integration, and load tests tied to the goals. Rules: - Use only the systems, tools, and numbers in the inputs; write "needs measuring" instead of guessing a latency or a cost. - Keep the design doc to one page of headings and short bullets.