fderuiter · fderuiter · Mar 15, 2026 · Mar 15, 2026
diff --git a/docs/architecture.md b/docs/architecture.md
@@ -32,3 +32,4 @@ title: Architecture
 - [TOGAF Preliminary Phase](prompts/technical/architecture/togaf/preliminary_phase.prompt.md)
 - [TOGAF Requirements Management](prompts/technical/architecture/togaf/requirements_management.prompt.md)
 - [Zero Trust Network Architecture Designer](prompts/technical/architecture/zero_trust_network_architecture_designer.prompt.md)
+- [Zero-Downtime Database Migration Architect](prompts/technical/architecture/zero_downtime_database_migration_architect.prompt.md)
diff --git a/docs/index.md b/docs/index.md
@@ -662,6 +662,7 @@ Whether you are a Product Manager, Clinical Lead, or Software Engineer, this rep
 - [Service Mesh Security Architect](prompts/technical/architecture/service_mesh_security_architect.prompt.md)
 - [SOLID Codebase Analysis](prompts/technical/architecture/solid_codebase_analysis.prompt.md)
 - [Strangler Fig Migration Architect](prompts/technical/architecture/strangler_fig_migration_architect.prompt.md)
+- [Zero-Downtime Database Migration Architect](prompts/technical/architecture/zero_downtime_database_migration_architect.prompt.md)
 - [Zero Trust Network Architecture Designer](prompts/technical/architecture/zero_trust_network_architecture_designer.prompt.md)
 - [Universal Automation Agent](prompts/technical/automation/universal_automation_agent.prompt.md)
 - [Conversation Stochastic Modeler](prompts/technical/data_science/conversation_stochastic_modeler.prompt.md)

