Review a match or competition for a team coach: what the plan was, what happened in each phase of the game, three things that worked and three to improve, evidence from notes or stats, individual development notes kept private, and what changes in training this week. Use when asked to review Saturday's match, write a match report for the players, what should we take from this loss, analyse these match stats, or prepare my team talk for Monday. Produces a coach's review, a short player-facing version, private individual notes, and the training implications. Distinct from retro-analysis, which r
A source-grounded starter task has not been verified for this skill yet.
SKILL.md
name: match-reviewdescription: "Review a match or competition for a team coach: what the plan was, what happened in each phase of the game, three things that worked and three to improve, evidence from notes or stats, individual development notes kept private, and what changes in training this week. Use when asked to review Saturday's match, write a match report for the players, what should we take from this loss, analyse these match stats, or prepare my team talk for Monday. Produces a coach's review, a short player-facing version, private individual notes, and the training implications. Distinct from retro-analysis, which reviews a sprint."version: 1.0.0
Match Review
After a loss the temptation is to list every mistake; after a win, to learn nothing. This skill reviews performance against what the team was trying to do, keeps the result in proportion, and turns the review into next week's training. For youth teams it keeps the tone on learning and effort.
What This Skill Produces
A coach's review: plan, key moments, what worked, what to improve, with evidence
A player-facing version of half a page that starts with what went well
Private notes on individuals, phrased as development points
Two or three training implications for the coming week
One question to put to the players
Required Inputs
Ask for these if not provided:
Sport, age group, level, opposition and result
The game plan and the season's current training emphasis
The coach's notes by period or phase, and any stats or video observations
Context: availability, conditions, travel, the standard of the opposition
Who the review is for: coaching staff, players, parents, a club report
Anything sensitive: an injury, a disciplinary matter, a player in a difficult patch
Framework
Judge against the plan, not the score. Did the team do what it trained to do?
Break the game into phases: in possession, out of possession, transitions and set plays, or the equivalent for the sport.
Evidence for each point. A moment, a pattern or a number. "We lost the ball" becomes "we gave the ball away in our own half nine times, six under no pressure".
Three and three. Three things to keep, three to improve. More than that will not be remembered.
Controllables. Separate what the team controls from refereeing, luck and conditions. Mention the latter once at most.
Individuals in private. Development points go to the player one to one, framed as the next step. The team version names people only for praise.
Link to training. Each improvement point becomes a theme or a practice.
Youth tone. Effort, bravery and learning first. No public blame for a result.
Output Format
Match review: [team] v [opposition], [date], [result]
The plan: [what the team set out to do]
By phase
Phase
What happened
Evidence
Keep
[point and evidence]
Improve
[point, evidence, and the training response]
Context, once: [conditions, availability]
Player-facing version
[What we did well. What we will work on. What is next.]
Private individual notes (not for the group)
Player
Did well
Next step
Training this week: [themes or practices]
Question for the players: [one open question]
Assumptions and gaps
[What was assumed from limited notes]
[What video or stats would confirm or change]
Quality Checks
The review is measured against the plan
Every point has a moment, pattern or number behind it
There are no more than three keep and three improve points
No player is criticised by name in the team version
Each improve point links to training
Referee and luck get one mention at most
Anti-Patterns
Do not write the review in the hour after the final whistle.
Do not list every error.
Do not let the scoreline write the review. A poor win and a good loss both exist.
Do not share individual notes with the group or with parents.
Do not invent statistics to support an impression.
Example Trigger Phrases
"We lost 4-1 but played well for an hour. Help me review it honestly."
"Turn these touchline notes into a review and a Monday team talk."
"Write a short match report for the under-13s that focuses on what they did well."
"What should we train this week based on these stats?"