skills.rest
Shirataki2
Shirataki2COMMUNITY
Explore all skills by this author →
GitHub

issue-driven-development

Automate issue-driven development from issue selection to PR preparation.

2|Updated Dec 1, 2025
Search Tags:#git#branching#linear#software-development#workflow-automation#pull-request#issue-management
One-click install
npx skills add https://github.com/Shirataki2/discalendar-next-v2 --skill issue-driven-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-driven-development
Source: https://github.com/Shirataki2/discalendar-next-v2/tree/main/.claude/skills/issue-driven-development
Command: npx skills add https://github.com/Shirataki2/discalendar-next-v2 --skill issue-driven-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Linear Issue-driven Development coordinates the entire lifecycle from issue selection to branch creation, implementation, PR preparation, and eventual completion, reducing context switching and ensuring traceability.

Core Features & Use Cases

  • Phase-driven workflow: Select an issue, start work, implement changes, and prepare a PR with a clear linkage to the original issue.
  • Branch and PR discipline: Generates and uses consistent branch naming and PR workflows to maintain traceability.
  • State synchronization: Keeps issue status aligned with development progress from "In Progress" to "Done".

Quick Start

Select an issue from your tracker and run the start workflow to create a branch and begin implementation.

Frequently Asked Questions about issue-driven-development

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

FAQPage Schema
How do I automate issue-driven development from issue selection to pull request?▼

Issue-driven development automation coordinates the entire lifecycle from issue selection to branch creation, implementation, PR preparation, and completion, reducing context switching. It enforces a structured workflow with explicit phases to ensure traceability and predictable delivery.

How does branch naming work in an issue-driven workflow?▼

Branch naming in an issue-driven workflow uses deterministic conventions generated from the selected issue. This ensures consistent branch discipline and maintains clear traceability between the original issue tracker entry and the resulting code changes.

Can I synchronize issue tracker status with my development progress automatically?▼

Yes, issue-driven workflow automation keeps issue status synchronized with development progress. It aligns the issue tracker state from "In Progress" through implementation and PR preparation to final completion, ensuring state consistency.

What is the best way to ensure traceability between issues and pull requests?▼

Ensuring traceability between issues and pull requests requires a phase-driven workflow that links the original issue to the PR. This approach generates consistent branch naming and enforces PR workflows to maintain a clear development audit trail.

Does issue-driven development work without external dependencies?▼

Yes, this issue-driven development workflow operates with no external dependencies. It applies to projects that manage work via issue trackers, structuring the workflow internally to enable deterministic phase progression from planning to delivery.

Related Skills

Explore More Software Engineering Skills→
robwestzrobwestz

status-report-generator

Generate project status reports from Git history and issue trackers.

Community
Intermediate
smallnestsmallnest
207

ship-it

Commit changes, create and merge a pull request, and close the linked GitHub issue.

Community
Advanced
crsieblercrsiebler
1

git-manager

Manage Git branches, commits, and pull requests with Git Flow conventions.

Community
Intermediate
mag123cmag123c

task

Orchestrate software development tasks from analysis to Git commit.

Community
Advanced