SessionPlan

View saved version →

---
name: sessionplan-football-drill-creator
description: Create usable football or soccer training drills and pitch diagrams in SessionPlan when a coach asks to create, draw, design or build a specific practice. Use for rondos, arrival activities, passing or dribbling exercises, defending practices, finishing games, positional practices and small-sided games. Infer sensible setup and progressions. Do not create drills for explanations, football rules, general weekly advice or lists of training ideas unless the coach asks to turn an idea into an actual drill.
---

Turn coaching intent into a coherent practice and call `create_sessionplan_drill`.

1. Identify the objective, age, available players and goalkeepers, time, organisation and scoring. Infer sensible missing details as a competent coach would. Ask only when an ambiguity materially changes the practice. Do not ask for pitch dimensions merely because they are unspecified.
2. Design the exercise before drawing it. Count every active player; include keepers in the stated total unless the coach explicitly says otherwise. Allocate teams, rotation and rest fairly. Give clear rules, restarts, scoring and short coaching interventions. Infer an age-appropriate area; put its metre dimensions in organisation notes.
3. Read [the board contract](references/board-contract.md). Use full snapshots for frames, consistent player/ball IDs across them, meaningful coaching notes and progressions. Diagrams must agree with the exercise: a 4v2 rondo has four spaced possession players around two defenders, a keeper stands near a goal, width practices place useful wide options, and directional games show targets and direction. Include only purposeful equipment. Keep margins and marker spacing legible.
4. Use the tool schema as authoritative. Set `schemaVersion: 2`, title, objective, duration, organisation in `notes`, coaching points, classification and board frames. Use normalized pitch coordinates, not pixels: x runs between goal lines (left to right), y runs between touchlines (width). On a full pitch, put goals near x=0/1 and keepers just inside them; portrait display does not change stored axes. Do not invent ownership, publication, analytics or external URL fields.
5. Generate a new UUID `operationId` for each intended drill. Reuse the identical operation ID and arguments for a retry. Use `destination: auto` ordinarily. If the coach explicitly requests their SessionPlan account/library, use `destination: account`; follow the connection challenge instead of silently making a guest draft. Do not ask a new coach to connect an account merely to get a drill.
6. Create only when the request authorizes an actual saved drill. “What is a rondo?” needs an explanation. “Give me five ideas” needs ideas. “Draw a game for teaching width” authorizes creation.
7. On success, state the actual title, player count and frame count from the result, briefly describe the organisation, and link the returned URL as “Open the drill in SessionPlan”. For guests, explain that it opens immediately and Save & edit keeps a private editable copy. For connected users, say it is in their private library. Never claim success on an error. Explain account limits through SessionPlan's normal account workflow; preserve the guest draft.

Do not fetch external URLs, publish drills or build an embedded editor. A future edit request requires an editing capability; v1 creates new drills only.

Referenced files: 1 — file references are metadata, not package contents.