using-board-superpowers

To route Claude Code sessions, this Skill acts as a gatekeeper by performing preflight dependency checks and role disambiguation. It determines whether to bootstrap a project or hand off the session to the appropriate sub-skill for deterministic routing.

Board Manager and Board Consumer roles govern workflow routing decisions based on user intent. This Skill disambiguates these roles during a session to ensure the correct sub-skill is triggered for board management versus consumer interactions.

Your board-superpowers workflow fails because preflight checks enforce dependency verification and fail loudly if requirements are missing. This gating mechanism ensures deterministic handoffs by preventing sessions from proceeding without required components.

You need a one-time bootstrap setup to initialize project routing and labels before starting board management tasks. This optional preflight step ensures deterministic handoffs and proper session routing for subsequent board-superpowers interactions.

The best way to enforce preflight checks for Claude Code project routing is using a gatekeeper Skill that verifies dependencies via scripts and disambiguates roles. This approach guarantees deterministic handoffs and prevents missing dependency failures.