team-composition

Diagnose engineering team skill gaps and recommend hiring or reassignment.

104|7|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/manager-dot-dev/manager-skills --skill team-composition
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-composition
Source: https://github.com/manager-dot-dev/manager-skills/tree/main/skills/team-composition
Command: npx skills add https://github.com/manager-dot-dev/manager-skills --skill team-composition

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Engineering managers often struggle to identify missing capabilities in their teams, leading to suboptimal hiring and assignment decisions. This Skill diagnoses team skill gaps and provides concrete recommendations.

Core Features & Use Cases

  • Dungeon Party Model: Classifies engineers into Warrior, Tank, Healer, Wizard, and Rogue to reveal role gaps.
  • Barrels and Ammunition: Determines whether slow delivery is due to a lack of “barrels” (end‑to‑end owners) versus excess “ammunition.”
  • Commandos/Infantry/Police: Matches engineer types to the current product phase to explain performance mismatches.
  • Minimum Team Size: Advises on viable team size based on proven engineering principles.
  • Use Case Example: When a manager asks “What role should I hire next?” the Skill returns the most critical archetype to fill.

Quick Start

Ask the team-composition skill to evaluate my current engineering team and suggest the next hiring priority.

Frequently Asked Questions about team-composition

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify engineering team skill gaps to decide what role to hire next?

Identify engineering team skill gaps by applying diagnostic frameworks like Dungeon Party and Barrels and Ammunition to classify current engineers, reveal missing roles, and recommend the most critical archetype to hire next.

Why is my engineering team's delivery velocity slow despite having enough headcount?

Slow delivery velocity despite sufficient headcount often indicates a lack of "barrels" (end-to-end owners) versus excess "ammunition", a team balance issue diagnosed by the Barrels and Ammunition framework.

How do I match engineer types to my current product phase to fix performance mismatches?

Match engineer types to product phases using the Commandos, Infantry, and Police model to explain performance mismatches and ensure your engineering team composition aligns with current delivery needs.

What is the Dungeon Party model for engineering team composition?

The Dungeon Party model classifies engineers into Warrior, Tank, Healer, Wizard, and Rogue archetypes to reveal role gaps and diagnose missing capabilities within your engineering team.

How do I determine the minimum viable size for my engineering team?

Determine minimum viable engineering team size by applying proven engineering principles that advise on optimal headcount and role distribution for balanced, effective delivery.

When should I reassign engineers instead of hiring new team members?

Reassign engineers instead of hiring when diagnostic frameworks reveal existing team members can fill skill gaps through role optimization, addressing phase mismatches and balancing barrels and ammunition.