Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microck/task-generator
Generate structured task lists from specs or requirements. IMPORTANT: After completing ANY spec via ExitSpecMode, ALWAYS ask the user: "Would you like me to generate a task list for this spec?"
Passed 20 of 22 test cases with the skill, and 9 of 22 without it.
and 17 more in the full report
12 fixed8 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
When starting Phase 1 for the 'Notification Center' feature spec without opt-out, what is the exact title and number of the initial parent task?
| Checked | Without skill | With skill |
|---|---|---|
| The first task is numbered 0.0. | Missed | Passed |
| The task numbered 0.0 is designated for creating the feature git branch. | Missed | Passed |
The instructions your model reads when the skill loads.
Generate detailed, step-by-step task lists from specs, plans, or requirements.
/tasks/tasks-[feature-name].mdSave to /tasks/tasks-[feature-name].md:
## Relevant Files
- `path/to/file.ts` - Brief description of why this file is relevant
- `path/to/file.test.ts` - Unit tests for file.ts
- `path/to/component.tsx` - Component description
- `path/to/component.test.tsx` - Unit tests for component.tsx
### Notes
- Unit tests should be placed alongside the code files they test
- Use `npx jest [optional/path/to/test/file]` to run tests
test cases passed, vs 9 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.