▸case-01 We just finished reviewing the database migration project. Can you go through the closeout artifacts and compile a post-project review? Make sure process improvements and software defects are categorized separately so future teams can benefit. | pass→fail | 13,011 | 8,138 | -37% | 1 | 1 | 0% | 2,089 | 1,308 | -37% | 0 | 0 | — |
▸case-02 Here are the raw notes from our auth-service refactor mission closeout: we had a token validation null pointer bug, CI pipeline runner timeouts, a race condition in session revocation, and poor PR review turnaround times. Put all of these into one unified list of issues encountered. | fail→pass | 3,494 | 4,143 | +19% | 1 | 1 | 0% | 558 | 825 | +48% | 0 | 0 | — |
▸case-03 We merged the payment gateway integration. Here is the git commit log showing 14 commits across 8 files modifying API endpoints and payload serializers. Please produce the post-mission retrospective based on this. | fail→fail | 6,340 | 6,900 | +9% | 1 | 1 | 0% | 977 | 1,237 | +27% | 0 | 0 | — |
▸case-04 For our Terraform EKS rollout mission review, team members logged two items: an AMI provisioner panic error in the code, and a lack of clear staging environment access permissions that delayed testing for 3 days. Prepare the retrospective summary, combining both into a single bug tracker summary format. | pass→pass | 10,894 | 7,329 | -33% | 1 | 1 | 0% | 1,810 | 1,246 | -31% | 0 | 0 | — |
▸case-05 Our Kubernetes cluster upgrade mission just finished. Can you generate the retrospective right now without looking up any review notes or closeout documents? | fail→pass | 10,850 | 4,038 | -63% | 1 | 1 | 0% | 1,685 | 722 | -57% | 0 | 0 | — |
▸case-06 In our GraphQL API mission closeout notes, developers mentioned needing automated schema breaking-change detection in CI and rewriting schema docs. The PR diff showed 50 schema file edits. Create a retrospective summary focusing on what matters for future missions. | pass→pass | 11,760 | 6,166 | -48% | 1 | 1 | 0% | 1,821 | 1,037 | -43% | 0 | 0 | — |
▸case-07 During the telemetry collection mission, the team faced recurring delays waiting for security compliance sign-off on every PR, along with a memory leak in the metrics exporter daemon. Summarize these learnings. | fail→pass | 7,804 | 4,779 | -39% | 1 | 1 | 0% | 1,343 | 809 | -40% | 0 | 0 | — |
▸case-08 I just merged feature branch `feat/oauth-pkce`. Please write a standard pull request description summarizing the technical changes made in the code diff for the repository's main README and PR body. | pass→pass | 21,965 | 7,285 | -67% | 1 | 1 | 0% | 2,181 | 1,276 | -41% | 0 | 0 | — |
▸case-09 Our production billing database went down for 45 minutes due to an unindexed query lock during peak load. Please generate an Incident Root Cause Analysis (RCA) document with a timeline, technical root cause, and immediate remediation steps. | pass→pass | 20,292 | 11,701 | -42% | 1 | 1 | 0% | 3,327 | 1,805 | -46% | 0 | 0 | — |
▸case-10 We are mid-sprint in the search-indexing project. Please review these 5 candidate user stories for search filtering and estimate story points while checking acceptance criteria completeness. | pass→pass | 5,250 | 3,629 | -31% | 1 | 1 | 0% | 797 | 714 | -10% | 0 | 0 | — |
▸case-11 Our Spark ETL pipeline mission notes list two main points: PySpark workers OOM killed on large datasets, and complete lack of documentation on local testing setup causing every onboarding dev to waste 2 days. Draft the retrospective summary. | fail→fail | 8,695 | 8,093 | -7% | 1 | 1 | 0% | 1,408 | 1,250 | -11% | 0 | 0 | — |
▸case-12 The design system migration project closeout notes mention: CSS z-index bleeding on mobile dropdowns, and designers not being tagged early enough in PR reviews leading to last-minute UI re-works. Please summarize. | fail→pass | 3,986 | 5,374 | +35% | 1 | 1 | 0% | 591 | 871 | +47% | 0 | 0 | — |
▸case-13 Here is the list of 25 commits merged for the search relevance tuning mission. Summarize what was learned and what future teams should do. | fail→fail | 5,089 | 4,101 | -19% | 1 | 1 | 0% | 805 | 773 | -4% | 0 | 0 | — |
▸case-14 We wrapped up the microservice split for billing. I remember developers complained about slow local docker builds. Can you finish the mission retrospective now based on just that sentence? | fail→fail | 9,555 | 6,059 | -37% | 1 | 1 | 0% | 1,528 | 1,102 | -28% | 0 | 0 | — |
▸case-15 Our engineering organization uses a standardized retrospective template tool in Jira for mission closeouts. How should we initiate the retro for our logging platform migration? | pass→pass | 16,240 | 7,594 | -53% | 1 | 1 | 0% | 2,283 | 1,216 | -47% | 0 | 0 | — |
▸case-16 API gateway migration notes: Envoy proxy route matching bug on wildcard paths, and rate limits on third-party test keys blocking automated integration tests every afternoon. Please organize these feedback items. | pass→pass | 9,141 | 4,284 | -53% | 1 | 1 | 0% | 1,572 | 765 | -51% | 0 | 0 | — |
▸case-17 I drafted this retrospective draft for our Redis caching layer mission: 'We changed 12 files in cache/redis.go, added 3 helper functions, updated 4 unit tests, and bumped redis driver to v8.' Evaluate this draft. | fail→pass | 10,151 | 6,191 | -39% | 1 | 1 | 0% | 1,704 | 1,055 | -38% | 0 | 0 | — |
▸case-18 During the iOS release mission, apple store review rejections due to missing privacy manifest keys happened twice, and Xcode build cache invalidation added 40 minutes to every CI run. Create the retro summary. | pass→pass | 12,328 | 6,699 | -46% | 1 | 1 | 0% | 1,919 | 1,222 | -36% | 0 | 0 | — |
▸case-19 We completed the SOC2 security remediation mission. Should the retrospective focus on detailed lines of code modified in the crypto utils or on how to streamline compliance review workflows for future missions? | pass→pass | 11,020 | 4,720 | -57% | 1 | 1 | 0% | 1,505 | 789 | -48% | 0 | 0 | — |
▸case-20 Database sharding mission notes: SQL syntax error in custom router for multi-tenant queries, missing staging DB backup before performance test, and flaky integration test runner. Group these feedback items. | pass→pass | 4,539 | 5,576 | +23% | 1 | 1 | 0% | 766 | 1,008 | +32% | 0 | 0 | — |
▸case-21 We merged the last PR for the cloud migration mission 10 minutes ago. What is the immediate first step for compiling the mission retrospective? | fail→pass | 7,969 | 2,545 | -68% | 1 | 1 | 0% | 1,177 | 498 | -58% | 0 | 0 | — |
▸case-22 Closeout items from notification service mission: APNS payload truncation bug when message exceeds 2KB, and lack of clear ownership on who updates notification template schemas. Structure these into the retrospective. | pass→pass | 11,666 | 5,087 | -56% | 1 | 1 | 0% | 1,838 | 872 | -53% | 0 | 0 | — |
▸case-23 The observability mission completed. Artifacts note: need automated alert threshold tuning script, and runbook for memory alerts needs updating. How should this be represented in the retrospective? | pass→pass | 7,917 | 5,313 | -33% | 1 | 1 | 0% | 1,349 | 998 | -26% | 0 | 0 | — |