jira-task

Name: jira-task
Availability: InStock
Author: Fyodor

Automate Jira ticket lifecycle from research through PR creation across multiple repositories.

Updated Aug 27, 2026

Search Tags:#automation #tdd #branching #multi-repo #jira #ticket-management

Ready to run

npx skills add https://github.com/fyodoriv/agentbrew --skill jira-task-fyodoriv

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jira-task
Source: https://github.com/fyodoriv/agentbrew/tree/main/skill-plugins/dev/jira-task
Command: npx skills add https://github.com/fyodoriv/agentbrew --skill jira-task-fyodoriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end Jira ticket lifecycle: research → branch → plan → implement (TDD) → validate → commit → PR. One-shots a ticket from "In Progress" to "ready for review". Use when starting work on a Jira ticket. Don't use for creating tickets (use jira) or pure planning (use plan).

Core Features & Use Cases

Orchestrates the full Jira ticket workflow across multiple repos so work starts quickly and stays aligned.
Automatically discovers related repositories, creates feature branches per ticket, and keeps Jira updated with Implementation Notes.
Enforces a TDD-driven workflow with disciplined commits and ticket state transitions to reduce drift and manual handoffs.

Quick Start

Provide a Jira issue key to start the end-to-end lifecycle automation.

Frequently Asked Questions about jira-task

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

FAQPage Schema

How do I automate the Jira ticket lifecycle from branching to pull request creation?▼

Automate the Jira ticket lifecycle end-to-end by providing a Jira issue key to trigger an automated workflow: research, branch creation, TDD implementation, validation, and PR creation. This orchestrates the entire process from "In Progress" to "ready for review".

Can I coordinate feature branches across multiple related repositories for a single Jira ticket?▼

Yes, multi-repo project coordination is supported. The automation discovers related repositories, clones them, and creates feature branches per ticket, ensuring all related codebases are aligned and updated with implementation notes in Jira.

How do I enforce a test-driven development workflow when implementing Jira tickets?▼

Enforce a TDD-driven workflow by automating the ticket lifecycle with strict commit-driven development. The process moves from planning through implementation and validation, ensuring disciplined commits and ticket state transitions to reduce drift.

Does jira-task work for creating new Jira tickets or just planning?▼

jira-task automates the end-to-end implementation lifecycle for existing tickets. It should not be used for creating tickets or pure planning; use dedicated tools for those tasks. It is designed to one-shot a ticket from "In Progress" to ready for review.

What is the best way to keep Jira updated with implementation notes during multi-repo development?▼

Keep Jira updated with implementation notes by using an automated ticket lifecycle workflow. The automation manages branch creation, applies TDD implementation, and modernizes Jira description updates automatically as work progresses across repositories.