Architecture Decision Record
Constraints force ChatGPT to evaluate options against your real-world limits, not theoretical ideals. The review date ensures decisions don't become permanent by default.
Help me write an Architecture Decision Record (ADR) for this decision: **Decision:** {{what you're choosing}} (e.g., "Use PostgreSQL over MongoDB for the user service") **Context:** {{why this decision came up}} **Constraints:** - {{constraint 1}} (e.g., "Team has strong SQL experience") - {{constraint 2}} (e.g., "Budget: $500/month for database costs") - {{constraint 3}} (e.g., "Must support full-text search") Write the ADR with these sections: 1. **Status:** Proposed 2. **Context:** The business/technical context (2-3 sentences) 3. **Decision:** What we decided and why 4. **Alternatives considered:** What else we evaluated (pros/cons table) 5. **Consequences:** What changes as a result (both positive and negative) 6. **Review date:** When to revisit this decision
Variables to customize
Why this prompt works
Constraints force ChatGPT to evaluate options against your real-world limits, not theoretical ideals. The review date ensures decisions don't become permanent by default.
What you get when you save this prompt
Your workspace unlocks powerful tools to iterate and improve.
AI Optimization
One-click improvement with structure analysis and pattern suggestions.
Version History
Track every edit. Compare versions side-by-side with word-level diffs.
Folders & Tags
Organize your library with nested folders, tags, and drag-and-drop.
$ npm i -g @promptingbox/mcpUse Everywhere
Access prompts from Claude, Cursor, ChatGPT & more via MCP integration.
Your prompts, organized
Save, version, and access your best prompts across ChatGPT, Claude, Cursor, and more.