plan-jira-ticket

Creating an implementation plan from a Jira ticket involves extracting requirements, performing root-cause analysis on the codebase, proposing solution options, and writing a documented workplan. This Skill automates that workflow by generating plan.md and progress.md files inside your docs directory for review.

Root-cause analysis in software engineering workplans searches and inspects relevant files, tests, and dependencies to identify true defects or constraints. It provides cited evidence to ensure the implementation plan addresses the actual underlying issues rather than just surface symptoms.

Breaking down Jira tickets involves deep requirements synthesis to surface implicit requirements and edge cases. You then map these into decision-driven implementation tasks, producing up to three optimized maintainable solution options with documented pros and cons for team review.

Yes, you need a designated worktree to finalize a ticket workplan. The planning process validates and operates inside the isolated worktree to ensure proposed solutions and generated documentation align with the correct codebase state before implementation begins.

The best way to document solution options before coding is to write a structured plan.md file under a docs/<ticket-id>/ directory. This file should capture up to three optimized solution options with pros and cons, pausing for a user decision before finalizing the implementation tasks.

Yes, you can track implementation progress alongside the ticket workplan. The process generates a progress.md file within the same docs/<ticket-id>/ directory, providing a tracker that developers and reviewers can update during execution against the isolated worktree.