managing-board

Orchestrate GitHub Project board planning and verification routines for architects.

2|Updated Apr 24, 2026

Search Tags:#planning #routing #decomposition #management #board #retro #intake

Ready to run

npx skills add https://github.com/PanQiWei/board-superpowers --skill managing-board

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: managing-board
Source: https://github.com/PanQiWei/board-superpowers/tree/main/archive/skills/managing-board
Command: npx skills add https://github.com/PanQiWei/board-superpowers --skill managing-board

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Use when the architect needs to plan, dispatch, or review the board — not when they are implementing a card. The Manager session orchestrates execution across a GitHub Project while preserving architectural governance and reducing cognitive load.

Core Features & Use Cases

Route architect messages to the appropriate routines (Daily, Intake, Review Queue, Retro) and surface the correct references.
Coordinate multiple Consumer sessions under a single Manager to keep attention aligned and streamlined.
Enforce governance: ensure preflight checks, design gates, and a clear triage path without engaging in code or PR creation.

Quick Start

Tell the Manager to plan today or review the board to begin a structured cycle.

Frequently Asked Questions about managing-board

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

FAQPage Schema

How do I manage GitHub Project board planning without writing code?▼

You can manage board planning without code by using a Manager session to orchestrate routines, route messages, and enforce governance across your GitHub Project workflow. It guides architects through daily planning and reviews while preventing direct coding actions.

When do I need board routing for architect intake and review routines?▼

Board routing is needed when an architect must plan, dispatch, or review tasks rather than implement cards. It routes messages to appropriate routines like Daily, Intake, Review Queue, and Retro, enforcing preflight checks and design gates.

Can I use this to coordinate multiple sessions under a single Manager?▼

Yes, you can coordinate multiple Consumer sessions under a single Manager to keep the architect's attention aligned and streamlined. This orchestration reduces cognitive load while preserving architectural governance across the GitHub Project.

How do I start a structured cycle for daily board planning or retro?▼

To start a structured cycle, instruct the Manager to plan today or review the board. This triggers the board-protocol routines, executes preflight checks, and generates kick-off prompts for daily planning, intake, review, or retro workflows.

Does this workflow allow direct PR creation or coding actions?▼

No, the workflow explicitly prevents direct coding or PR creation actions. It focuses on architectural governance, routing board-protocol routines, and ensuring design gates and triage paths are followed without engaging in implementation.

What is the best way to enforce design gates and triage paths during board review?▼

The best way to enforce design gates and triage paths is through the Manager's preflight checks and routing protocols. It guides the architect across the GitHub Project workflow, ensuring governance is preserved without direct code engagement.