Decompose a PRD issue into tracer-bullet tickets — demoable vertical slices sized to one fresh context window, with blocking edges and autonomy labels, published to the project issue tracker. Use after /to-prd when a build spans more than one session; skip it (use /implement directly) when the whole change fits one context window.
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
The canonical home for this skill is to-tickets in agranado2k/google-books-clojure
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The required procedure reads a PRD issue body from the project's GitHub issue tracker (step 1, "Read the PRD (issue body or conversation spec)"), and outsiders can file or comment on GitHub issues, so the workflow ingests outsider-authored text without the agent selecting a specific item.
agranado2k/tic-tac-toe-with-agentic-sdlc
931d5f3
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.