project-workflow-patterns

Design standardized GitHub Projects V2 workflows for Agile Scrum, Kanban, and Bug Triage.

9|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/yebot/rad-cc-plugins --skill project-workflow-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-workflow-patterns
Source: https://github.com/yebot/rad-cc-plugins/tree/main/plugins/github-project-manager/skills/project-workflow-patterns
Command: npx skills add https://github.com/yebot/rad-cc-plugins --skill project-workflow-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing effective workflows for GitHub Projects V2 can be challenging, leading to inefficient team collaboration and unclear project tracking. This skill provides proven workflow patterns for various methodologies, helping you optimize processes and achieve project success.

Core Features & Use Cases

  • Agile Scrum Workflow: Implement structured sprint planning, daily standups, and reviews with clear project structures and success metrics.
  • Kanban Continuous Flow: Establish a pull-based system with WIP limits, lead time tracking, and continuous delivery for flexible development.
  • Bug Triage & Feature Roadmap: Manage bug resolution with severity-based prioritization and plan long-term feature development with clear roadmaps and launch tracking.

Quick Start

To set up an Agile Scrum workflow, ask the skill to "Outline the project structure and workflow steps for an Agile Scrum team using GitHub Projects, including recommended fields and views."

Frequently Asked Questions about project-workflow-patterns

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

FAQPage Schema
How do I set up an Agile Scrum workflow in GitHub Projects?

An Agile Scrum workflow in GitHub Projects structures sprint planning, daily standups, and reviews using predefined fields like Status, Priority, and Story Points. Set up a Sprint Board view, configure automated transitions between Backlog, In Progress, and Done, and define standardized steps: Backlog Refinement, Sprint Planning, Development, Review, Verification, and Closure for measurable iteration tracking.

What's the difference between Kanban and Scrum workflows for GitHub Projects?

Kanban establishes continuous flow with work-in-progress limits and lead time tracking, pulling work as capacity allows. Scrum uses time-boxed sprints with planned iterations and velocity metrics. GitHub Projects supports both: use a Flow Board with WIP limits for Kanban, or a Sprint Board with sprint cycles for Scrum, depending on your team's delivery cadence.

How do I implement bug triage workflows in GitHub Projects?

Bug triage workflows use severity-based prioritization and a Triage Queue view to manage resolution. Configure Status fields (New, Triaged, In Progress, Resolved) and Priority levels, then automate transitions as bugs move through investigation, assignment, and closure stages for consistent resolution tracking.

Can I automate workflow transitions in GitHub Projects?

Yes, GitHub Projects V2 supports automated transitions between workflow steps. Configure rules to move items automatically based on triggers—for example, moving tasks from Backlog to Sprint during sprint planning, or from In Progress to Review when pull requests are linked, reducing manual status updates.

What project fields and views do I need for team workflow tracking?

Essential fields are Status, Priority, and Size or Story Points to support sprint planning and capacity management. Recommended views include Sprint Board for active sprints, Flow Board or Backlog for queues, and Triage Queue for bugs. These enable visibility across planning, development, and metric-driven retrospectives.

How do I measure workflow success in GitHub Projects?

Track measurable metrics: sprint velocity from Story Points, lead time from Kanban flow, bug resolution time from triage timestamps, and completion rates across sprint cycles. GitHub Projects fields and views capture this data to drive iteration improvements and team performance visibility.