skills.rest
PanQiWei
PanQiWeiCOMMUNITY
Explore all skills by this author →
GitHub

board-protocol

Enforce shared card schemas, state transitions, and PR templates in GitHub Projects.

2|Updated Apr 24, 2026
Search Tags:#workflow#branching#state-machine#github-projects#pr-templates#board-protocol#card-schema
One-click install
npx skills add https://github.com/PanQiWei/board-superpowers --skill board-protocol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: board-protocol
Source: https://github.com/PanQiWei/board-superpowers/tree/main/archive/skills/board-protocol
Command: npx skills add https://github.com/PanQiWei/board-superpowers --skill board-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This protocol defines a shared contract for coordinating board work between managers and consumers, ensuring predictable card states, transitions, and PR flows.

Core Features & Use Cases

  • State-machine driven card lifecycle with defined transitions.
  • Standard card body and PR templates plus a unique marker to distinguish board-superpowers items.
  • Branching, per-card worktrees, and concurrency rules to support multiple sessions without conflicts.
  • Guardrails like WIP limits and validation to prevent scope creep.

Quick Start

Apply the board-protocol to your GitHub project before decomposing cards to ensure consistent card bodies, PR templates, and transition rules.

Frequently Asked Questions about board-protocol

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

FAQPage Schema
How do I enforce a consistent state machine for GitHub Projects card transitions?▼

To enforce a consistent state machine for GitHub Projects, apply the board-protocol to define predictable card states and transitions, ensuring managers and consumers follow a shared coordination contract.

What is the best way to standardize PR templates and card schemas for board workflows?▼

Standardizing PR templates and card schemas requires applying a shared contract before decomposing cards, implementing required bodies, unique markers, and transition rules to distinguish board items.

Can I support multiple concurrent work sessions on the same GitHub Project board without branch conflicts?▼

Yes, you can support multiple concurrent sessions using per-card worktrees and defined branching concurrency rules, which prevent conflicts and maintain predictable PR flows across sessions.

How do I prevent scope creep and validate branch naming rules in GitHub Issues workflows?▼

Preventing scope creep and validating branch naming rules involves applying protocol guardrails like WIP limits and validation checks to enforce contract compliance across GitHub Issues workflows.

When should I apply a coordination protocol to my GitHub Projects workflow?▼

You should apply a coordination protocol before decomposing any cards in your GitHub project, ensuring consistent card bodies, PR templates, and transition rules are established from the start.

Related Skills

Explore More Software Engineering Skills→
tomzxtomzx
5

onboard-repository

Bootstrap repository onboarding with SDLC structure and automated issue triage workflows.

Community
Advanced
bybren-llcbybren-llc
395

release-patterns

Automate PR creation, CI validation, and release coordination in rebase-first workflows.

Official
Intermediate
TencentCloudBaseTencentCloudBase
1.1k

git-workflows

Standardize git delivery workflows with conventional commits and GitHub Actions triage.

Official
Advanced
akiojinakiojin

gh-pr

Automates GitHub PR creation and updates using gh CLI with merge-aware logic.

Community
Advanced