hire-guide
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".
Best use case
hire-guide is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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".
Teams using hire-guide should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/hire-guide/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How hire-guide Compares
| Feature / Agent | hire-guide | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Hire Guide Interactive guide for hiring BotMinter team members. Walks the operator through role selection, name choice, and explains what happens when a member is hired. ## How Hiring Works When the operator runs `bm hire <role> --name <name> -t <team>`: 1. The role is validated against the team's profile 2. A member directory is created at `<team-path>/team/members/<name>/` 3. The role's member skeleton is copied (ralph.yml, PROMPT.md, CLAUDE.md, hats, skills, knowledge) 4. The member is registered in the team configuration 5. After hiring, `bm teams sync` provisions the workspace ## Guiding the Operator ### Step 1: Identify Available Roles Read the team's profile manifest to list available roles: ```bash # If the operator has a team cat <team-path>/team/botminter.yml ``` Or use the CLI: ```bash bm roles list -t <team> ``` If no team exists yet, browse profiles to show what roles are available: ```bash bm profiles list bm profiles describe <profile> ``` ### Step 2: Explain Each Role For each available role, explain: - **What it does** — the role's responsibilities from the profile description - **What it gets** — hat collection, skills, knowledge files - **When you need it** — scenarios where this role adds value Read the role skeleton for details: ```bash ls ~/.config/botminter/profiles/<profile>/roles/<role>/ cat ~/.config/botminter/profiles/<profile>/roles/<role>/ralph.yml ``` ### Step 3: Help Choose a Name Member names must be: - Lowercase alphanumeric with hyphens - Unique within the team - Descriptive (e.g., `lead-architect`, `frontend-dev`, `docs-writer`) Suggest names based on the role and team composition: - First member of a role: use the role name (e.g., `architect`) - Multiple members in same role: add a qualifier (e.g., `backend-dev`, `frontend-dev`) - Specialized focus: reflect the specialization (e.g., `api-architect`, `test-engineer`) ### Step 4: Confirm and Execute Show the operator the exact command: ```bash bm hire <role> --name <name> -t <team> ``` After hiring, remind them to sync: ```bash bm teams sync -t <team> ``` ## Handling Edge Cases ### No Teams Configured If `~/.botminter/config.yml` does not exist: > No teams registered yet. Before hiring, create a team with `bm init`. ### Role Already Filled Multiple members can have the same role. Explain that each gets an independent workspace and Ralph Orchestrator instance. ### Unknown Role If the operator asks about a role not in the profile: > That role isn't available in the `<profile>` profile. Available roles are: <list>. > Roles are defined by the profile. To add custom roles, modify the profile. ## CLI Quick Reference | Task | Command | |------|---------| | List available roles | `bm roles list -t <team>` | | Hire a member | `bm hire <role> --name <name> -t <team>` | | List current members | `bm members list -t <team>` | | Show member details | `bm members show <member> -t <team>` | | Sync after hiring | `bm teams sync -t <team>` |
Related Skills
workspace-sync
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).
team-design
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.
role-management
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.
retrospective
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.
process-evolution
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.
member-tuning
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.
cos-session
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.
github-project
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
workspace-doctor
Diagnoses common BotMinter workspace issues — stale submodules, broken symlinks, missing files, outdated context, and sync problems. Use when the operator asks to "check my workspace", "diagnose issues", "why isn't X working", "fix my setup", "workspace health", or "something seems wrong".
team-overview
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.
profile-design
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.
profile-browser
Browses and describes BotMinter profiles — team methodology templates that define roles, statuses, coding agents, and process conventions. Use when the operator asks to "list profiles", "show profiles", "what profiles are available", "describe a profile", "what roles does X have", or "compare profiles". Reads ~/.config/botminter/profiles/.