botminter

Backport improvements from a running team repo to its source profile. Use when asked to "backport to profile", "upstream team changes", "harvest improvements", "reverse-sync to profile", or "/profiles-backport". Do NOT use for profile-to-team sync (workspace-sync), member config tuning (member-tuning), or process changes (process-evolution).

Migrates existing permanent BotMinter workspaces to the ephemeral session model. Initializes shared bare clones from local workspace repos so that `bm start` can create sessions without a slow remote fetch. Use when the operator asks to "migrate workspaces", "set up shared clones", "transition to sessions", or "prepare for ephemeral sessions".

Board scanning and dispatch procedure for GitHub Projects v2. Scans the project board for actionable issues, dispatches human gates to po_gate, and delegates to specialized hats via priority tables. Auto-injected into coordinator prompts.

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

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

Manages the full epic planning lifecycle using Prompt-Driven Development (PDD). Use for idea honing, requirements extraction, requirements planning, research, architectural design, adversarial review, story breakdown, feature planning, roadmap planning, and epic decomposition into stories. Also triggers on "plan an epic", "design a feature", "run PDD", or /epic-mgmt. Do NOT use for stories or tasks — use the story-mgmt skill instead.

Manages story and task lifecycle. Use for story decomposition, task generation, task planning, code task creation, story management, task management, TDD task structuring, acceptance criteria traceability, and adversarial review of task breakdowns. Also triggers on "decompose a story", "generate tasks", "break down a story", or /story-mgmt. Do NOT use for epics or feature-level planning — use the epic-mgmt skill instead.

Board scanning and dispatch procedure for GitHub Projects v2. Scans the project board for snt:* statuses and open PRs on project forks, dispatches work to pr_gate and pr_triage hats. Auto-injected into coordinator prompts.

Diagnoses and tunes individual member configurations by mapping symptoms to the responsible artifact — PROMPT.md, CLAUDE.md, ralph.yml (hats), skills, or PROCESS.md. Provides a diagnostic decision tree, inspection commands, example edits, and propagation steps for each artifact type. Use when asked to "tune a member", "fix a member", "troubleshoot a member", "member isn't working", "adjust member behavior", "member diagnostic", "why is the member doing X", or when an cos:exec:todo issue requests member tuning.

Guides a structured team retrospective examining what went well, what didn't, and produces typed action items. Outputs a retro summary to agreements/retros/. Use when asked to "run a retro", "do a retrospective", "reflect on the sprint", "what went well", "review team performance", or when an cos:exec:todo issue requests a retrospective.

Entry point for all day-2 team design operations. Routes operator intent to the appropriate sub-skill — retrospective, role-management, member-tuning, or process-evolution — and provides a unified dashboard of team design state. Use when asked to "design the team", "show me the team", "team overview", "what's our team setup", "let's evolve the team", "team health check", or when the operator's intent spans multiple team design areas.

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.

Board scanning and dispatch procedure for GitHub Projects v2. Scans the project board for actionable issues, handles auto-advance transitions, and dispatches work to specialized hats via priority tables. Auto-injected into coordinator prompts.

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

Board scanning and dispatch procedure for GitHub Projects v2. Scans the project board for snt:* statuses and open PRs on project forks, dispatches work to pr_gate and pr_triage hats. Auto-injected into coordinator prompts.

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

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

Board scanning and dispatch procedure for GitHub Projects v2. Scans the project board for po:* statuses and dispatches work to specialized product ownership hats via priority table. Auto-injected into coordinator prompts.

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

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.

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.

Diagnoses and tunes individual member configurations by mapping symptoms to the responsible artifact — PROMPT.md, CLAUDE.md, ralph.yml (hats), skills, or PROCESS.md. Provides a diagnostic decision tree, inspection commands, example edits, and propagation steps for each artifact type. Use when asked to "tune a member", "fix a member", "troubleshoot a member", "member isn't working", "adjust member behavior", "member diagnostic", "why is the member doing X", or when an cos:exec:todo issue requests member tuning.

