Menu
Build staffing plans for pure-soul agents, mixed soul+skill agents, and skill attachments
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Safely edit an existing Agent Hub asset with asset-type-specific checks and follow-up verification.
Create or revise the core assets for an Agent Hub agent, including soul, bundle, and optional profile.
Draft or update a portable Agent Hub skill with clean frontmatter and a practical workflow.
Use when implementation is complete on a normal feature branch and you need to verify, clean up commits, rebase, and either merge locally or create a PR without using a worktree-heavy workflow.
Use after implementing a feature, fixing a bug, or reaching a wave checkpoint when you need to actively test the behavior by running the app, exercising the flow, and confirming the change actually works.
Use when you have a written implementation plan to execute in a separate session with review checkpoints
| name | hr-staffing |
| description | Build staffing plans for pure-soul agents, mixed soul+skill agents, and skill attachments |
| audience | HR planner subagent |
| license | MIT |
| compatibility | opencode >= 0.1 |
| metadata | {"domain":"agent-staffing","version":"1.0"} |
Produce a staffing plan that is advisory, explicit, and downstream-compatible with Agent Hub composition.
This skill must not be invoked until the parent HR agent has completed Stage 1 - REQUIREMENTS and the user has confirmed the requirements summary. If requirements are still ambiguous, return that gap to the parent instead of pretending the plan is ready.
Write the latest plan to:
$HR_HOME/state/staffing-plans/latest.json$HR_HOME/state/staffing-plans/latest.mdEvery staffing plan must include:
schema_versiontask_summaryrecommended_teamalternativescompositionrequired_skillsrequired_toolsdraft_names (draft agent names and draft profile name for user review)risksteam_size_advisory (included when recommended team exceeds four agents)next_actionKeep latest.md compact and field-based. Use this shape:
recommended:
- role: ... | source: ... | agent_class: ... | model: ...
alternatives:
- ...
composition:
- ...
draft_names:
- seat: ... | proposed_agent_name: ... | reason: ...
- profile: ... | reason: ...
required_skills:
- skill: ... | why: ...
risks:
- ...
team_size_advisory: <omit if ≤4 agents; otherwise: "Recommend one to two primary agents with remaining agents as subagents.">
next_action: ...
For each recommended entry, specify:
asset_kind: agent or skillagent_class: pure-soul, mixed-soul-skill, or not-applicabledeployment_role: primary-capable, subagent-preferred, or skill-attachmentcompatibility: native-ready, needs-adaptation, or skill-onlydeployment_role: primary-capable.team_size_advisory noting that the team should be structured around one to two primary agents with the remaining agents deployed as subagents. Do not recommend more than two primary-capable agents unless the user explicitly requests it.$HR_HOME/inventory/workers/ with inventory_status = available.draft worker cards as sourcing inputs that still need review or explicit operator acceptance.retired worker cards from recommended staffing compositions.