GitHub Project Board Management

Enforce GitHub Project Board workflows for issues and PRs via gh project item-edit.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/JDL440/nfl-eval --skill github-project-board-management-jdl440
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: GitHub Project Board Management
Source: https://github.com/JDL440/nfl-eval/tree/main/.squad/skills/github-project-board
Command: npx skills add https://github.com/JDL440/nfl-eval --skill github-project-board-management-jdl440

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams struggle with inconsistent task tracking across GitHub Projects, causing delays and miscommunication.

Core Features & Use Cases

  • Standardized statuses (Todo, In Progress, Pending User, Blocked, For Review, Done) to align team expectations and reporting.
  • Transition commands via gh project item-edit to move issues and PRs across stages with auditable history.
  • Use Case: teams triage new work into Todo, push active work to In Progress, resolve blockers, and mark items Done after PRs merge.

Quick Start

Move an item from Todo to In Progress using the gh project item-edit command.

Frequently Asked Questions about GitHub Project Board Management

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

FAQPage Schema
How do I automate moving GitHub project board issues between statuses?

You can automate moving GitHub project board issues between statuses using the gh project item-edit command. This enforces workflow transitions like moving tasks to In Progress before agents act or marking them Done after PRs merge.

What statuses should I use for a GitHub kanban workflow?

A standardized GitHub kanban workflow uses statuses like Todo, In Progress, Pending User, Blocked, For Review, and Done. These align team expectations for triage, active work, reviews, and blockers.

Can I enforce policy rules for issue management on a GitHub project board?

Yes, GitHub project board management can enforce policy rules like moving items to In Progress before agents act and marking them Done after PR merge. This coordinates tasks across issues and PRs with auditable history.

How do I handle blocked tasks in a GitHub project board workflow?

To handle blocked tasks in a GitHub project board workflow, move issues to the Blocked status using transition commands. This standardizes tracking for blockers until they are resolved and moved to For Review or Done.

Do I need specific dependencies to manage GitHub project boards with this approach?

No specific dependencies are required to manage GitHub project boards with this approach. It relies on standard gh project item-edit commands to move issues and PRs across stages.

What is the best way to track PR reviews on a GitHub kanban board?

The best way to track PR reviews on a GitHub kanban board is using the For Review status. Transition commands move items to this stage, ensuring auditable history before marking them Done after merge.