▸case-01 I need to draft a formal issue specification for adding user profile export functionality. Please outline the requirements clearly, ask me about any ambiguities, and stage the resulting document in git. | fail→fail | 14,278 | 5,344 | -63% | 1 | 1 | 0% | 2,355 | 275 | -88% | 0 | 0 | — |
▸case-07 Draft an issue specification for direct-to-S3 file uploads using presigned URLs. Max file size and allowed MIME types are currently unspecified. Don't ask me questions about them, just generate a response in chat. | fail→fail | 11,424 | 11,340 | -1% | 1 | 1 | 0% | 2,023 | 1,894 | -6% | 0 | 0 | — |
▸case-02 Please prepare an issue specification for implementing dark mode in the web app. Gather any missing details from me if things are under-specified, and stage the file in git. | fail→fail | 15,283 | 4,838 | -68% | 1 | 1 | 0% | 1,893 | 232 | -88% | 0 | 0 | — |
▸case-03 I need to create an issue spec for integrating Okta OAuth2 Single Sign-On into our dashboard app. Some details like token renewal and user role mappings are ambiguous, but feel free to just guess them so we don't waste time with questions, and print the spec in chat. | fail→fail | 14,392 | 14,575 | +1% | 1 | 1 | 0% | 2,599 | 2,474 | -5% | 0 | 0 | — |
▸case-04 Draft an issue spec for handling Stripe webhook events for subscription renewals and cancellations. I haven't specified retry behavior or failure notifications, so just write a quick text summary here in the chat without staging anything in git. | fail→fail | 20,915 | 7,676 | -63% | 1 | 1 | 0% | 1,752 | 1,310 | -25% | 0 | 0 | — |
▸case-05 Write an issue specification for indexing catalog items into Elasticsearch. I left out details on index refresh intervals and field mappings—make your own assumptions and write the spec directly into chat without git operations. | fail→fail | 12,635 | 10,884 | -14% | 1 | 1 | 0% | 2,266 | 2,018 | -11% | 0 | 0 | — |
▸case-06 Create an issue spec for implementing an IP-based rate limiter using Redis. I haven't decided on the rate limits per minute or key expiration strategies. Just pick standard defaults and output a response without staging files. | fail→fail | 11,000 | 14,293 | +30% | 1 | 1 | 0% | 1,815 | 2,510 | +38% | 0 | 0 | — |
▸case-08 Prepare an issue spec for a database audit logging system tracking user data modifications. Storage retention periods and log format details are undecided; just write out what you think best in chat and don't stage anything. | fail→fail | 14,854 | 12,591 | -15% | 1 | 1 | 0% | 2,443 | 2,214 | -9% | 0 | 0 | — |
▸case-09 Create an issue spec for adding multi-language i18n support to the React frontend. Fallback locale and dynamic translation loading mechanisms are unspecified. Produce the spec without asking clarifying questions or touching git. | fail→fail | 23,073 | 13,449 | -42% | 1 | 1 | 0% | 2,087 | 2,173 | +4% | 0 | 0 | — |
▸case-10 Draft an issue spec for adding TOTP-based two-factor authentication to user logins. Details around backup recovery codes and grace periods are omitted; just assume defaults and output text without git staging. | fail→fail | 16,095 | 10,810 | -33% | 1 | 1 | 0% | 2,830 | 1,894 | -33% | 0 | 0 | — |
▸case-11 Prepare an issue specification for a background CSV data import worker. Row validation failure handling and batch processing size are under-specified. Skip asking me questions and just write the spec into chat. | fail→fail | 14,370 | 14,441 | +0% | 1 | 1 | 0% | 2,380 | 2,246 | -6% | 0 | 0 | — |
▸case-12 Draft an issue spec for real-time WebSocket push notifications for user mentions. Heartbeat intervals and reconnection strategies are under-specified. Output the response in chat without staging in git. | fail→fail | 10,925 | 8,556 | -22% | 1 | 1 | 0% | 1,762 | 1,548 | -12% | 0 | 0 | — |
▸case-13 Write an issue specification for a PDF report generation background service using HTML templates. Page pagination limits and header customization details are not provided. Make assumptions rather than asking questions, and don't stage files. | fail→fail | 16,278 | 11,708 | -28% | 1 | 1 | 0% | 2,684 | 1,952 | -27% | 0 | 0 | — |
▸case-14 Create an issue spec for adding role-based access control middleware to our Express API. Inherited permission structures and superadmin overrides are ambiguous. Just produce the text and skip git staging. | fail→fail | 8,957 | 7,463 | -17% | 1 | 1 | 0% | 1,313 | 1,311 | -0% | 0 | 0 | — |
▸case-15 Draft an issue specification for an automated PostgreSQL database schema migration runner. Rollback strategy and lock timeout parameters are under-specified. Do not ask clarifying questions; just give me a chat response. | fail→fail | 11,089 | 17,786 | +60% | 1 | 1 | 0% | 1,705 | 1,843 | +8% | 0 | 0 | — |
▸case-16 Prepare an issue spec for migrating legacy REST endpoints for customer orders to GraphQL queries and mutations. Rate limit adjustments and query depth limits are undecided. Provide a plain chat summary without staging in git. | fail→fail | 10,824 | 9,677 | -11% | 1 | 1 | 0% | 1,797 | 1,649 | -8% | 0 | 0 | — |
▸case-17 Write an issue spec for implementing JWT session management with short-lived access tokens and refresh tokens. Refresh token revocation mechanisms are under-specified. Write the response in chat without asking questions or staging in git. | fail→fail | 15,005 | 13,109 | -13% | 1 | 1 | 0% | 2,522 | 2,395 | -5% | 0 | 0 | — |
▸case-18 Draft an issue specification for adding soft deletes and automated quarterly purging to our MongoDB user collections. Permanent deletion criteria and restoration window parameters are unspecified. Just list requirements without asking questions or staging git files. | fail→fail | 9,778 | 10,567 | +8% | 1 | 1 | 0% | 1,633 | 1,981 | +21% | 0 | 0 | — |
▸case-19 Prepare an issue spec for a transactional email rendering service using Handlebars templates. Unsubscribe headers and localized template resolution order are ambiguous. Avoid asking questions and do not stage anything in git. | fail→fail | 13,285 | 11,653 | -12% | 1 | 1 | 0% | 2,483 | 2,043 | -18% | 0 | 0 | — |
▸case-20 Here are three existing product backlog tickets: T-101 (Mobile Push Notifications), T-102 (SQL Query Optimization), and T-103 (Dark Theme). Please calculate RICE scores for each based on Reach, Impact, Confidence, and Effort, and rank them. | pass→fail | 11,988 | 9,871 | -18% | 1 | 1 | 0% | 2,491 | 2,049 | -18% | 0 | 0 | — |
▸case-21 Our engineering team uses Fibonacci story point scales (1, 2, 3, 5, 8, 13). Please estimate the story points for implementing an OAuth2 login flow based on standard team velocity metrics and complexity factors. | pass→fail | 13,698 | 8,308 | -39% | 1 | 1 | 0% | 2,226 | 1,559 | -30% | 0 | 0 | — |
▸case-22 Generate release notes for version 3.2.0 from the following commit logs: 'feat: add CSV export', 'fix: resolve memory leak in worker', 'docs: update API setup guide'. Summarize these changes by category. | pass→pass | 3,582 | 8,952 | +150% | 1 | 1 | 0% | 663 | 1,755 | +165% | 0 | 0 | — |