skills.rest
luigiinred
luigiinredCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

dev-workflow-start-work

Extract ticket IDs from branch names, fetch requirements, and create an implementation plan.

1|Updated Feb 18, 2026
Search Tags:#development workflow#github#ticket management#issue tracking#coding#jira
One-click install
npx skills add https://github.com/luigiinred/dotfiles --skill dev-workflow-start-work
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-workflow-start-work
Source: https://github.com/luigiinred/dotfiles/tree/main/dot_cursor/skills/dev-workflow-start-work
Command: npx skills add https://github.com/luigiinred/dotfiles --skill dev-workflow-start-work

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of starting or resuming work on a development ticket or issue, streamlining the initial setup and planning phase of coding tasks.

Core Features & Use Cases

  • Automated Ticket/Issue Identification: Extracts ticket or issue IDs directly from branch names.
  • Requirement Fetching: Gathers details from Jira or GitHub using respective APIs.
  • Implementation Planning: Generates a structured plan based on requirements.
  • Commit Strategy: Asks the user for their preferred commit strategy (atomic, single, manual).
  • Use Case: When you're ready to start coding on a new feature, simply run this skill, and it will identify your ticket, fetch requirements, propose a plan, and prepare for implementation based on your commit preferences.

Quick Start

Use the dev-workflow-start-work skill to begin working on the current ticket.

Frequently Asked Questions about dev-workflow-start-work

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

FAQPage Schema
How do I automate starting work on a Jira ticket or GitHub issue?▼

You can automate starting work on a Jira ticket or GitHub issue by extracting the identifier from your branch name, fetching requirements via Jira MCP or GitHub API, and generating an implementation plan.

How do I fetch Jira requirements using my current Git branch name?▼

Fetching Jira requirements is handled by extracting the ticket identifier directly from your branch name, querying the Jira MCP, and presenting the specifications for your coding task.

Can I choose my commit strategy when starting a development workflow?▼

Yes, you can choose your commit strategy when starting a development workflow by selecting atomic, single, or manual commits during the implementation plan confirmation phase.

Does this development workflow skill work with both Jira and GitHub issue tracking?▼

Yes, the development workflow skill works with both Jira and GitHub issue tracking by utilizing the Jira MCP and GitHub API to fetch requirements based on the extracted identifiers.

What is the best way to create an implementation plan from a GitHub issue?▼

The best way to create an implementation plan from a GitHub issue is to parse the issue ID from your branch, fetch the details via the GitHub API, and generate a structured plan for user confirmation.

Related Skills

Explore More Software Engineering Skills→
shysssthanhtrishysssthanhtri

create-branch

Create a git branch from a Jira ticket key and issue summary slug.

Community
Intermediate
ajsai47ajsai47
11

do

Execute phased implementation plans with subagent delegation and verification.

Community
Advanced
Luney-IndustriesLuney-Industries
4

ship-task

Merge GitHub pull requests and transition Linear or Jira tickets to Done.

Official
Advanced
mcj-codermcj-coder
1

requirements-gathering

Gather requirements through interactive questioning and create structured tickets.

Community
Advanced