Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gotalab/kiro-spec-tasks
Generate implementation tasks for a specification
Passed 12 of 17 test cases with the skill, and 5 of 17 without it.
and 9 more in the full report
9 fixed6 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
In `tasks.md` for `email-worker`, we have core implementation sub-tasks and optional post-MVP test coverage tasks for non-critical edge cases. What standard markdown checkbox syntax marks these deferred testing sub-tasks?
| Checked | Without skill | With skill |
|---|---|---|
| Uses the `- [ ]*` syntax for optional testing sub-tasks deferred post-MVP. | Passed | Passed |
| Restricts optional test task notation to test coverage satisfying already implemented acceptance criteria. | Missed | Passed |
The instructions your model reads when the skill loads.
<background_information>
tasks.md is written
</background_information>Read all necessary context:
{{KIRO_DIR}}/specs/$1/spec.json, requirements.md, design.md{{KIRO_DIR}}/specs/$1/tasks.md (if exists, for merge mode)product.md, tech.md, structure.mdValidate approvals:
-y flag provided: Auto-approve requirements and design in spec.json. Tasks approval is also handled automatically in Step 4.--sequentialLoad generation rules and template:
rules/tasks-generation.md from this skill's directory for principlessequential is false: Read rules/tasks-parallel-analysis.md from this skill's directory for parallel judgement criteria{{KIRO_DIR}}/settings/templates/specs/tasks.md for format (supports (P) markers)The following research areas are independent and can be executed in parallel:
test cases passed, vs 5 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.