▸case-01 We are planning the implementation of a new user authentication service based on our spec document. Can you split this feature into manageable work items with titles, clear acceptance checks, prerequisite links, and effort estimates? Make sure to include parallel work streams, highlight the longest sequence of dependent items, and link each item back to our spec requirements. | fail→pass | 20,439 | 27,575 | +35% | 1 | 1 | 0% | 4,253 | 4,877 | +15% | 0 | 0 | — |
▸case-02 I need to break down our upcoming multi-tenant dashboard epic into actionable developer subtasks. Please structure the work so each item has a unique ID, detailed description, success criteria, and effort rating. I also need to see which tasks can be worked on concurrently, the main bottleneck path, and dedicated testing tasks paired with the feature work. | fail→fail | 18,479 | 19,272 | +4% | 1 | 1 | 0% | 3,596 | 3,552 | -1% | 0 | 0 | — |
▸case-03 Could you help structure our upcoming payment gateway integration project into individual coding tasks? We need a detailed breakdown where every item lists its prerequisites, estimated effort, and test criteria. Please group items that don't depend on each other for concurrent assignment and identify the longest execution chain from start to finish. | fail→pass | 20,548 | 19,235 | -6% | 1 | 1 | 0% | 3,657 | 4,348 | +19% | 0 | 0 | — |
▸case-04 We are breaking down our notification engine spec into engineering tasks. A team member suggested creating a single combined task titled 'Build, test, and deploy entire SMS and Email delivery pipelines' with an effort estimate of 3 weeks. Should we keep this as one big task to avoid overhead, or how should work items be scoped for development sessions? | fail→pass | 13,356 | 11,595 | -13% | 1 | 1 | 0% | 2,372 | 2,495 | +5% | 0 | 0 | — |
▸case-05 During the task breakdown for our search indexing service, Task A (Schema Migration) depends on Task B (Query Service), but Task B relies on Task A's database schema being available first. Is it acceptable to mark these two tasks as mutually dependent in our task breakdown graph? | fail→fail | 11,871 | 6,006 | -49% | 1 | 1 | 0% | 1,755 | 1,255 | -28% | 0 | 0 | — |
▸case-06 I'm generating a task breakdown list for our CSV export feature spec. My lead says a simple bulleted list of task titles like 'Create export route' and 'Format CSV output' is enough for engineering handover. What exact fields must be defined for each decomposed task? | pass→pass | 14,747 | 6,496 | -56% | 1 | 1 | 0% | 2,312 | 1,475 | -36% | 0 | 0 | — |
▸case-07 We are decomposing the user profile edit feature spec into development tasks. Should acceptance testing and unit test creation be folded implicitly into each developer's coding task, or handled as distinct items? | pass→pass | 13,149 | 9,256 | -30% | 1 | 1 | 0% | 2,129 | 2,065 | -3% | 0 | 0 | — |
▸case-08 Once we finish generating our task breakdown, dependency graph, parallel groups, and requirement mappings for the new rate-limiting middleware, can developers immediately start pulling tasks into the sprint? | fail→pass | 9,874 | 5,011 | -49% | 1 | 1 | 0% | 1,537 | 1,082 | -30% | 0 | 0 | — |
▸case-09 We have decomposed our OAuth2 authorization server spec into 12 tasks. Developers want to know which chain of dependent tasks dictates the absolute minimum duration to complete the feature. How do we determine this sequence? | fail→fail | 13,132 | 10,286 | -22% | 1 | 1 | 0% | 2,163 | 1,995 | -8% | 0 | 0 | — |
▸case-10 In our audit logging feature breakdown, we have tasks for database table creation, S3 archive configuration, and UI log viewer styling. How should we group tasks that have no mutual dependencies among them? | fail→fail | 9,187 | 8,480 | -8% | 1 | 1 | 0% | 1,581 | 1,559 | -1% | 0 | 0 | — |
▸case-11 We are running an automated spec-kit workflow babysitter process to decompose our real-time messaging spec. Which tool path should be invoked specifically for the task decomposition phase? | fail→pass | 9,240 | 1,836 | -80% | 1 | 1 | 0% | 1,558 | 534 | -66% | 0 | 0 | — |
▸case-12 When running the complete end-to-end spec-kit pipeline process for a feature, which overarching tool route is invoked? | fail→pass | 9,034 | 1,780 | -80% | 1 | 1 | 0% | 1,522 | 540 | -65% | 0 | 0 | — |
▸case-13 An engineer added a task called 'Refactor legacy logging utility to use colorized console output' during our spec breakdown for the new file upload service. This refactoring is not mentioned in the specification. Should this task be included in the feature task breakdown? | pass→pass | 10,402 | 7,676 | -26% | 1 | 1 | 0% | 1,682 | 1,393 | -17% | 0 | 0 | — |
▸case-14 When decomposing the Webhook Management API spec, a developer asks whether a task should span an entire 2-week sprint or if tasks should be sized differently. What is the standard atomic scope for a task? | fail→pass | 9,891 | 4,171 | -58% | 1 | 1 | 0% | 1,772 | 820 | -54% | 0 | 0 | — |
▸case-15 When processing a spec document into actionable engineering tasks, what steps should immediately follow identifying parallel groups and determining the critical path, before requesting human review? | fail→pass | 11,317 | 2,854 | -75% | 1 | 1 | 0% | 1,804 | 768 | -57% | 0 | 0 | — |
▸case-16 In our ETL pipeline task breakdown, Task 101 (Data Ingestion) depends on Task 102 (Validation Schema), and Task 102 depends on Task 101's output format. How should dependency graph constraints handle this loop? | fail→fail | 11,594 | 9,117 | -21% | 1 | 1 | 0% | 1,989 | 1,912 | -4% | 0 | 0 | — |
▸case-17 Can we skip writing explicit acceptance criteria for small tasks in our task decomposition list, like 'Add config variable for Redis timeout', to save planning time? | fail→pass | 12,418 | 10,186 | -18% | 1 | 1 | 0% | 1,913 | 1,952 | +2% | 0 | 0 | — |
▸case-18 What is the difference in tool invocation between running just the task decomposition phase versus orchestrating the complete spec-kit workflow? | fail→pass | 13,602 | 4,619 | -66% | 1 | 1 | 0% | 2,231 | 893 | -60% | 0 | 0 | — |
▸case-19 During a task decomposition audit for our PDF generator feature, we found 2 tasks that do not connect to any specification requirement in the spec document. How should these unmapped tasks be treated? | pass→pass | 9,989 | 8,211 | -18% | 1 | 1 | 0% | 1,723 | 1,652 | -4% | 0 | 0 | — |
▸case-20 We need to draft a technical specification document for our new file upload service, outlining system requirements, architectural components, and API contracts. Can you write the spec document text? | fail→fail | 23,802 | 29,134 | +22% | 1 | 1 | 0% | 4,615 | 5,922 | +28% | 0 | 0 | — |
▸case-21 Our backend team has 4 engineers with 80 total available hours next sprint. Developer A is taking 2 days off. Can you calculate our sprint capacity and build a developer assignment calendar schedule for the next two weeks? | fail→fail | 18,272 | 12,683 | -31% | 1 | 1 | 0% | 3,138 | 2,790 | -11% | 0 | 0 | — |
▸case-22 Here is Task 101 acceptance criteria: 'Implement POST /api/v1/auth/login returning a JWT token with 15-minute expiration'. Please write the TypeScript/Node.js Express controller implementation for this route. | fail→fail | 10,740 | 12,003 | +12% | 1 | 1 | 0% | 2,412 | 2,477 | +3% | 0 | 0 | — |