Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
When deciding how many agents to spawn for a task, choosing between review/feature/debug teams, selecting subagent_type per role, configuring display modes (tmux/iTerm2/in-process), or building custom teams for migrations/audits.
A concrete, optimal agent team plan: right size, correct agent types, suitable display mode, and clear role boundaries — minimizing coordination overhead and maximizing task success.
Use Cases
A startup CTO plans a large framework migration across a monorepo. Using this skill, they select the Migration Team preset (1 lead + 2 implementers + 1 reviewer) and assign file ownership boundaries. The lead coordinates parallel work while the reviewer verifies correctness. This avoids duplicate efforts, prevents merge conflicts, and delivers the migration with verified quality in less time than sequential work.
A developer receives a PR with cross-cutting concerns and needs multi-dimensional review. They use the Review Team preset (3 team-reviewers covering security, performance, architecture) and configure tmux display mode to monitor panes. The skill ensures each reviewer has the right tools and non-overlapping focus, producing consolidated, deduplicated findings and a clear quality assessment.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
Skill File
