5 AI Prompts Every Amateur Athlete Should Have Saved

Five copy-paste-ready AI prompts for amateur athletes — covering macrocycle design, weekly microcycle rebuilds, intensity auditing, injury interruption planning, and taper design.

The quality of AI-assisted training planning lives or dies on prompt quality. A vague request produces a generic plan that could apply to anyone. A specific, contextualized prompt produces something you can actually use.

These five prompts cover the core planning conversations every amateur athlete needs. Copy them, fill in the brackets, and save them somewhere accessible.


Prompt 1: The Macrocycle Architect

Use this at the start of a training season to establish the full arc from today to your target event.

I'm training for [EVENT: distance + type] on [DATE]. 

Current training: [X miles / hours per week across N days].
Recent performance baseline: [most recent race result OR estimated threshold pace OR power output].
Injury history: [any recurring issues in the past 12 months].
Weekly constraints: [fixed rest day, days with hard time limits, travel weeks you know about].
Goal: [finish / specific time / specific outcome].

Build me a [N]-week macrocycle with distinct phases. For each phase, include:
- Duration (weeks)
- Dominant adaptation goal
- Weekly volume range
- Key session types
- Recovery week placement

Flag any assumption you're making that I should verify.

Prompt 2: The Microcycle Rebuild

Use this every Sunday evening or Monday morning. It is the most frequently used prompt in the system.

MESOCYCLE CONTEXT: I'm in week [N] of a [TOTAL]-week [MESOCYCLE TYPE, e.g., threshold development] block. Target weekly volume: [X]. Key session types this phase: [e.g., 2 easy runs, 1 tempo, 1 long run].

LAST WEEK — PLANNED vs ACTUAL:
[List each planned session and what you actually did. Note any pain, soreness, or fatigue.]

THIS WEEK CONSTRAINTS:
[Any days unavailable, hard time limits on sessions, travel, anything else relevant.]

REBUILD REQUEST:
Please rebuild this week's microcycle within the mesocycle's parameters, accounting for last week's actual output. If last week included missed sessions, tell me whether to absorb the missed volume, redistribute it, or skip it and move forward.

Prompt 3: The Intensity Auditor

Use this weekly, alongside your microcycle rebuild, to track your polarized training distribution.

Here are my completed sessions from this week with approximate zone breakdowns:

[Session 1 — date, distance/duration, zone split (e.g., "8mi — 90% Z1-2, 10% Z3")]
[Session 2]
[Session 3]
[Session 4]

Calculate my weekly intensity distribution as percentages across:
- Low intensity (Zone 1–2 / below first lactate threshold)
- Moderate intensity (Zone 3 / grey zone)
- High intensity (Zone 4–5 / above second lactate threshold)

Compare to a polarized target of approximately 80% low / 10% moderate / 10% high. Note if grey-zone volume is accumulating above 15%.

Prompt 4: The Injury Interruption Planner

Use this when a physical symptom appears — alongside arranging a professional assessment, not instead of one.

I've had [describe symptom: location, type, when it appeared, whether it's sharp/dull/aching] for [N days]. I'm going to contact my physio to arrange an assessment.

While I wait for that appointment, I want to think through scheduling options. I'm in week [N] of a [TOTAL]-week plan, with [N weeks] until my target event.

Without diagnosing the injury, help me think through three possible scenarios:
1. I need to skip all running for 5–7 days
2. I can do modified easy running (shorter, flatter, reduced intensity)
3. It resolves in 2–3 days and I can return to normal training

For each scenario, what would the adjustment to my remaining plan look like?

Prompt 5: The Taper Designer

Use this 2–3 weeks before your target event to design a structured volume reduction.

I'm [N weeks] out from my target [EVENT: distance + type]. My peak training week was [X miles/hours]. My usual key sessions are [e.g., one tempo run, one long run per week].

Design a [2 or 3]-week taper:
- Week 1 of taper: reduce volume by approximately [30–40%], maintain one shorter quality session
- Race week: reduce volume by approximately [50–60%], easy running only, except one short race-pace segment 2–3 days before the race
- Race day falls on [DAY OF WEEK], so work backwards from there

Note: I tend to feel slow and anxious during taper (taper madness). If the plan feels conservative in the final week, that's intentional — reassure me and don't add mileage.

These five prompts handle the five highest-leverage planning conversations an amateur athlete has across a training season. Save them somewhere you can open quickly on a Sunday evening — the microcycle rebuild prompt in particular is most useful when you use it consistently, not occasionally.

Copy prompt 2 (the Microcycle Rebuild), fill in last week’s actual training, and run it this Sunday.


Tags: AI prompts for athletes, training plan prompts, AI running plan, microcycle planning, athletic AI prompts

Frequently Asked Questions

  • Can I use these prompts with any AI tool?

    Yes. These prompts are designed for general-purpose AI assistants. The key is filling in the bracketed placeholders with your actual data — generic inputs produce generic output.
  • How often should I use these prompts?

    The microcycle rebuild prompt is weekly. The intensity auditor is weekly. The macrocycle prompt is once per training season. The mesocycle and taper prompts are used at phase transitions — roughly every 4–6 weeks and 2 weeks before your target event, respectively.
  • What information do I need before using these prompts?

    At minimum: your target event date, current weekly training volume, recent performance baseline (recent race time, estimated threshold pace, or similar), and any injury history. The more specific your inputs, the more useful the output.