Every club says it does player development plans. Most do them at pre-season, file them, and never look at them again. The reason isn't lack of will — it's that the format doesn't survive the season. A Claude Project per player turns the development file into something you can actually query: 'What were the three things we agreed on with [player] in pre-season? Are we on track?' Tier: Claude Pro (Free is capped at 5 projects total).
A memory tool, not a notes tool. The distinction matters.
This upgrades the Memory layer at the individual level. A development plan is only as useful as the rate at which you actually re-engage with it. Project Knowledge holds the plan, the GPS exports, the previous review notes, the injury history — and Claude reads them on every prompt.
It removes the 'where is that document' load and the 'I should re-read their plan before the 1:1' load. Both happen at the same time, and both go away.
Set up at the start of the season for your starting XV plus 5 development priorities — that's 20 projects, well within Pro's unlimited cap. Update Knowledge after each formal review (monthly or quarterly). Use the project before every 1:1, every contract conversation, every injury return-to-play decision.
Three steps. Twelve minutes total.
- Step 01
InstallDecide which players get a project. Realistically: starting XV + 3–5 development priorities. Don't make 40 projects — you won't maintain them. In Claude, create a new project per player: 'Player — [First name] [Surname]'. - Step 02
Use oncePopulate Project Knowledge for each player: pre-season individual development plan, last 3 months of GPS data exports (CSV is fine), any review notes from previous coaching staff, any injury history if relevant. Add the Project Instructions prompt below — this tells Claude how to talk about the player. - Step 03
StoreUse it. Before every 1:1, ask: 'What were the three priorities we set with [player] in pre-season? Looking at their data and notes since, where are they on each one?' Before contract talks, ask: 'Pull a 5-bullet performance summary I can take into this conversation.'
3 prompts, one unlocked.
You are a coaching assistant focused on the development of one specific player: [PLAYER NAME], [POSITION]. Their development plan, GPS data, review notes, and injury history are in Project Knowledge. Behaviour rules: - Always ground recommendations in the actual data and notes — no generic advice. - When I ask 'how are they doing on X' check the development plan for what X means specifically for this player, then check the data. - If something is missing from Knowledge that I should add (e.g. 'I don't see any notes from the last review'), tell me. - Don't sugar-coat. If the data shows they're behind on a target, say so plainly. The point is the player improves, not that I feel comfortable. - Use British English. Use S&C / coaching language, not management consultancy.
Member-only prompt — click to unlock.
Member-only prompt — click to unlock.