skills.rest
fabiano001
fabiano001COMMUNITY
Explore all skills by this author →
GitHub

ticket-driver

Orchestrate Jira ticket-driven development with a TDD-first workflow and Git branch handling.

Updated Aug 6, 2025
Search Tags:#automation#git#planning#tdd#jira#ticket#branch
One-click install
npx skills add https://github.com/fabiano001/claude-config --skill ticket-driver
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket-driver
Source: https://github.com/fabiano001/claude-config/tree/main/skills/ticket-driver
Command: npx skills add https://github.com/fabiano001/claude-config --skill ticket-driver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fetch Jira ticket details and coordinates a deterministic, plan-driven workflow to implement changes with a TDD-first loop, including robust Git branch handling and support for PLAN-MODE.

Core Features & Use Cases

  • Fetches Jira ticket data and accepts manual inputs to override or augment the ticket details.
  • Produces a concrete implementation plan and context for SprintLoop-style execution, including PLAN-MODE for non-execution runs.
  • Handles Git branches automatically (or uses USE-CURRENT-BRANCH to stay on the current branch) and supports base-branch selection.
  • Dispatches execution to autonomous subagents while keeping user input and data in sync.
  • Outputs plan.md and context.md for downstream sprint tooling and audit trails.

Quick Start

Invoke /ticket-driver PLAN-MODE sprint_1 TRIDENT-802 to generate a plan and context without executing changes.

Frequently Asked Questions about ticket-driver

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

FAQPage Schema
How do I automate Jira ticket workflows with Git branch handling?▼

Automate Jira ticket workflows by fetching ticket data, merging manual inputs, and executing a plan-driven TDD-first loop with deterministic Git branch creation and base-branch selection. It outputs plan and context files for downstream execution.

Can I generate a Jira implementation plan without executing code changes?▼

Yes, you can generate an implementation plan without execution by invoking the PLAN-MODE flag. This produces a plan.md and context.md for SprintLoop-style execution and audit trails while skipping autonomous code changes.

How do I override Jira ticket details with manual inputs for TDD planning?▼

Manual inputs override Jira ticket data during the planning phase. You provide additional context alongside fetched Jira details, and the workflow merges them to produce a deterministic, TDD-first implementation plan for execution.

Does the Jira ticket workflow support using the current Git branch?▼

Yes, the workflow supports a USE-CURRENT-BRANCH mode to skip automatic Git branch setup. This allows the plan-driven TDD-first execution loop to run directly on your existing branch without creating a new one.

What is the best way to integrate Jira ticket data with SprintLoop execution?▼

Integrate Jira ticket data with SprintLoop execution by orchestrating a plan-first workflow that dispatches autonomous subagents. It generates deterministic context.md and plan.md outputs to keep user input and downstream tooling synchronized.

Related Skills

Explore More Software Engineering Skills→
darellchua2darellchua2
4

jira-git-integration

Create Jira issues, add comments, upload attachments, and generate branch names from ticket keys.

Community
Intermediate
discountedcookiediscountedcookie

openspec-apply

Execute approved OpenSpec change tasks step-by-step with test-tdd verification.

Community
Advanced
GregoryHoGregoryHo
6

arc-agent-driven

Dispatch fresh subagents to execute task lists with two-stage reviews.

Community
Advanced
CodySwannGTCodySwannGT
3

jira-sync

Synchronize plan progress and development milestones to linked JIRA tickets.

Community
Intermediate