Creates comprehensive Architecture Decision Records with options analysis, decision matrices, and consequence documentation.
You are a software architect who documents architectural decisions. Create an Architecture Decision Record for this decision. Decision needed: [WHAT ARCHITECTURE CHOICE] Context: [PROJECT BACKGROUND] Options considered: [LIST OPTIONS] Stakeholders: [WHO'S INVOLVED] Timeline: [DECISION DEADLINE] Create an ADR: ```markdown # ADR [NUMBER]: [TITLE] ## Status [Proposed | Accepted | Deprecated | Superseded by ADR-XXX] ## Date [YYYY-MM-DD] ## Context [Describe the issue motivating this decision, forces at play, including technological, political, social, and project local. What is the problem we're trying to solve?] ## Decision [Describe the decision and its rationale. Be specific about what we decided to do and why.] ## Options Considered ### Option 1: [Name] **Description:** [How it works] **Pros:** - Pro 1 - Pro 2 **Cons:** - Con 1 - Con 2 **Estimated Effort:** [T-shirt size or hours] ### Option 2: [Name] [Same structure...] ### Option 3: [Name] [Same structure...] ## Decision Matrix | Criterion | Weight | Option 1 | Option 2 | Option 3 | |-----------|--------|----------|----------|----------| | Performance | 3 | 3 (9) | 2 (6) | 3 (9) | | Maintainability | 2 | 2 (4) | 3 (6) | 2 (4) | | Cost | 2 | 3 (6) | 1 (2) | 2 (4) | | Team expertise | 1 | 2 (2) | 3 (3) | 1 (1) | | **Total** | | **21** | **17** | **18** | ## Consequences **Positive:** - [Good outcomes] **Negative:** - [Trade-offs accepted] **Risks:** - [Potential issues to monitor] ## Implementation Notes - [Key implementation considerations] - [Migration path if applicable] - [Dependencies] ## Related Decisions - [Links to related ADRs] ## References - [External resources, documentation] ```
You are a software architect who documents architectural decisions. Create an Architecture Decision Record for this decision. Decision needed: [WHAT ARCHITECTURE CHOICE] Context: [PROJECT BACKGROUND] Options considered: [LIST OPTIONS] Stakeholders: [WHO'S INVOLVED] Timeline: [DECISION DEADLINE] Create an ADR: ```markdown # ADR [NUMBER]: [TITLE] ## Status [Proposed | Accepted | Deprecated | Superseded by ADR-XXX] ## Date [YYYY-MM-DD] ## Context [Describe the issue motivating this decision, forces at play, including technological, political, social, and project local. What is the problem we're trying to solve?] ## Decision [Describe the decision and its rationale. Be specific about what we decided to do and why.] ## Options Considered ### Option 1: [Name] **Description:** [How it works] **Pros:** - Pro 1 - Pro 2 **Cons:** - Con 1 - Con 2 **Estimated Effort:** [T-shirt size or hours] ### Option 2: [Name] [Same structure...] ### Option 3: [Name] [Same structure...] ## Decision Matrix | Criterion | Weight | Option 1 | Option 2 | Option 3 | |-----------|--------|----------|----------|----------| | Performance | 3 | 3 (9) | 2 (6) | 3 (9) | | Maintainability | 2 | 2 (4) | 3 (6) | 2 (4) | | Cost | 2 | 3 (6) | 1 (2) | 2 (4) | | Team expertise | 1 | 2 (2) | 3 (3) | 1 (1) | | **Total** | | **21** | **17** | **18** | ## Consequences **Positive:** - [Good outcomes] **Negative:** - [Trade-offs accepted] **Risks:** - [Potential issues to monitor] ## Implementation Notes - [Key implementation considerations] - [Migration path if applicable] - [Dependencies] ## Related Decisions - [Links to related ADRs] ## References - [External resources, documentation] ```
This prompt is released under CC0 (Public Domain). You are free to use it for any purpose without attribution.
Explore similar prompts based on category and tags
Conducts thorough code reviews covering security, performance, maintainability, and best practices with specific fix suggestions.
Analyzes complex error stack traces to identify root causes and provide specific code fixes.
Identifies security vulnerabilities with fixes, OWASP analysis, and comprehensive hardening recommendations.
Designs complete authentication systems with multiple auth methods, security measures, and implementation code.