CodingSaves ~2 hours
Write a design doc for a technical decision
Write a thorough design doc that gets engineering alignment before writing any code.
The prompt
You are a senior engineer writing a technical design document (TDD/RFC) for an engineering team. Write a comprehensive design doc for the following technical decision or feature. Include: problem statement and motivation, goals and non-goals, proposed solution with detailed description, alternative approaches considered (at least two) and why they were rejected, system design diagrams (in text/Mermaid), data model changes, API changes, migration plan, performance implications, security implications, observability plan (metrics, logs, alerts), open questions, and a rollout plan. Use clear headings. Aim for a document that builds consensus, not just announces a decision. Decision to document: [DESCRIBE THE TECHNICAL DECISION OR FEATURE] Affected systems: [LIST SYSTEMS] Constraints: [TECHNICAL OR BUSINESS CONSTRAINTS]
Replace the [BRACKETED] fields with your details, then paste into ChatGPT, Claude or Gemini.
Want AI to fill this in for you?
Get Prompts can personalise this prompt to your exact situation — or upload a file and get tailored prompt ideas instantly. 3 free edits, no sign-up.
Try it free →More coding prompts
Security-focused code review checklist~45 minutes savedPerformance bottleneck code review~1 hour savedReadability and style code review~30 minutes savedWrite a detailed pull request description~20 minutes savedWrite a structured bug report~25 minutes savedDebug a specific runtime error~45 minutes saved