guild-team-compose

Map spec domains to Guild's 13 specialists and identify coverage gaps.

6|Updated Apr 24, 2026

Search Tags:#planning #yaml #gap-analysis #guild #team-composition #spec-matching

Ready to run

npx skills add https://github.com/lookatitude/guild --skill guild-team-compose

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: guild-team-compose
Source: https://github.com/lookatitude/guild/tree/main/skills/meta/team-compose
Command: npx skills add https://github.com/lookatitude/guild --skill guild-team-compose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates the selection of Guild's 13 shipping specialists for a given spec by analyzing domain coverage, surfacing gaps, and presenting concrete team options that meet governance rules.

Core Features & Use Cases

Match spec domains to the roster of Guild's shipping specialists (architect, researcher, backend, devops, qa, mobile, security, copywriter, technical-writer, social-media, seo, marketing, sales).
Classify coverage as existing or gaps and propose handling options (auto-create, skip, substitute, compose from scratch) for each gap.
Write .guild/team/<slug>.yaml with the resolved team and downstream dependencies to drive planning and execution.

Quick Start

Compose a team for the current spec by triggering the /guild:team workflow to evaluate coverage and options.

Frequently Asked Questions about guild-team-compose

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

FAQPage Schema

How do I map a project spec to a team composition for execution?▼

Mapping a spec to a team composition involves analyzing domain coverage to match the spec against 13 available specialists. It identifies existing coverage and gaps, proposing a concrete team configuration that enforces a strict six-specialist cap.

What is the best way to handle role coverage gaps when forming a project team?▼

Handling role coverage gaps involves choosing between auto-create, skip, substitute, or compose from scratch options. The skill evaluates your spec domains against the specialist roster and presents these concrete gap-handling strategies to ensure complete coverage.

How many specialists should be assigned to a single project spec?▼

A project spec should default to 3–4 specialists, with a hard maximum enforced at 6 specialists. This cap ensures manageable team composition while applying backend execution rules like defaulting to subagent execution.

When should I use subagent versus agent-team execution for my team?▼

You should use subagent execution by default for your team, switching to agent-team only when specific backend execution conditions are met. These execution rules are applied automatically during the team composition and spec-matching process.

Can I export the resolved team configuration to a YAML file?▼

Yes, you can export the resolved team configuration to a .guild/team/<slug>.yaml file. This output captures the final team roster and downstream dependencies to directly drive subsequent planning and execution workflows.