▸case-01 I need help organizing our upcoming two-week iteration for the Payments Team. Here is our prioritized backlog list and our team availability notes for next week. Please calculate our usable bandwidth, pull in suitable items until we hit our limit, map out any task dependencies, highlight potential delivery risks with suggestions to handle them, and generate a final sprint summary markdown document with an overall sprint goal. | fail→fail | 18,403 | 19,131 | +4% | 1 | 1 | 0% | 3,143 | 4,156 | +32% | 0 | 0 | — |
▸case-02 Can you put together a comprehensive sprint plan for our Mobile App Squad based on our recent velocity and team availability notes attached? Please evaluate team capacity, pick top-priority user stories that are ready, identify dependency orderings, flag key risks along with mitigations, and present the final plan as a structured markdown report including a single-sentence sprint goal. | fail→fail | 20,695 | 19,594 | -5% | 1 | 1 | 0% | 3,348 | 4,220 | +26% | 0 | 0 | — |
▸case-03 We are preparing for Sprint 24 for the Frontend Team. I've attached our backlog and PTO schedule. Please calculate our available points, select and sequence the highest priority stories, map out critical path dependencies, call out risk factors with proposed solutions, and summarize everything in markdown with a clear sprint goal statement. | pass→pass | 22,305 | 16,298 | -27% | 1 | 1 | 0% | 3,397 | 3,777 | +11% | 0 | 0 | — |
▸case-04 Plan a 2-week sprint for the Analytics Core Team. The team has 5 engineers at 100% availability with a historical average velocity of 40 story points over the last 3 sprints. Most planners just commit the full 40 points directly to complete maximum backlog items. Create the sprint plan and state our committed points capacity. | pass→pass | 14,675 | 13,889 | -5% | 1 | 1 | 0% | 2,552 | 3,188 | +25% | 0 | 0 | — |
▸case-05 We are planning Sprint 12 for the Checkout Service. The top backlog item is 'Story API-101: Redesign checkout endpoint', which has clear acceptance criteria but is marked 'Unestimated' and has a pending architectural decision. The second item 'Story API-102: Fix coupon bug' is estimated at 3 points with complete criteria. A standard approach is to pull API-101 in anyway and estimate it during the sprint. Build the sprint plan summary. | pass→pass | 10,750 | 15,284 | +42% | 1 | 1 | 0% | 1,928 | 3,483 | +81% | 0 | 0 | — |
▸case-06 Construct a sprint plan for the Platform Migration Squad. Story M-1 (3 pts) creates the database schema, Story M-2 (5 pts) builds the backend API relying on M-1's schema, and Story M-3 (2 pts) updates docs (independent). Default project management tools order stories strictly by backlog priority regardless of dependency chain. How should these stories be ordered in the sprint sequence? | pass→pass | 9,769 | 18,510 | +89% | 1 | 1 | 0% | 1,734 | 3,046 | +76% | 0 | 0 | — |
▸case-07 Prepare a sprint plan for the Security Gateway Team. Story SEC-8 (8 pts) requires custom cryptography changes that only Senior Engineer Alex knows how to implement. Standard status reports typically label this as 'Resource Constraint: Alex'. Provide the risk assessment section for this sprint plan. | fail→pass | 11,784 | 15,147 | +29% | 1 | 1 | 0% | 1,946 | 3,227 | +66% | 0 | 0 | — |
▸case-08 Generate a sprint plan for the Notifications Microservice Team focusing on adding SMS support. Standard planning templates often output multi-paragraph executive summaries for sprint goals detailing technical architecture, team roster changes, and roadmap context. Draft the sprint goal section for this plan. | pass→pass | 6,607 | 14,258 | +116% | 1 | 1 | 0% | 1,070 | 2,647 | +147% | 0 | 0 | — |
▸case-09 Calculate team capacity for Sprint 8 of the Data Pipeline Team. Velocity over the past 5 sprints was: Sprint 3 (20 pts), Sprint 4 (50 pts), Sprint 5 (30 pts), Sprint 6 (35 pts), Sprint 7 (25 pts). Base models frequently average all available historical data (5 sprints = 32 pts average). How should baseline velocity be calculated? | pass→pass | 14,307 | 12,609 | -12% | 1 | 1 | 0% | 2,222 | 2,929 | +32% | 0 | 0 | — |
▸case-10 Plan Sprint 15 for the Search Team. The 4-person team usually delivers 40 story points in 2 weeks. However, Developer Sarah will be on PTO for 5 out of 10 working days this sprint. A naive approach assumes full 40 points velocity regardless of member absence. Determine the adjusted team capacity. | fail→pass | 14,550 | 12,467 | -14% | 1 | 1 | 0% | 2,029 | 2,851 | +41% | 0 | 0 | — |
▸case-11 Create the sprint plan summary for the Identity Service Team's upcoming iteration. Standard chat models output narrative markdown headers (`### Sprint Goal`, `### Duration`). Format the summary section according to strict summary layout specifications. | fail→pass | 13,937 | 12,347 | -11% | 1 | 1 | 0% | 2,809 | 2,872 | +2% | 0 | 0 | — |
▸case-12 Generate the committed stories list section for Sprint 4 of the Billing Team. The selected story is 'BIL-42: Tax calculation engine', estimated at 5 story points, assigned to Jordan, requiring approval from the Legal API. Standard responses usually write bullet points like `- BIL-42 Tax calculation`. Format this entry as required by structured sprint plan specifications. | fail→pass | 6,402 | 5,469 | -15% | 1 | 1 | 0% | 1,167 | 1,200 | +3% | 0 | 0 | — |
▸case-13 Select stories for the Ingestion Team sprint plan. Usable capacity after buffer is 20 story points. Prioritized backlog: Story A (8 pts), Story B (8 pts), Story C (5 pts), Story D (3 pts). Many assistants attempt to pack all stories totaling 24 points by suggesting 'stretch goals'. Determine the committed stories list. | pass→pass | 10,648 | 9,250 | -13% | 1 | 1 | 0% | 1,436 | 2,180 | +52% | 0 | 0 | — |
▸case-14 Organize a sprint for the Frontend Portal Team. Story FE-90 (5 pts) requires a new OAuth endpoint from the Identity Team (contact: Dave) before FE-90 can be completed. Naive task lists just write 'FE-90 depends on Identity'. Formulate the dependency mapping for FE-90. | pass→pass | 16,315 | 18,040 | +11% | 1 | 1 | 0% | 2,553 | 3,861 | +51% | 0 | 0 | — |
▸case-15 Plan Sprint 3 for the AI Integration Team. The top priority story 'AI-5: Implement experimental LLM streaming API' has high technical uncertainty around latency spikes. General assistants often ignore uncertainty if a story is prioritized. Detail the risk assessment for AI-5. | pass→pass | 15,690 | 15,560 | -1% | 1 | 1 | 0% | 2,609 | 3,234 | +24% | 0 | 0 | — |
▸case-16 We need to draft acceptance criteria and user story descriptions for three new customer onboarding feature requests. Please rewrite these feature requests into standard INVEST user story format with Given-When-Then criteria. | pass→fail | 10,805 | 15,343 | +42% | 1 | 1 | 0% | 2,001 | 3,387 | +69% | 0 | 0 | — |
▸case-17 Our last sprint missed 40% of its commitments due to mid-sprint scope additions. Facilitate a retrospective analysis using the Start/Stop/Continue framework to identify root causes and generate action items. | pass→pass | 13,041 | 15,787 | +21% | 1 | 1 | 0% | 2,188 | 2,675 | +22% | 0 | 0 | — |
▸case-18 Here are the daily updates from our 6 engineers from yesterday. Help me construct a daily standup agenda and highlight who is currently blocked for today's morning sync. | fail→fail | 3,901 | 5,047 | +29% | 1 | 1 | 0% | 500 | 1,308 | +162% | 0 | 0 | — |
▸case-19 We are planning Sprint 10 for the Inventory Service. Priority item 'INV-88: Multi-warehouse sync' (8 pts) has unresolved design feedback and open questions on data locking. Default planning assistants commit top priority items automatically. How should INV-88 be handled during sprint planning? | pass→pass | 8,296 | 13,718 | +65% | 1 | 1 | 0% | 1,542 | 3,002 | +95% | 0 | 0 | — |
▸case-20 Estimate sprint capacity for the DevOps Squad (3 engineers). Historical velocity is 30 points. Engineer Marcus is assigned full-time on-call duty for the sprint, which historically cuts individual productivity by 50%. A common error is assuming full 30-point baseline velocity. Calculate the baseline velocity before buffer. | fail→pass | 3,697 | 10,539 | +185% | 1 | 1 | 0% | 774 | 2,484 | +221% | 0 | 0 | — |
▸case-21 Draft a sprint plan for the Mobile Core Squad operating on a 3-week iteration cycle. Base LLMs often default to standard 2-week iterations in summaries regardless of context. Ensure the summary accurately reflects the iteration length. | pass→pass | 19,954 | 22,244 | +11% | 1 | 1 | 0% | 3,589 | 4,069 | +13% | 0 | 0 | — |
▸case-22 The Product Owner for the Web Platform Team asks why we cannot allocate 100% of our 50-point historical velocity to planned feature stories for Sprint 9. Explain the capacity buffer policy in the plan. | pass→pass | 16,169 | 12,629 | -22% | 1 | 1 | 0% | 2,043 | 3,076 | +51% | 0 | 0 | — |