Turn a Jira ticket into a scoped implementation plan
Read a Jira ticket and generate an implementation plan with affected files, changes, and test coverage
Overview
Moving from ticket to code means first figuring out what the ticket actually requires—which files to touch, what edge cases matter, and what tests to write. This template reads the ticket and writes out a plan you can execute against, so you spend less time reverse-engineering and more time building.
How it works
- Fetches the Jira ticket by ID from your specified project
- Reads the title, description, and acceptance criteria
- Analyzes the codebase to identify affected files
- Writes an implementation plan with proposed changes, edge cases, and test coverage
- Posts the plan as a comment on the Jira ticket
Who this is for
Engineers who want to move faster from ticket to implementation without spending time manually scoping the work.
Suggested prompt
Fetch the Jira ticket [1. Ticket ID] from project [2. Project key]. Read the title, description, and any acceptance criteria. Based on the codebase in this repository, write an implementation plan that includes: affected files, proposed changes per file, edge cases to handle, and suggested test coverage. Post the plan as a comment on the same Jira ticket.
Frequently asked questions
Can I save the plan somewhere else?
Yes, modify the prompt to save the plan to Confluence, Notion, or a Google Doc instead of a Jira comment.
Can I customize what the plan includes?
Yes, adjust the prompt to add or remove sections like dependencies, rollback steps, or deployment notes.
What if I use Linear instead of Jira?
Swap Jira for Linear in the prompt and connect Linear to your MCP server.
Can I generate plans for multiple tickets at once?
Yes, modify the prompt to loop through a list of ticket IDs and generate a plan for each.