From migration-planner
Recommend team composition (roles, headcount, allocation, cost projections) based on the migration estimate, complexity, and timeline.
How this skill is triggered — by the user, by Claude, or both
Slash command
/migration-planner:migrate-teamThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Recommend team composition (roles, headcount, allocation, cost projections) based on the migration estimate, complexity, and timeline.
Recommend team composition (roles, headcount, allocation, cost projections) based on the migration estimate, complexity, and timeline.
Load data from MCP tools first, falling back to JSON files:
get_assessment with project_path (current working directory). Fall back to .migration/assessment.json.get_estimate with the assessment ID. Fall back to .migration/estimate.json.get_composed_heuristics with assessment ID and type: "roles". Fall back to reading skills/migrate-knowledge/heuristics/base-effort-hours.json for role definitions.get_analysis with the assessment ID. Fall back to .migration/analysis.json. Needed for active multipliers and risk data.get_client_proficiencies with the client ID (if assessment has client_id). Used to flag skill gaps and estimate adoption hours.If estimate data is unavailable from both MCP and JSON, inform the user and suggest running /migrate estimate first.
For each role referenced in the estimate's by_role breakdowns:
Per role, per phase:
headcount = ceil(rolePhaseHours / (40 * 0.8 * phaseWeeks))| Condition | Allocation |
|---|---|
| < 80h total | Contractor |
| < 160h total | Part-time |
| >= 160h total | Full-time |
| Condition | Seniority |
|---|---|
| High complexity multipliers active | Senior |
| < 40h total | Junior |
| Default | Mid |
For each role:
Aggregate across all roles for total cost projection.
Build a per-phase view showing:
Flag:
Call save_team_snapshot with:
assessment_id: The assessment IDestimate_version: The estimate version used as inputroles: Array of team role recommendationsassumptions: Key assumptions about team availability, rates, etc.cost_projection: { low, expected, high, byRole }phase_staffing: Per-phase headcount breakdownhiring_notes: Flagged observationsThe MCP tool handles versioning automatically.
Create .migration/deliverables/team-composition.json with the full team recommendation:
{
"assessment_id": "...",
"estimate_version": 1,
"generated_at": "ISO timestamp",
"roles": [...],
"cost_projection": { "low": 0, "expected": 0, "high": 0, "byRole": {} },
"phase_staffing": [...],
"hiring_notes": [...],
"assumptions": {}
}
Display a formatted team summary:
Team Composition Recommendation
═══════════════════════════════════
Based on estimate v1 | {total_hours}h total effort
Role Hours HC Allocation Seniority Rate Range
─────────────────────────────────────────────────────────────────────
Cloud Architect 320h 1 Full-time Senior $175-225/hr
DevOps Engineer 240h 1 Full-time Mid $150-200/hr
Sitecore Developer 480h 2 Full-time Senior $150-200/hr
QA Engineer 160h 1 Part-time Mid $100-150/hr
Project Manager 120h 1 Part-time Senior $125-175/hr
─────────────────────────────────────────────────────────────────────
Total 1,320h 6
Cost Projection
───────────────
Low: $180,000
Expected: $225,000
High: $275,000
Phase Staffing
──────────────
Phase 1 (Assessment): 3 people — Architect, PM, DevOps
Phase 2 (Build): 5 people — +2 Sitecore Devs
Phase 3 (Migration): 6 people — +QA
Phase 4 (Validation): 4 people — -1 Dev, -DevOps
Phase 5 (Cutover): 3 people — Core team only
Hiring Notes
────────────
⚠ QA Engineer needed for only 4 weeks — consider contractor
⚠ Client team has no Azure experience — budget for ramp-up
✓ Cloud Architect spans all phases — recommend dedicated hire
Include:
/planning/?assessment={id}&tab=teamBefore generating the team recommendation, check if the assessment has challenge_required: true. If so, call get_challenge_reviews for the estimate step. If no review exists with status passed or conditional_pass, inform the user:
This assessment requires challenge reviews before advancing. Run
/migrate challenge estimatefirst to validate estimate quality, then re-run/migrate team.
npx claudepluginhub smithdak/plugin-migration-plannerPlans organizational structure, headcount, and team design. Provides benchmarks for span of control, management layers, IC-to-manager ratio, and team size. Outputs org charts, headcount plans, and hiring roadmaps.
Model team capacity across quarters, accounting for hiring, attrition, and project work. Use when forecasting resource availability for roadmaps.
Analyzes team capacity and workload to produce utilization forecasts and resource allocation plans. Useful for quarterly planning, hiring decisions, and stress-testing project fit.