issue-workflow

Guides GitHub issue-to-merge workflow with TDD, PRs, code review, and merge criteria for Kanban teams.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Inteligentsensingsolutions/tdd-dev-workflow --skill issue-workflow-inteligentsensingsolutions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-workflow
Source: https://github.com/Inteligentsensingsolutions/tdd-dev-workflow/tree/main/skills/issue-workflow
Command: npx skills add https://github.com/Inteligentsensingsolutions/tdd-dev-workflow --skill issue-workflow-inteligentsensingsolutions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinated, repeatable guidance for moving GitHub issues from Todo to Done, ensuring every handoff follows a standardized lifecycle with explicit criteria and artifacts.

Core Features & Use Cases

  • Enforces the issue lifecycle: Todo → In Progress → Review → Done, with rules for when to transition.
  • Guides branching and PR conventions: naming schemes, commit discipline, and review expectations.
  • Supports end-to-end development with TDD, automated checks, and merge strategies, including auto-closing of issues on merge.
  • Use Case: A team can start with an issue, create a feature branch, implement tests first, submit a PR, undergo code review, and merge, with the issue closing automatically.

Quick Start

Tell me the issue ID you want to start with and I will guide you through picking, branching, implementing with TDD, reviewing, and merging it.

Frequently Asked Questions about issue-workflow

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

FAQPage Schema
How do I manage a GitHub issue lifecycle from Todo to Done?

To enforce a structured GitHub issue lifecycle, you transition issues through Todo, In Progress, Review, and Done states. This workflow defines hard requirements for state transitions, branch naming, PR conventions, and auto-closing rules to ensure consistent delivery.

What's the best way to automate issue closing on PR merge in a Kanban workflow?

Automating issue closing on PR merge in a Kanban workflow requires defining explicit auto-closing rules. This workflow ensures that when a feature branch is merged after code review, the associated GitHub issue automatically transitions to Done without manual intervention.

How do I enforce git branching and PR conventions for development teams?

Enforcing git branching and PR conventions involves defining hard requirements for branch naming schemes and commit discipline. This workflow guides teams to standardize PR conventions, ensuring all handoffs follow a standardized lifecycle with explicit artifacts and review expectations.

Can I integrate TDD discipline into an end-to-end issue-to-merge workflow?

Integrating TDD discipline into an issue-to-merge workflow means implementing tests first before submitting a PR. This workflow supports end-to-end development by guiding teams to implement tests, run automated checks, and meet merge criteria including code review.

Does this issue workflow support Kanban-based project management?

Yes, this issue workflow supports Kanban-based projects by enforcing the issue lifecycle: Todo → In Progress → Review → Done. It provides explicit criteria for when to transition states across the end-to-end GitHub issue-to-merge lifecycle.