Jira Driven Planning

This takes Jira ticket requirements and Confluence docs that you've already fetched and turns them into a structured implementation plan split across Frontend, Backend, and Infrastructure. It follows a template approach and expects you to have the context loaded before running it. The output focuses on task breakdown, dependencies, and risk assessment without diving into implementation details. Use it when you need to convert a ticket into an actual work plan for your team. It's opinionated about staying at the planning level rather than getting into code, which is probably the right call for this phase. The workflow is straightforward: review inputs, apply template, present for review.