Build a 1600m or 5K Race Plan

Purpose

Use the RSLTS connection guide for AI tools and MCP to ask a focused race-planning question about an authorized athlete’s training and race history. Use the AlphaPeak Pace Lab to explore optimal pacing strategies. Produce a practical 1600 m or 5K plan that includes pacing, tactical options, cues, and uncertainty.

What the connection adds

An MCP connection lets an approved AI tool retrieve supported rslts context instead of relying on copied fragments. The coach still controls the question, reviews the evidence, and decides what to share. Connection does not make an AI answer automatically correct.

Race plans should combine:

• Current, recent performance rather than an aspirational time alone.

• Relevant workouts and race results.

• Athlete strengths, limiter signals, and finishing ability.

• Course, weather, competition, and championship context.

• The athlete’s pacing habits, confidence, and tactical preferences.

Deriving actionable insight

Ask one decision question at a time. “Analyze this athlete” is too broad. Better questions include:

• “What current-performance range is supported for a 1600 m next Saturday?”

• “Where has this runner tended to lose time in recent 5K races?”

• “What opening pace protects the athlete from an early fade while keeping contact?”

The final plan should include a primary plan, one faster/slower contingency, athlete-readable cues, and a post-race learning question.

75–105 minute assignment

0–15 minutes — Connect and verify. Follow the rslts MCP guide. Confirm you are accessing only the authorized athlete or cohort and that the returned context matches the intended athlete.

15–30 minutes — Frame the race. Choose 1600 m or 5K. Record current performance, target range, event date, course/track context, likely competition, and the athlete’s normal race pattern.

30–55 minutes — Query the evidence. Ask 3–5 specific questions about current fitness, recent execution, pace durability, and finishing ability. Save the answers and identify the rslts evidence behind each claim.

55–80 minutes — Build the plan. For 1600 m, specify opening 400 m, middle-race positioning, response to a surge, and final-lap cue. For 5K, specify controlled opening, middle-race rhythm, terrain or kilometer checkpoints, and finish initiation. Add a Plan B for unexpectedly fast or slow early conditions.

80–105 minutes — Athlete review. Explain the plan to the athlete without jargon. Ask the athlete to repeat the plan in their own words and select two cues they will remember.

Questions to answer

1. Which rslts evidence supports the target range?

2. What is the largest uncertainty?

3. Where is the highest risk of over-pacing or hesitation?

4. What cue will the athlete use under pressure?

5. How will the post-race review distinguish execution from fitness?

Generative AI knowledge check

Prompt 1: “Using the connected rslts context, build a 1600 m race plan for the athlete’s current performance range. Cite the training or race evidence behind every pacing recommendation, add one tactical contingency, and state uncertainty. Do not promise a finish time.”

Prompt 2: “Using the connected rslts context, build a 5K plan with opening restraint, middle-race checkpoints, terrain or pack decisions, and a finish cue. Compare even-effort and even-pace approaches.”

Prompt 3: “Audit this race plan for hallucinated facts, false precision, unsupported assumptions, and cues that are too complex to remember. Return a simpler athlete-facing version with no more than four cues.”

Deliverable

Submit the question log, evidence table, primary and contingency race plans, the athlete’s chosen cues, and a post-race review template.