Skip to content
TriedPrompts

More in Hobbies, Fitness & Learning.

Build a marathon training plan from 459 Strava runs with Claude

Beginner-friendlyNo logins, payments or coding needed. Low risk: paste the prompt and you should get something useful.

Copy the prompt below and paste it into the AI tool named on this page.

Prompt Improved prompt

Our fuller version of the source's prompt, or one written to avoid a problem in the source. Not tested by the poster. It doesn't change what happened in the source.

What the prompt labels mean

Before you start, ask me 1–3 short questions about the details below and wait for my answers. Once I've answered, confirm the plan in one line and run the whole task start to finish.

Goal: Analyze my running history and build a marathon plan that fits my real weekly schedule, explained in plain language.

Questions to ask me first:
- When is the race, and what's your goal time?
- Which days and times can you run each week?
- What happened in your last race or training block?

Inputs (fill in or confirm):
- Running data export (Strava, Garmin or similar): [EXPORT]
- Race date and goal: [RACE / GOAL]
- Weekly availability: [SCHEDULE]
- Injuries or limits: [INJURIES]

Rules:
- Explain what the data shows in plain words, not just charts.
- Show how much of my running falls in each pace or heart-rate zone and what to change.
- Build a week-by-week plan with recovery weeks, and say which research it's based on.
- Leave room to swap or skip sessions when family life gets in the way.

Checkpoint: Show me the analysis and plan outline before making a calendar file.

If you get stuck: If my data is missing or unclear, ask instead of guessing, and tell me when to check with a coach or doctor.

Verify before you finish: Check that weekly volume rises gradually and recovery weeks cut volume enough.

Output: A plain-language analysis, a week-by-week plan and a calendar file with sessions on the right dates.

Done when: I have a plan I understand that fits my week and is loaded into my calendar.

Try this in:

This prompt has blanks to fill in, like [EXPORT]. We'll copy it instead of filling it in, so you can edit it before you send.

The source used Claude. These are general chat tools, so results may differ.

Opens in a new tab. We don't see what you send.

These links are only a shortcut. We're not affiliated with OpenAI, Google or xAI, and your results may not match the source.

The prompt they actually used

The exact prompt from the source.

Help me analyse my performance over the past year, and use that information to plan my training for the marathon.

AI tool

Claude

Outcome

After finishing a first marathon in 4:14 with a painful final stretch, Piet van den Boer asked Claude to analyze the race and training data. Claude found that 26% of the runs sat in a 'moderate' grey zone, too hard for easy days and too easy for quality days. For the next marathon, van den Boer gave Claude a full Strava export of 459 runs from three years, plus a weekly schedule built around two young kids. Claude built a specific, flexible plan, then reviewed it against marathon research and revised it with deeper recovery weeks (20–30% instead of 10–16%), truly easy Monday runs and strides on Fridays. Early on, Claude gave generic advice and a graph-filled PDF that van den Boer found useless, and a calendar export took several tries. Van den Boer says Claude could be confidently wrong and there's no way to tell without expertise.

Evidence: Described by posterThe person describes what happened in words, without screenshots or video.

Source

Posted
by Piet van den Boer (The long run, Substack)
Last checked
Method:
How we verify

https://pvandenboer.substack.com/p/how-i-trained-for-a-marathon-with

Context: The post was written three weeks into the new plan, before the second marathon, so the result isn't known. Check with a doctor if you have an injury.

More in Hobbies, Fitness & Learning