board-canon

Apply the canonical board contract for state transitions, branch naming, and WIP rules.

2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/PanQiWei/board-superpowers --skill board-canon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: board-canon
Source: https://github.com/PanQiWei/board-superpowers/tree/main/skills/board-canon
Command: npx skills add https://github.com/PanQiWei/board-superpowers --skill board-canon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides the authoritative, read-only contract for board operations in board-superpowers, enabling consistent card state transitions, branch naming, and WIP counting across teams.

Core Features & Use Cases

  • Central reference for the six-state board lifecycle, card body schema, branch naming conventions, and WIP rules.
  • Enables other skills to validate actions against the canonical contract before performing operations or audits.
  • Supports rapid onboarding by providing a single source of truth for governance and interoperability.

Quick Start

Read this guide to apply the canonical board contract before any card transitions.

Frequently Asked Questions about board-canon

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

FAQPage Schema
How do I enforce a consistent board state machine for card transitions and branch naming?

Enforce a consistent board state machine by applying the canonical board contract, which defines a six-state lifecycle for card transitions, branch naming conventions, and WIP rules. This provides a read-only reference to validate operations across all workflows.

What is the canonical board contract used for governance and WIP limit validation?

The canonical board contract is an authoritative reference that defines card body schemas, branch naming schemes, and WIP rules. It validates card bodies and state transitions to ensure consistent governance across all board operations.

How do I validate card body schema and branch naming before pull requests or audits?

Validate card body schema and branch naming by checking actions against the canonical board contract before performing operations. It acts as a central reference point for ensuring compliance during transitions, claims, PRs, and audit log trails.

Does the board contract require any dependencies to implement audit log trails?

No dependencies are required to implement the board contract audit log trails. The contract operates independently with references stored in a references directory, providing a single source of truth for governance and interoperability.

When do I need to apply the canonical board contract for board operations?

Apply the canonical board contract before any card transitions or board operations to ensure consistent state transitions and governance. It is essential for validating actions across workflows including transitions, claims, PRs, and audits.