Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
91
92%
Does it follow best practices?
Impact
83%
1.48xAverage score across 3 eval scenarios
Passed
No known issues
Vertical slice issue planning from feature plan
Vertical slice structure
16%
83%
Thin slices — many over few
100%
100%
Each slice demoable
50%
70%
HITL/AFK labels present
70%
90%
AFK preferred over HITL
0%
100%
Dependency order
100%
87%
What to build section
75%
87%
End-to-end behavior description
40%
60%
Acceptance criteria section
100%
100%
Blocked by section
75%
100%
needs-triage label
0%
0%
Issue template format and parent issue handling
Parent section present
60%
100%
What to build section
0%
100%
End-to-end behavior in What to build
0%
60%
Acceptance criteria section
100%
100%
Blocked by section
50%
100%
None/can start immediately phrasing
25%
100%
Vertical slices
0%
30%
HITL/AFK classification
40%
100%
Dependency order
100%
100%
needs-triage label
0%
0%
Parent issue unmodified
100%
100%
Domain vocabulary, ADRs, and AFK preference in issue planning
Domain vocabulary usage
100%
100%
ADR-012 respected
100%
100%
Thin vertical slices
100%
100%
Each slice end-to-end
50%
100%
HITL/AFK labels
50%
100%
AFK majority
100%
100%
What to build section
75%
100%
Acceptance criteria with checkboxes
100%
100%
Blocked by section
75%
87%
Dependency ordering
100%
100%
needs-triage label
0%
0%
Behavior not layer breakdown
33%
83%
a05d4e5
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.