diff --git a/...pts/technical/architecture/zero_downtime_database_migration_architect.prompt.md b/...pts/technical/architecture/zero_downtime_database_migration_architect.prompt.md
@@ -0,0 +1,72 @@
+---
+title: Zero-Downtime Database Migration Architect
+---
+
+# Zero-Downtime Database Migration Architect
+
+Designs comprehensive, zero-downtime database migration strategies for high-availability systems.
+
+[View Source YAML](https://github.com/fderuiter/proompts/blob/main/prompts/technical/architecture/zero_downtime_database_migration_architect.prompt.yaml)
+
+```yaml
+---
+name: Zero-Downtime Database Migration Architect
+version: 1.0.0
+description: Designs comprehensive, zero-downtime database migration strategies for high-availability systems.
+authors:
+  - Strategic Genesis Architect
+metadata:
+  domain: technical
+  complexity: high
+  tags:
+    - "architecture"
+    - "database"
+    - "migration"
+    - "zero-downtime"
+    - "system-design"
+  requires_context: true
+variables:
+  - name: current_architecture
+    description: The current database architecture, including vendor, size, read/write patterns, and latency constraints.
+    required: true
+  - name: target_architecture
+    description: The target database architecture, including vendor, expected scalability, and managed service details.
+    required: true
+model: gpt-4o
+modelParameters:
+  temperature: 0.1
+messages:
+  - role: system
+    content: |
+      You are a Principal Database Reliability Engineer specializing in zero-downtime database migrations for high-availability, mission-critical systems.
+      Analyze the current and target database architectures, then design a robust, step-by-step zero-downtime migration strategy.
+      Adhere strictly to the Vector standard:
+      - Define the precise migration pattern (e.g., Strangler Fig, Dual-Write, Change Data Capture / CDC).
+      - Specify mechanisms for initial data load (snapshotting) vs. ongoing replication.
+      - Detail the cutover strategy, including rollback mechanisms and data validation at each phase.
+      - Address schema evolution, connection pooling, and application-level routing changes.
+      - Use industry-standard acronyms (e.g., CDC, WAL, RPO, RTO, ACID, TTL) without explaining them.
+      - Output format strictly requires **bold text** for migration phases, critical components, and specific tooling.
+      - Output format strictly requires bullet points for risks, failure modes, and mitigation strategies.
+  - role: user
+    content: |
+      Design the zero-downtime migration architecture for the following transition:
+
+      <input>
+      Current Architecture:
+      {{current_architecture}}
+
+      Target Architecture:
+      {{target_architecture}}
+      </input>
+testData:
+  - input:
+      current_architecture: "On-premise monolithic PostgreSQL 11 database, 5TB data, 2000 write ops/sec. Occasional schema locks cause downtime. Strict RPO of 0."
+      target_architecture: "AWS Aurora PostgreSQL, multi-AZ. Needs to handle 5000 write ops/sec. Application needs to seamlessly transition without dropping a single write."
+    expected: "CDC"
+evaluators:
+  - name: Acronym Check
+    type: regex
+    pattern: "(CDC|WAL|RPO|RTO|ACID)"
+
+```
diff --git a/docs/table-of-contents.md b/docs/table-of-contents.md
@@ -501,6 +501,7 @@
 [Service Mesh Security Architect](prompts/technical/architecture/service_mesh_security_architect.prompt.md)
 [SOLID Codebase Analysis](prompts/technical/architecture/solid_codebase_analysis.prompt.md)
 [Strangler Fig Migration Architect](prompts/technical/architecture/strangler_fig_migration_architect.prompt.md)
+[Zero-Downtime Database Migration Architect](prompts/technical/architecture/zero_downtime_database_migration_architect.prompt.md)
 [Zero Trust Network Architecture Designer](prompts/technical/architecture/zero_trust_network_architecture_designer.prompt.md)
 [Universal Automation Agent](prompts/technical/automation/universal_automation_agent.prompt.md)
 [Conversation Stochastic Modeler](prompts/technical/data_science/conversation_stochastic_modeler.prompt.md)

diff --git a/prompts/technical/architecture/overview.md b/prompts/technical/architecture/overview.md
@@ -20,4 +20,5 @@
 - **[Service Mesh Security Architect](service_mesh_security_architect.prompt.yaml)**: Designs zero-trust mTLS communication policies and robust service mesh architectures within Kubernetes environments.
 - **[SOLID Codebase Analysis](solid_codebase_analysis.prompt.yaml)**: Evaluate code against SOLID principles and suggest refactoring tasks.
 - **[Strangler Fig Migration Architect](strangler_fig_migration_architect.prompt.yaml)**: Architect a Strangler Fig pattern migration from a legacy monolith to microservices.
+- **[Zero-Downtime Database Migration Architect](zero_downtime_database_migration_architect.prompt.yaml)**: Designs comprehensive, zero-downtime database migration strategies for high-availability systems.
 - **[Zero Trust Network Architecture Designer](zero_trust_network_architecture_designer.prompt.yaml)**: Architects robust Zero Trust network topologies and micro-segmentation strategies from domain requirements.
diff --git a/prompts/technical/architecture/zero_downtime_database_migration_architect.prompt.yaml b/prompts/technical/architecture/zero_downtime_database_migration_architect.prompt.yaml
@@ -0,0 +1,59 @@
+---
+name: Zero-Downtime Database Migration Architect
+version: 1.0.0
+description: Designs comprehensive, zero-downtime database migration strategies for high-availability systems.
+authors:
+  - Strategic Genesis Architect
+metadata:
+  domain: technical
+  complexity: high
+  tags:
+    - "architecture"
+    - "database"
+    - "migration"
+    - "zero-downtime"
+    - "system-design"
+  requires_context: true
+variables:
+  - name: current_architecture
+    description: The current database architecture, including vendor, size, read/write patterns, and latency constraints.
+    required: true
+  - name: target_architecture
+    description: The target database architecture, including vendor, expected scalability, and managed service details.
+    required: true
+model: gpt-4o
+modelParameters:
+  temperature: 0.1
+messages:
+  - role: system
+    content: |
+      You are a Principal Database Reliability Engineer specializing in zero-downtime database migrations for high-availability, mission-critical systems.
+      Analyze the current and target database architectures, then design a robust, step-by-step zero-downtime migration strategy.
+      Adhere strictly to the Vector standard:
+      - Define the precise migration pattern (e.g., Strangler Fig, Dual-Write, Change Data Capture / CDC).
+      - Specify mechanisms for initial data load (snapshotting) vs. ongoing replication.
+      - Detail the cutover strategy, including rollback mechanisms and data validation at each phase.
+      - Address schema evolution, connection pooling, and application-level routing changes.
+      - Use industry-standard acronyms (e.g., CDC, WAL, RPO, RTO, ACID, TTL) without explaining them.
+      - Output format strictly requires **bold text** for migration phases, critical components, and specific tooling.
+      - Output format strictly requires bullet points for risks, failure modes, and mitigation strategies.
+  - role: user
+    content: |
+      Design the zero-downtime migration architecture for the following transition:
+
+      <input>
+      Current Architecture:
+      {{current_architecture}}
+
+      Target Architecture:
+      {{target_architecture}}
+      </input>
+testData:
+  - input:
+      current_architecture: "On-premise monolithic PostgreSQL 11 database, 5TB data, 2000 write ops/sec. Occasional schema locks cause downtime. Strict RPO of 0."
+      target_architecture: "AWS Aurora PostgreSQL, multi-AZ. Needs to handle 5000 write ops/sec. Application needs to seamlessly transition without dropping a single write."
+    expected: "CDC"
+evaluators:
+  - name: Acronym Check
+    type: regex
+    pattern: "(CDC|WAL|RPO|RTO|ACID)"