work-on-ticket-plan

To execute a Jira ticket implementation plan phase-by-phase, this Skill reads your plan and progress docs, presents a structured summary for the next incomplete phase, and waits for your approval before writing code or staging commits.

To track pre-existing test failures when implementing Jira tickets, the Skill captures a pre-implementation full-test baseline, allowing it to distinguish prior failures from new regressions introduced during your current phase changes.

Yes, this workflow requires a dedicated git worktree for ticket implementation, specifically expecting the worktree to contain your plan and progress markdown files inside a docs directory matching your ticket ID.

You can create a draft PR after completing a Jira ticket implementation plan by requesting it once your final phase is approved, integrating directly with conventional-commit workflows to stage only approved changes.

If the full-suite regression check fails after the final phase, the Skill requires you to fix the regressions or escalate the issue, preventing incomplete or broken code from being committed to your branch.

Unlike manual git staging for Jira ticket execution, conventional commit workflows automatically stage only approved phase changes and generate standardized commit messages, ensuring an auditable and disciplined project history.