skills.rest
hadenlabs
hadenlabsOFFICIAL
Explore all skills by this author →
Website𝕏@hadenlabsGitHub

jira-start-task

Select an unfinished Jira issue and create a feature/<ISSUE-KEY> branch.

1|Updated Dec 9, 2024
Search Tags:#git#mcp#branching#jira#openspec#issue-tracking
One-click install
npx skills add https://github.com/hadenlabs/tasks --skill jira-start-task
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-start-task
Source: https://github.com/hadenlabs/tasks/tree/main/.claude/skills/jira-start-task
Command: npx skills add https://github.com/hadenlabs/tasks --skill jira-start-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Jira planning and execution can slow teams down when engineers must locate an unfinished issue, verify the correct branch naming convention, and prepare a structured prompt for OpenSpec enrichment. This skill automates those steps and coordinates Jira, Git, and MCP workflows to streamline task intake and branch creation.

Core Features & Use Cases

  • List unfinished Jira issues assigned to the current user and present a selectable menu.
  • Create or verify a deterministic branch named feature/<ISSUE-KEY>, ensuring it exists before proceeding.
  • Generate an OpenSpec prompt and enrich context via Obsidian MCP when available.

Quick Start

Ask the agent to start work on a Jira issue by selecting a pending task and creating the corresponding feature branch.

Frequently Asked Questions about jira-start-task

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

FAQPage Schema
How do I create a feature branch from an unfinished Jira issue?▼

You can start a Jira task by providing an issueKey to fetch it directly, or let the skill read jasper.toml for your projectKey, query eligible issues, and present a numbered list for selection before branching.

What is the correct branch naming convention when starting Jira work?▼

The correct branch naming convention is feature/<ISSUE-KEY>. The skill ensures this deterministic branch name exists and applies git operations to verify it before proceeding.

How does Jira issue branching integrate with OpenSpec and Obsidian?▼

Jira issue branching integrates with OpenSpec and Obsidian by optionally generating an OpenSpec prompt and enriching task context via Obsidian MCP after the feature branch is created.

Do I need a specific configuration file to list my pending Jira issues?▼

You need a jasper.toml configuration file to list pending Jira issues if no explicit issueKey is provided. The skill reads this file to obtain your projectKey for querying eligible issues.

Can I select a specific Jira issue instead of choosing from a list?▼

You can select a specific Jira issue by providing an issueKey. If provided, the skill fetches that exact issue directly, bypassing the query and numbered selection list.

What limitations exist when automating Jira task intake and git branching?▼

Limitations include requiring a jasper.toml file for projectKey lookup without an issueKey, and dependency on Obsidian MCP availability for context enrichment during OpenSpec prompt generation.

Related Skills

Explore More Software Engineering Skills→
hadenlabshadenlabs
1

jira-add-worklog

Derive Jira issue keys from Git branches and submit worklogs.

Official
Intermediate
081595081595

openspec-apply-change

Implement OpenSpec change tasks using the openspec CLI.

Community
Advanced
dtsongdtsong
1

GitHub Issue

Create and manage GitHub issues with templates and branch linking.

Community
Intermediate
pabloimrik17pabloimrik17

openspec-ff-change

Automate creation of OpenSpec change artifacts within CLI workflows.

Community
Intermediate