issue-driven-development

Orchestrate a 13-step GitHub issue-driven development workflow with TDD and CI verification.

10|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/troykelly/codex-skills --skill issue-driven-development-troykelly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-driven-development
Source: https://github.com/troykelly/codex-skills/tree/main/skills/issue-driven-development
Command: npx skills add https://github.com/troykelly/codex-skills --skill issue-driven-development-troykelly

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a disciplined, step-by-step process for software development, ensuring all work is tied to GitHub issues, follows best practices like TDD, and includes rigorous verification and review gates.

Core Features & Use Cases

  • Issue Tracking: Enforces that all work starts with a clearly defined GitHub issue.
  • Development Workflow: Guides through a 13-step process including research, TDD, code review, and CI monitoring.
  • Project Board Integration: Mandates continuous updates to GitHub project boards for status tracking.
  • Use Case: A developer needs to implement a new feature. They use this Skill to ensure the feature is properly defined in an issue, broken down if necessary, developed with tests, reviewed thoroughly, and merged only after all checks pass, with the project board status updated at each stage.

Quick Start

Follow the 13-step process outlined in the issue-driven-development skill to complete your current task.

Frequently Asked Questions about issue-driven-development

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

FAQPage Schema
What is issue-driven development and how does it manage a GitHub workflow?

Issue-driven development is a software development workflow that enforces GitHub issue tracking, TDD, code review, and CI verification. It manages project board status updates and branch discipline throughout the entire development lifecycle.

How do I implement TDD within a structured GitHub issue workflow?

Implement TDD within a GitHub issue workflow by following a structured 13-step process. This guides you through research, test-driven development, comprehensive code review, and CI monitoring before merging any feature branches.

Can I use this development workflow process without a GitHub project board?

No, this development workflow process mandates continuous updates to GitHub project boards. It enforces project board integration to ensure strict status tracking and branch discipline across all development stages.

What's the best way to enforce code review and CI verification before a pull request?

Enforce code review and CI verification before a pull request by using an orchestrated development process. It integrates PR creation gates to ensure branches merge only after all tests and checks pass.

Does this 13-step development process handle breaking down large GitHub issues?

Yes, the 13-step development process handles large GitHub issues by breaking them down if necessary. It ensures features are properly defined in an issue, developed with tests, and reviewed thoroughly before merging.