Skip to main content
CodingArchitectureadvanced

Engineering RFC & Technical Design Document Author

Optimized for Claude, Chatgpt, Gemini • Verified Prompt Template

Author comprehensive Request for Comments (RFC) documents detailing alternatives considered, trade-offs, and rollout risks.

Compatibility & Specs

Compatible AI Models
ClaudeChatGPTGemini
Last UpdatedApr 1, 2026
Customizable Variables5 parameters

How to Use This Prompt

Follow this 3-step workflow to extract high-signal responses from any compatible AI model.

01

1. Tailor the Parameters

Use the interactive customizer above to substitute the bracketed placeholders with your exact context, requirements, and constraints.

02

2. Send to AI Model

Copy the prompt and paste it into Claude, ChatGPT, Gemini, or Copilot. These models follow structured multi-step constraints reliably.

03

3. Review and Iterate

Review the output against the verified benchmark below. Follow up in the conversation to stress-test edge cases or refine tone.

Prompt Variables & Parameters

Reference breakdown of every dynamic variable embedded in this prompt template.

PlaceholderParameter NameTypeStatusDescription & Guidance
[initiative_title]Initiative TitletextRequiredDescriptive name of the RFCDefault: RFC-089: Distributed Webhook Delivery & Event Retry Engine
[problem_statement]Problem Statement & FrictiontextareaRequiredWhy current architecture is failingDefault: Currently, third-party partner webhooks are dispatched synchronously inside our main HTTP checkout thread. When customer endpoints time out or return 500 errors, our worker threads stall, causing checkout thread pool exhaustion and message loss.
[proposed_solution]Proposed Technical SolutiontextareaRequiredYour intended architectural designDefault: Decouple webhook dispatching into an asynchronous event-driven queue powered by Redis Streams and background worker pods using exponential backoff with jitter and a Dead-Letter Queue (DLQ).
[alternatives_considered]Alternatives ConsideredtextareaRequiredOther options and why they were not chosenDefault: Alternative 1: Managed SaaS (Svix) - Rejected due to data residency compliance requirements. Alternative 2: Dedicated Kafka cluster - Rejected due to disproportionate operational maintenance overhead.
[non_goals]Explicit Non-GoalstextareaOptionalWhat this project deliberately will NOT solveDefault: 1. Not building a self-service customer UI for viewing webhook logs in this phase; 2. Not supporting custom payload encryption keys beyond standard HMAC-SHA256 signatures.

Example Output & Parameters Breakdown

Inspect verified benchmark AI responses and review how parameters, system constraints, and input variables calibrate generation.

Parameters & Variable Breakdown

5 Inputs
[initiative_title]
RFC-089: Distributed Webhook Delivery & Event Retry Engine
[problem_statement]
Currently, third-party partner webhooks are dispatched synchronously inside our main HTTP checkout thread. When customer endpoints time out or return 500 errors, our worker threads stall, causing checkout thread pool exhaustion and message loss.
[proposed_solution]
Decouple webhook dispatching into an asynchronous event-driven queue powered by Redis Streams and background worker pods using exponential backoff with jitter and a Dead-Letter Queue (DLQ).
[alternatives_considered]
Alternative 1: Managed SaaS (Svix) - Rejected due to data residency compliance requirements. Alternative 2: Dedicated Kafka cluster - Rejected due to disproportionate operational maintenance overhead.
[non_goals]
1. Not building a self-service customer UI for viewing webhook logs in this phase; 2. Not supporting custom payload encryption keys beyond standard HMAC-SHA256 signatures.

Verified AI Benchmark Response

Grounded Output
### RFC-089: Distributed Webhook Delivery & Event Retry Engine **Status:** DRAFT | **Author:** Staff Infrastructure Engineer | **Target Date:** Q3 ### 1. Context & Problem Statement Today, third-party webhook dispatches are coupled directly to the HTTP checkout request lifecycle. If a customer webhook endpoint hangs for 15 seconds, our application thread remains blocked. During a partner outage on Aug 14, 180 worker threads were consumed waiting on dead endpoints, triggering a cascade of 504 Gateway Timeouts across unrelated API routes. ### 2. Goals & Non-Goals - **Goal:** Guarantee sub-5ms return time for internal events by decoupling dispatch asynchronously. - **Goal:** Provide guaranteed at-least-once delivery with exponential backoff (1m, 5m, 30m, 2h, 24h). - **Non-Goal:** Customer-facing payload inspection UI (deferred to RFC-094). ### 5. Alternatives Considered & Rejection Rationale - **Svix (Third-Party Managed Service):** Would save 4 weeks of engineering effort, but requires routing sensitive EU customer metadata through a third-party multi-tenant cloud, conflicting with our HIPAA/GDPR vendor compliance boundaries. - **Apache Kafka:** Provides higher throughput, but introduces ZooKeeper/KRaft operational burden that our 8-person team cannot sustainably maintain.

Best Use Cases

Scenarios and roles where this prompt produces maximum leverage.

Staff and Senior engineers pitching major infrastructure changes to leadership
Engineering teams establishing institutional RFC templates for architectural governance
Developers proposing significant database migrations or third-party service deprecations

Tips for Best Results

Techniques to elevate response fidelity

  • •Provide rich background context rather than one-sentence inputs to receive deep, non-generic responses.
  • •Engage in multi-turn conversation: use the initial output as a baseline, then ask the AI to sharpen specific sections.
  • •Prompt the model to highlight any hidden assumptions or missing trade-offs in its recommendations.

Common Mistakes to Avoid