Guides deliberate, team-wide process changes — adding or removing statuses, modifying transitions, updating review gates, and evolving the workflow lifecycle. Validates changes against the status graph before applying and records every decision as a team agreement. Use when asked to "change the process", "add a status", "remove a status", "modify the workflow", "update transitions", "add a review gate", "evolve the process", "change auto-advance rules", or when an cos:exec:todo issue requests a process change.

Guides a structured team retrospective examining what went well, what didn't, and produces typed action items. Outputs a retro summary to agreements/retros/. Use when asked to "run a retro", "do a retrospective", "reflect on the sprint", "what went well", "review team performance", or when an cos:exec:todo issue requests a retrospective.

Manages team role composition — list, add, remove, and inspect roles defined in botminter.yml. Includes impact analysis of statuses, hats, and knowledge before changes, and records every change as a team agreement decision. Use when asked to "add a role", "remove a role", "list roles", "inspect a role", "change team composition", "what roles do we have", "team structure", or when an cos:exec:todo issue requests a role change.

Entry point for all day-2 team design operations. Routes operator intent to the appropriate sub-skill — retrospective, role-management, member-tuning, or process-evolution — and provides a unified dashboard of team design state. Use when asked to "design the team", "show me the team", "team overview", "what's our team setup", "let's evolve the team", "team health check", or when the operator's intent spans multiple team design areas.

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).

Designs and troubleshoots BotMinter profiles — team methodology templates that define roles, statuses, hats, skills, and process conventions. Use when the operator asks to "design a profile", "create a new role", "fork a profile", "fix my profile", "troubleshoot profile issues", "design a process workflow", "add a hat", "customize a profile", or "validate my profile". Operates on profile templates, not live team repos.

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

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.

Diagnoses and tunes individual member configurations by mapping symptoms to the responsible artifact — PROMPT.md, CLAUDE.md, ralph.yml (hats), skills, or PROCESS.md. Provides a diagnostic decision tree, inspection commands, example edits, and propagation steps for each artifact type. Use when asked to "tune a member", "fix a member", "troubleshoot a member", "member isn't working", "adjust member behavior", "member diagnostic", "why is the member doing X", or when an cos:todo issue requests member tuning.

Guides deliberate, team-wide process changes — adding or removing statuses, modifying transitions, updating review gates, and evolving the workflow lifecycle. Validates changes against the status graph before applying and records every decision as a team agreement. Use when asked to "change the process", "add a status", "remove a status", "modify the workflow", "update transitions", "add a review gate", "evolve the process", "change auto-advance rules", or when an cos:todo issue requests a process change.

Guides a structured team retrospective examining what went well, what didn't, and produces typed action items. Outputs a retro summary to agreements/retros/. Use when asked to "run a retro", "do a retrospective", "reflect on the sprint", "what went well", "review team performance", or when an cos:todo issue requests a retrospective.

Manages team role composition — list, add, remove, and inspect roles defined in botminter.yml. Includes impact analysis of statuses, hats, and knowledge before changes, and records every change as a team agreement decision. Use when asked to "add a role", "remove a role", "list roles", "inspect a role", "change team composition", "what roles do we have", "team structure", or when an cos:todo issue requests a role change.

Entry point for all day-2 team design operations. Routes operator intent to the appropriate sub-skill — retrospective, role-management, member-tuning, or process-evolution — and provides a unified dashboard of team design state. Use when asked to "design the team", "show me the team", "team overview", "what's our team setup", "let's evolve the team", "team health check", or when the operator's intent spans multiple team design areas.

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).

Board scanning and dispatch procedure for GitHub Projects v2. Scans the project board for actionable issues, handles auto-advance transitions, and dispatches work to specialized hats via priority tables. Auto-injected into coordinator prompts.

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", "move issue

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.

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".