What problem does it solve? Writing detailed, codebase-grounded implementation plans for Jira tickets is time-consuming, and vague plans slow developers down. This Skill automates the planning step by reading Jira epics and tickets, inspecting the actual codebase, and posting concrete implementation plans back to each ticket as comments. ## Core Features & Use Cases - Jira Ticket and Epic Planning: Accepts a single ticket key, multiple keys, or an epic key, then fetches the epic and all child tickets via JQL for batch planning. - Codebase-Grounded Plans: Reads relevant Django models, views, serializers, and frontend components so plans cite real file paths, model names, and endpoints rather than generic descriptions. - Structured Plan Output and Posting: Produces a consistent plan template covering data model changes, APIs, frontend changes, edge cases, testing, dependencies, and complexity estimates, then posts it as a Jira comment. - Use Case: A tech lead receives an epic with eight child stories and asks the Skill to plan the whole epic; each ticket gets a detailed, actionable implementation plan posted as a comment without any code being written. ## Quick Start Ask the assistant to run plan-pipeline for a Jira issue key such as RGDEV-180 or an epic key to generate and post implementation plans.