Frequent failure modes and anti-patterns

  • •Giving minimal context and expecting nuanced, expert-level strategic output.
  • •Not validating factual references, citations, or statistical claims with verified primary sources.
  • •Skipping the customization step and pasting raw bracketed template variables into the AI chat.

Frequently Asked Questions About This Prompt

Technical guidance on model compatibility, parameter substitution, iteration techniques, and commercial usage.

Q1.Which AI models work best with the "Engineering RFC & Technical Design Document Author" prompt?

This prompt is thoroughly tested and compatible with Claude, Chatgpt, Gemini. For multi-step reasoning, architectural planning, and code refactoring, Claude 3.7/3.5 Sonnet and ChatGPT-4o provide the highest constraint adherence. For large-document synthesis, Google Gemini 2.5 Pro is also recommended.

Q2.How do I customize the parameters in this prompt template?

This template features 5 customizable parameter(s): [initiative_title], [problem_statement], [proposed_solution], [alternatives_considered], [non_goals]. Replace each bracketed placeholder with your project's specific details, constraints, or code before submitting to your AI model. You can also use our interactive workbench on this page to populate and copy the completed prompt in one click.

Q3.Can I use this prompt and its outputs for commercial projects?

Yes. All prompts published on Beautiful AI Prompt are 100% free for both personal and commercial use. You hold full ownership of all code, copy, strategies, or imagery generated by your selected AI model when running this prompt.

Q4.How does this prompt prevent AI hallucinations and ensure output accuracy?

This template enforces explicit negative constraints, few-shot parameter boundaries, and schema requirements (such as tabular comparisons or step-by-step logic). This suppresses speculative drift and forces the AI model to ground its response in your provided inputs.

Part of Curated Collections

This prompt is sequenced as part of these goal-oriented workflows

View all collections

Related AI Prompts

Complementary workflows in Coding

View all Coding prompts
Codingadvanced

Principal Code Reviewer & Architecture Auditor

Conduct rigorous architectural code reviews identifying memory leaks, race conditions, and typing holes.

[Copy & Paste Template]4 parameters

›You are a Principal Software Architect conducting an uncompromising production code review. Programming Language & Stack: [language_stack] Primary Objective: [primary_objective] Target Strictness: [strictness_level] Code to review: ``` [code_to_review] ``` Deliver your review in this structured format: 1. Executive Summary: 2-sentence verdict on production-readiness. 2. Critical Vulnerabilities & Bugs: Race conditions, unhandled exceptions, memory leaks, security flaws (OWASP), or type unsafety. 3. Architecture & Separation of Concerns: Assess coupling, cohesion, testability, and state management. 4. Complete Before & After Refactoring: Rewrite the code adhering to clean architecture, full typing, and explicit error handling. 5. Performance & Complexity Analysis: Big-O time and space delta between original and refactored versions.

claudechatgptcopilot
#code-review#clean-code#architecture
Codingadvanced

Pragmatic REST & GraphQL API Contract Architect

Design robust, backwards-compatible API contracts with clean error schemas, pagination, and idempotency keys.

[Copy & Paste Template]4 parameters

›You are a Principal API Architect and API Governance Director. I need to design a clean, backwards-compatible, and enterprise-grade API contract for [entity_domain] operations. API Paradigm: [api_paradigm] Primary Client Consumers: [client_consumers] Key Use Cases & Capabilities Needed: [api_use_cases] Deliver a complete production API contract specification: 1. Resource Schema / Type Definitions: Full TypeScript / GraphQL interface definitions with strict field nullability, scalar types, and descriptive field comments. 2. Endpoint / Mutation Design: Complete HTTP routes (verbs, paths, query parameters) or GraphQL queries/mutations following idiomatic naming conventions. 3. Idempotency & Concurrency Control: Exact headers (e.g. `Idempotency-Key`, `If-Match` ETag) and mechanics for safe payment/mutation retries. 4. Standardized Error Response Envelope: RFC 7807 Problem Details JSON format specifying machine-readable error codes, human messages, and field-level validation error arrays. 5. Cursor Pagination & Filtering: Efficient cursor-based pagination schema for large datasets.

claudechatgptgemini
#api-design#rest-api#graphql
Codingadvanced

Monolith to Modular Decoupling & Boundary Architect

Carve clear bounded contexts out of entangled monoliths using the Strangler Fig pattern and event-driven seams.

[Copy & Paste Template]4 parameters

›You are a Principal Software Architect and Distributed Systems Strategist. I need to decouple a critical domain out of an entangled monolith without causing downtime or disrupting ongoing product feature velocity. Existing Monolith Stack & Database: [monolith_stack] Target Domain to Extract: [domain_to_extract] Known Entanglements & Shared Dependencies: [shared_entanglements] Target Architecture: [target_architecture] Deliver a step-by-step Modular Decoupling Blueprint: 1. Bounded Context & Interface Seams: Define the strict input/output API contract and domain events (`OrderCreated`, `InventoryReserved`) for the extracted module. 2. Database Decoupling & Dual-Write Migration Strategy: Exact 4-phase database transition protocol (Dual-write -> Backfill -> Read from new -> Deprecate old) avoiding distributed transactions (2PC). 3. Strangler Fig Routing Architecture: How API gateway / reverse proxy rules will incrementally route 1% -> 10% -> 100% of traffic to the new service. 4. Failure Modes & Rollback Safety: What to do if the extracted service fails or introduces cross-service latency degradation.

claudechatgptgemini
#software-architecture#refactoring#monolith-to-microservices

Related Engineering Guides

Deep-dive playbooks and system prompt methodologies for Coding

View all guides