jira-plan

Analyze Jira issues and project code to generate Markdown development guides.

3|1|Updated May 1, 2026

Search Tags:#automation #code analysis #project planning #issue analysis #jira #development guide

Ready to run

npx skills add https://github.com/bigbulgogiburger/claude_jira_harness --skill jira-plan-bigbulgogiburger

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jira-plan
Source: https://github.com/bigbulgogiburger/claude_jira_harness/tree/main/skills/jira-plan
Command: npx skills add https://github.com/bigbulgogiburger/claude_jira_harness --skill jira-plan-bigbulgogiburger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating comprehensive development guides by analyzing Jira issues and project code, reducing manual documentation effort.

Core Features & Use Cases

Issue Analysis: Deeply analyzes Jira issues, including descriptions, comments, and sub-tasks, to understand requirements.
Codebase Inspection: Automatically inspects project files and architecture to inform development plans from the perspective of a senior developer persona.
Guide Generation: Produces a structured, detailed Markdown development guide with implementation phases, impact analysis, and technical considerations for each issue.
Use Case: A team receives a Jira ticket requesting feature enhancement; using this Skill, they generate a step-by-step development guide that covers affected files, potential risks, and implementation phases, ensuring clarity before coding.

Quick Start

Run the command to generate a development guide for a specific Jira issue key to facilitate planning and implementation.

Frequently Asked Questions about jira-plan

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

FAQPage Schema

How do I generate a development guide from Jira issues automatically?▼

To generate a development guide from Jira issues, analyze the issue descriptions, comments, and sub-tasks alongside your project code. This process identifies affected files, technical strategies, and risk factors to produce a structured Markdown implementation plan.

What is the best way to plan implementation phases for a Jira feature request?▼

Planning implementation phases for a Jira feature request is best done by inspecting your codebase architecture and issue details to map out technical considerations. This approach yields a step-by-step development guide covering potential risks and affected files.

Can I use Jira issue analysis to identify affected files in my codebase?▼

Yes, Jira issue analysis can identify affected files in your codebase by deeply analyzing issue requirements and automatically inspecting your project architecture. This ensures your development plan accurately reflects necessary code changes from a senior developer perspective.

Does automated project planning from Jira tickets work for complex codebases?▼

Automated project planning from Jira tickets works for complex codebases by inspecting project files and architecture to inform comprehensive plans. It ensures detailed documentation aligned with senior engineering perspectives, covering technical strategies and risk factors.

What should a detailed development guide generated from issue analysis include?▼

A detailed development guide generated from issue analysis should include implementation phases, impact analysis, technical considerations, and identified risk factors. It maps out affected files based on Jira issue requirements and codebase inspection to ensure clarity before coding.

Why does manual documentation fall short compared to automated Jira issue analysis?▼

Manual documentation falls short compared to automated Jira issue analysis because it requires significant effort to deeply analyze tickets and inspect codebase architecture. Automation streamlines this by directly generating comprehensive, structured Markdown development guides with implementation phases.