▸case-01 We are scaling a healthcare claims platform where audit trails are strict, business rules update monthly, and four dev teams constantly overwrite each other's domain concepts. Can you evaluate if we should commit to full Domain-Driven Design for this project? Please structure your response by detailing our scope and core assumptions, pointing out our current stage (whether strategic, tactical, or event-focused), listing the explicit artifacts produced, and outlining open risks along with next step recommendations. | fail→fail | 42,213 | 13,585 | -68% | 1 | 1 | 0% | 7,397 | 2,631 | -64% | 0 | 0 | — |
▸case-02 Our enterprise logistics platform suffers from high business rule complexity and fragile integration contracts across three engineering teams. We want to know if adopting DDD makes sense here and which architectural paths we should pursue. Ensure your answer includes our project scope and assumptions, defines our current stage in the process, lists all explicit artifacts produced, and details open risks with clear recommendations for our next steps. | fail→fail | 47,324 | 16,385 | -65% | 1 | 1 | 0% | 8,262 | 3,316 | -60% | 0 | 0 | — |
▸case-03 We are building an automated loan underwriting tool with strict audit requirements and frequent regulatory updates. I need an assessment on whether full DDD is justified and how to route our upcoming architecture work. In your response, explicitly state the scope and assumptions, identify the current stage, itemize the artifacts produced, and summarize open risks together with a recommended next step. | fail→pass | 27,539 | 14,527 | -47% | 1 | 1 | 0% | 4,368 | 2,923 | -33% | 0 | 0 | — |
▸case-04 Our single-team inventory tracker for Acme Corp updates item counts via basic REST endpoints. Rules rarely change and integration contracts are stable across our internal UI. A developer suggests adopting full Domain-Driven Design to future-proof the codebase. Evaluate whether full DDD is justified for this system, outlining scope and assumptions, stage, produced artifacts, and open risks. | fail→pass | 18,053 | 12,082 | -33% | 1 | 1 | 0% | 2,744 | 2,517 | -8% | 0 | 0 | — |
▸case-05 Apex Telecom runs a legacy billing platform where rate calculation rules change biweekly due to regional promotions, and two engineering teams frequently break each other's billing domain models. Should we commit to full Domain-Driven Design? Provide an assessment containing scope and assumptions, current stage, artifacts, and open risks. | fail→pass | 18,548 | 11,805 | -36% | 1 | 1 | 0% | 2,913 | 2,373 | -19% | 0 | 0 | — |
▸case-06 We are launching a new freight logistics domain service and developers want to start immediately by writing TypeScript aggregate classes and database entity schemas. What strategic artifacts must be produced first before diving into tactical code? Present your response with scope, current stage, artifacts, and next steps. | pass→pass | 16,530 | 13,208 | -20% | 1 | 1 | 0% | 2,458 | 2,672 | +9% | 0 | 0 | — |
▸case-07 Our team needs to integrate a modern payment service with a legacy AS400 billing system, requiring anti-corruption layers and translation maps between contexts. Which specialized domain skill should handle this integration mapping? Return an assessment with scope, current stage, artifacts, and next steps. | fail→pass | 15,500 | 10,702 | -31% | 1 | 1 | 0% | 2,376 | 2,248 | -5% | 0 | 0 | — |
▸case-08 We are implementing aggregate roots, entities, and value objects in C# for our warehouse fulfillment context. Which specialized skill should guide this object-level domain structure? Provide scope, current stage, artifacts, and next step recommendations. | fail→pass | 15,264 | 9,342 | -39% | 1 | 1 | 0% | 2,400 | 2,075 | -14% | 0 | 0 | — |
▸case-09 Our ecommerce platform is bottlenecked because complex search queries lock database tables during heavy checkout writes. We want to separate read models from write models. Which architectural routing handle targets this separation? Include scope, stage, artifacts, and open risks. | fail→pass | 13,971 | 9,413 | -33% | 1 | 1 | 0% | 2,290 | 2,114 | -8% | 0 | 0 | — |
▸case-10 For our financial ledger microservice, regulatory compliance requires keeping an immutable history of every domain state change as the ultimate source of truth. Which specialized skill routing handles should we use? Provide scope, current stage, artifacts, and next steps. | fail→fail | 14,183 | 13,334 | -6% | 1 | 1 | 0% | 2,274 | 2,764 | +22% | 0 | 0 | — |
▸case-11 Our travel booking app needs to coordinate multi-step long-running business workflows across flight reservation, hotel booking, and car rental microservices. Which specialized skill handle orchestrates this multi-context workflow? Output scope, stage, artifacts, and next step. | fail→pass | 8,291 | 7,338 | -11% | 1 | 1 | 0% | 1,267 | 1,777 | +40% | 0 | 0 | — |
▸case-12 We have an event-sourced order context and need to construct optimized denormalized view tables for the customer dashboard. Which domain skill handle governs building read projections? Include scope, current stage, artifacts, and recommendations. | fail→pass | 18,548 | 9,142 | -51% | 1 | 1 | 0% | 2,881 | 2,082 | -28% | 0 | 0 | — |
▸case-13 We need to document our domain boundary trade-offs, aggregate choices, and technical trade-offs for future team members. Which skill handle governs recording these architectural decisions? Provide scope, current stage, explicit artifacts, and next step. | pass→pass | 9,221 | 7,127 | -23% | 1 | 1 | 0% | 1,433 | 1,735 | +21% | 0 | 0 | — |
▸case-14 We are currently mapping subdomains, negotiating Ubiquitous Language terms, and defining bounded context boundaries for a health insurance portal. How should our current project stage be explicitly classified? Structure response with scope, stage classification, artifacts, and next steps. | pass→pass | 12,359 | 10,212 | -17% | 1 | 1 | 0% | 1,973 | 2,110 | +7% | 0 | 0 | — |
▸case-15 Our dev team is writing domain entity invariant logic, value object validation, and domain event dispatchers inside the Order Bounded Context. What is our current project stage? Provide scope, stage classification, artifacts, and open risks. | pass→pass | 14,211 | 10,701 | -25% | 1 | 1 | 0% | 2,210 | 2,197 | -1% | 0 | 0 | — |
▸case-16 We are configuring event store retention policies, constructing read projections, and building saga state machines for payment processing. Identify our current stage classification and outline scope, stage, artifacts, and recommendations. | pass→pass | 16,199 | 13,687 | -16% | 1 | 1 | 0% | 2,413 | 2,590 | +7% | 0 | 0 | — |
▸case-17 We are establishing governance for our new core banking domain design process. What requirement must be specified for each stage of the domain-driven design transition? Include scope, current stage, artifacts, and open risks in your answer. | pass→pass | 17,729 | 12,548 | -29% | 1 | 1 | 0% | 2,892 | 2,524 | -13% | 0 | 0 | — |
▸case-18 Evaluate if our mobile app's push notification preference system should adopt full DDD, given that two teams manage conflicting preference rules and integration contracts with external gateways change monthly. Ensure your response includes all standard output sections. | fail→pass | 24,136 | 10,905 | -55% | 1 | 1 | 0% | 3,832 | 2,345 | -39% | 0 | 0 | — |
▸case-19 A developer wants to apply full DDD to an internal employee directory service because the integration contract with our HR software changes twice a year. However, rules are trivial, only one team maintains it, and strict audit logs are not needed. Perform a viability check and provide scope, stage, artifacts, and next steps. | fail→pass | 15,028 | 9,419 | -37% | 1 | 1 | 0% | 2,367 | 2,208 | -7% | 0 | 0 | — |
▸case-20 We are building an admin CRUD panel to view and update internal employee office location badges (room number, desk ID) with standard REST forms. No complex business logic or multi-team collisions exist. Provide architectural guidelines for implementing this service. | pass→pass | 17,391 | 11,355 | -35% | 1 | 1 | 0% | 3,129 | 2,423 | -23% | 0 | 0 | — |
▸case-21 We found a null reference error in the function calculateSalesTax() inside our checkout service repository. Provide the steps to fix this bug. | pass→pass | 13,716 | 12,319 | -10% | 1 | 1 | 0% | 2,495 | 2,589 | +4% | 0 | 0 | — |
▸case-22 Our outsourced dev team wants to build a complex actuarial modeling platform for crop insurance. However, we have no access to domain experts or product proxies, and nobody on the team understands insurance math. Should we perform DDD strategic domain modeling now? | pass→pass | 14,730 | 7,871 | -47% | 1 | 1 | 0% | 2,270 | 1,798 | -21% | 0 | 0 | — |
▸case-23 Our enterprise retail platform needs to split its monolithic schema into core subdomains and define clear boundary boundaries between inventory, ordering, and customer management. Which specialized handle should lead this boundary definition? Structure your answer with scope, current stage, artifacts, and next steps. | fail→pass | 14,480 | 11,494 | -21% | 1 | 1 | 0% | 2,169 | 2,476 | +14% | 0 | 0 | — |