Board scanning and dispatch procedure for GitHub Projects v2. Scans the project board for mgr:* statuses and dispatches work to the executor hat via priority table. Auto-injected into coordinator prompts.

Chief of Staff working session with the operator. Use when the operator says "chief of staff session", "cos session", "I have things to file", "let's work through some items", "I found some problems", "what's <member> doing", "let's go over the board", or brings any mix of observations, bugs, ideas, or operational concerns.

Manages GitHub Projects v2 workflows for issue tracking and project management. Use when user asks to "show the board", "view issues", "what's in [status]", "create an epic", "add a story", "create a bug", "move issue

Interactive guide for hiring team members with `bm hire`. Helps operators choose roles, pick names, and understand hiring implications. Use when the operator asks to "hire someone", "add a member", "what roles can I hire", "help me hire", "who should I hire next", or "explain the roles".

Diagnose and fix member behavior problems by identifying the responsible configuration artifact and applying targeted edits. Every significant change is recorded as a decision in `agreements/decisions/`.

Evolve the team's workflow by modifying statuses, transitions, review gates, and process conventions. Every change is validated against the status graph and recorded in `agreements/decisions/`.

Browses and describes BotMinter profiles. Profiles are team methodology templates shipped with the `bm` binary, defining roles, process conventions, status workflows, and member skeletons.

Designs, customizes, and troubleshoots BotMinter profiles at the template level. Profiles are methodology templates that `bm init` extracts into team repos. This skill works before any team exists or when a team is broken and needs fixes from outside.

Performs GitHub Projects v2 status transitions for issue workflow. Use when you need to "move issue to status", "transition status", "update project status", "set status field", or "change issue state". Handles status field mutations, GraphQL verification, and comment attribution. Works with cached board-scanner environment variables.

Conversational front door for all day-2 team design operations. Detect what the operator needs, load the right sub-skill, and pass along relevant context (recent agreements, pending action items).

Shows registered BotMinter teams, their members, roles, workspaces, and running state. Use when the operator asks to "show teams", "list teams", "who is on the team", "team status", "show members", or "what teams do I have". Reads ~/.botminter/config.yml and workspace directories.

Diagnoses common BotMinter workspace issues. Runs checks against team workspaces and reports findings with suggested fixes.

Sync and diagnose BotMinter workspaces. Use when the operator says "sync workspaces", "apply profile changes", "propagate changes", "update all workspaces", "check workspace health", "diff against profile", "full sync", "my workspace has old files", or "why is the workspace out of date". Do NOT use for member behavior/config tuning (use member-tuning) or structured process changes (use process-evolution).