wowprompt

Technical design document for a new feature

Writes an engineering design document for a feature, covering the approach, data changes, interfaces, risks, rollout and alternatives considered, ready for team review. Use it before building anything that touches several parts of a system or that would be costly to undo.

A design document with context, goals and non-goals, the proposed design, data model and API changes, alternatives, risks, rollout and open questions
The output this prompt produced, unedited.

The prompt

Goal

A design document reviewers can approve or challenge in one meeting, because the decisions and trade-offs are written down.

Inputs

  • Feature and the problem it solves: [description, link to requirements if any]
  • Current system: [stack, main components, where the feature fits]
  • Constraints: [deadline, budget, hosting limits, compliance needs, team size]
  • Expected scale: [users, requests per second, data size, growth]
  • Ideas already discussed: [approaches the team is considering]

Steps

  1. State the context and the problem in a few sentences.
  2. List goals and non-goals, so scope is clear.
  3. Describe the proposed design: components, data flow, data model changes and API changes.
  4. Compare at least two alternatives with their trade-offs.
  5. Cover security, privacy, performance, failure modes, testing, rollout with a feature flag, and rollback.

Output format

  • Title, status (draft) and summary in three sentences.
  • Context and problem.
  • Goals and non-goals.
  • Proposed design, with a text diagram of the data flow in a code block.
  • Data model and API changes, as tables.
  • | Alternative | Pros | Cons | Why not chosen |
  • Risks and mitigations.
  • Rollout plan and rollback plan.
  • Open questions for reviewers.

Check before answering

  • Every non-goal is something a reader might reasonably expect, so it prevents scope creep.
  • Security covers authentication, authorisation, input validation and secrets handling.
  • Rollback is possible without data loss, or the document says clearly that it is not.
  • No technology is recommended that the constraints rule out.
technical design documentsoftware design docsystem designengineering rfcarchitecture proposalfeature design

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity