designing-agent-teams
Designing Agent Teams
Generate multi-agent coding teams with optimal model assignments. Outputs a reasoning document (AGENTS.md) plus agent instruction files (.agents/) and platform-specific configs where applicable.
Determine the mode
- create-existing — Analyse an existing codebase, generate a tailored agent team
- create-new — From a project brief or tech stack, generate a starter agent team
- add — Add one or more agents to an existing team (e.g., a new dependency or cross-cutting concern)
- review — Evaluate an existing agent team config, suggest refinements
Creating for an existing codebase? → Follow "Gather inputs: existing codebase" below Starting a new project? → Follow "Gather inputs: new project" below Adding agents to an existing team? → Follow "Gather inputs: add" below Reviewing an existing team? → Follow "Gather inputs: review" below
Gather inputs
Gather what is available from the codebase and the user's request. If the user has not specified priorities, infer them from context (a solo side project likely values speed and cost; a team production app likely values quality). Do not block on missing information — use sensible defaults and note assumptions in AGENTS.md.
More from mattobee/skills
reviewing-accessibility
Use this skill to review implemented UI code for WCAG accessibility compliance. Triggers when reviewing components, pages, or templates for accessibility, auditing a feature after implementation, or answering questions about accessible patterns, ARIA, keyboard navigation, or screen reader support.
7suggesting-next-steps
Use this skill to suggest prioritised next steps for a project. Triggers when the user asks what to work on next, wants to resume after a break, or needs help prioritising a backlog.
7prioritising-accessibility-fixes
Use this skill to prioritise a set of accessibility issues for remediation based on severity, user impact, and effort. Triggers when triaging an accessibility backlog, deciding what to fix first after an audit, planning an accessibility sprint, or asking which accessibility issues matter most.
7estimating-accessibility-effort
Use this skill to estimate the effort required to remediate accessibility issues. Triggers when sizing accessibility work for a sprint, estimating how long a WCAG fix will take, scoping remediation work, or planning accessibility improvements.
7predicting-accessibility-risks
Use this skill to identify accessibility risks in a proposed feature, design, or technical plan before implementation begins. Triggers when planning a new feature, reviewing a design, assessing a technical approach for accessibility impact, or asking what could go wrong for disabled users.
7writing-accessibility-tests
Use this skill to write Playwright accessibility tests using the two-layer strategy (axe-core scans + targeted assertions). Triggers when adding accessibility test coverage, reviewing test gaps, writing axe scans, or creating Playwright assertions for accessible names, landmarks, ARIA states, focus management, or contrast.
7