to-issueslisted

> Source: [mattpocock/skills - engineering/to-tickets](https://github.com/mattpocock/skills/tree/main/skills/engineering/to-tickets) # To Issues Break a plan into independently-grabbable issues using vertical slices (tracer bullets). Target the project's issue tracker directly - GitHub via `gh` or Jira via `acli`, per `rules/git-conventions.md` and `rules/jira.md`. Use whatever label the tracker already uses to mark agent-ready work. ## Process ### 1. Gather context Work from whatever is already in the conversation context. If the user passes an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker and read its full body and comments. ### 2. Explore the codebase (optional) If you have not already explored the codebase, do so to understand the current state of the code. Issue titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching. Look for opportunities to prefactor the code to make the implementation easier - "make the change easy, then make the easy change." Any prefactoring should be its own issue, sequenced first. `(review-time: see section note)` ### 3. Draft vertical slices **why-no-hook:** skill workflow guidance; each step requires understanding the surrounding context (repo, task shape, prior state). 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 sl