issue-workflow

Orchestrate GitHub issue lifecycles from creation to closure with sub-skills.

Updated Jan 5, 2025
One-click install
npx skills add https://github.com/pkuppens/pkuppens --skill issue-workflow-pkuppens
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-workflow
Source: https://github.com/pkuppens/pkuppens/tree/main/skills/issue-workflow
Command: npx skills add https://github.com/pkuppens/pkuppens --skill issue-workflow-pkuppens

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub issue drafts are frequently inconsistent and incomplete, leading to wasted cycles and misaligned work. This Skill provides a repeatable flow to convert ideas into well-formed issues with clear scope, acceptance criteria, and traceability.

Core Features & Use Cases

  • Orchestrates end-to-end issue lifecycle from idea to closed, invoking optional sub-skills (5.1–5.7) as needed.
  • Enforces alignment with project goals, quality attributes, and architecture considerations where applicable.
  • Generates structured issue bodies, checks for duplicates, and attaches metadata for planning and tracking.

Quick Start

Draft a new issue following the workflow guidelines and open the issue to trigger the orchestration.

Frequently Asked Questions about issue-workflow

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

FAQPage Schema
How do I automate GitHub issue creation and lifecycle management from idea to closure?

Automating GitHub issue lifecycle management involves orchestrating issue creation, refinement, validation, and drafting through coordinated workflows. This ensures consistent issue bodies with clear scope, acceptance criteria, and metadata for tracking.

Why does GitHub issue drafting often lead to misaligned work and wasted cycles?

GitHub issue drafting leads to misaligned work when drafts lack consistent scope, acceptance criteria, and traceability. Applying structured orchestration enforces alignment with project goals and quality attributes to resolve this.

What's the best way to check for duplicate GitHub issues before drafting a new one?

Checking for duplicate GitHub issues requires applying structured guidance during the issue creation workflow. This orchestration validates new ideas against existing issues to prevent redundancy before refinement begins.

How do I structure GitHub issues with clear acceptance criteria and scope definitions?

Structuring GitHub issues with clear acceptance criteria requires applying workflow guidelines that define out-of-scope boundaries, estimates, and metadata. This converts ideas into well-formed, traceable issues.

Can I enforce project goal alignment and architecture considerations during GitHub issue orchestration?

Enforcing project goal alignment during GitHub issue orchestration is supported by validating issues against quality attributes and architecture considerations. This ensures structured guidance throughout the lifecycle.