Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mkurman/to-issues
Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices.
Passed 12 of 19 test cases with the skill, and 7 of 19 without it.
and 5 more in the full report
8 fixed7 passed either way7 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
For a vertical slice issue that has no prior blocking tasks, what explicit text should be placed under the Blocked by header in the ticket body?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies 'None - can start immediately' under the Blocked by header. | Missed | Passed |
The instructions your model reads when the skill loads.
Break a plan into independently-grabbable GitHub issues using vertical slices (tracer bullets).
Work from whatever is already in the conversation context. If the user passes a GitHub issue number or URL as an argument, fetch it with gh issue view <number> (with comments).
If you have not already explored the codebase, do so to understand the current state of the code.
Break the plan into tracer bullet issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.
Slices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible.
Present the proposed breakdown as a numbered list. For each slice, show:
Ask the user:
test cases passed, vs 7 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.