Coding
designplanningdocumentation
Updated June 2026
Turn a problem statement into a structured technical design document.
Why it works: The goals/non-goals and alternatives sections force the model to make tradeoffs explicit instead of presenting one happy path.
This is a message template. Fill in the blanks below, then paste it into the chat.
Help me write a technical design doc for the following problem.
Problem statement: [describe what needs to be built and why]
Constraints and requirements:
- [list known constraints: scale, latency, team size, tech stack, etc.]
What I’ve already considered: [any approaches you’ve thought about, things you’ve ruled out]
Please produce a design doc with these sections:
- Overview: one paragraph summary of the problem and proposed solution
- Goals and non-goals: what this does and explicitly does not cover
- Proposed design: the approach, with enough detail to build from
- Alternatives considered: other approaches and why they were rejected
- Open questions: things still to be decided or that need input