By name: vgc-team-audit description: Use when a Pokemon Champions team needs a findings-first audit.
VGC Team Audit
Perform a findings-first competitive audit of a team. Preserve the identity unless the identity itself is the problem.
Inputs
- full team
- optional target concerns
- optional target matchups
- optional event or ladder context
If format is omitted, assume the current Pokemon Champions regulation and say so.
Output
Return these sections in order:
Top FindingsTeam IdentityMatchup HolesRecommended ChangesResidual Risk
Section focus
Top Findings: highest-impact structural problems first, with gameplay consequencesTeam Identity: what the team is trying to do, and whether that identity is sound or under-supportedMatchup Holes: real pressure points, not generic type-chart recapRecommended Changes: smallest useful fixes first, each tied to the exact problem solvedResidual Risk: what stays shaky after the proposed changes
Workflow
- Identify what the team is trying to do before criticizing it.
- Separate structural flaws from stylistic differences.
- Surface the highest-impact issues first.
- Tie every issue to a concrete gameplay consequence or recurring loss pattern.
- Recommend the smallest useful fixes before larger rebuilds.
- Preserve the identity unless the identity itself creates the failure.
- End with residual risk instead of pretending the team is solved.
Required behavior
- Read audit-checklist, Verification Packet, and output-rubric before finalizing.
- Use live meta verification when the audit depends on current field assumptions.
- Consume or summarize verification-packet confidence when findings depend on current field assumptions, species legality, item legality, move access, mechanics, or exact matchup claims.
- Findings first, not a compliment sandwich.
- Keep fixes concrete, proportional, and identity-preserving when reasonable.
- Do not flatten unconventional teams into generic balance or recommend a major rebuild before proving a smaller fix is insufficient.