jira-action-plan

Convert a Jira issue into an approval-gated implementation plan with repo inspection.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Omniloy/agent-skills --skill jira-action-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-action-plan
Source: https://github.com/Omniloy/agent-skills/tree/main/skills/jira-action-plan
Command: npx skills add https://github.com/Omniloy/agent-skills --skill jira-action-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a Jira ticket into a careful implementation workflow so you can understand the issue, make the right design choices, and deliver changes without losing scope or control.

Core Features & Use Cases

  • Jira context gathering: Pulls the ticket, comments, remote links, and one-hop linked issues to build a clear picture of the request.
  • Repo-aware planning: Scans the current repository, identifies the closest code paths, and surfaces risks before any implementation starts.
  • Approval-gated execution: Drafts a step-by-step plan, pauses for human approval, and then implements one reviewable step at a time with explicit test and branch handling.
  • Use case: Ideal for a developer handling a single Jira task or feature who wants a disciplined, reviewed path from issue discovery to local implementation.

Quick Start

Ask the assistant to run /jira-action-plan with your Jira issue key or full issue URL.

Frequently Asked Questions about jira-action-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a Jira ticket into a reviewed implementation plan?

To turn a Jira ticket into a reviewed implementation plan, use a workflow that retrieves issue context, scans your local repository for relevant code paths, and drafts an approval-gated step-by-step execution plan before any changes are made.

Can I scope Jira feature implementation to specific repository code paths?

Yes, you can scope Jira feature implementation to specific repository code paths by performing repo-aware analysis that inspects the local repository, identifies the closest relevant code, and surfaces potential risks prior to starting development.

How does approval-gated execution work for Jira code review and testing?

Approval-gated execution for Jira code review and testing works by drafting a stepwise implementation plan, pausing for explicit human approval, and then executing changes one reviewable step at a time with dedicated test and commit controls.

What types of Jira issues can be processed for repo-aware analysis and stepwise implementation?

Jira issues that can be processed for repo-aware analysis and stepwise implementation include Task, Story, Feature, Bug, and Improvement tickets, provided they require scoped design decisions and local repository inspection.

Do I need local repository access for safe step-by-step Jira task implementation?

Yes, local repository access is required for safe step-by-step Jira task implementation because the workflow inspects local code paths to identify risks, make scoped decisions, and execute reviewable changes with explicit branch handling.

What is the best way to gather Jira context for a single feature workflow?

The best way to gather Jira context for a single feature workflow is to pull the ticket details, comments, remote links, and one-hop linked issues to build a comprehensive picture of the request before planning implementation.