Guide

Claude.ai Running Plan — Why It Needs Your Real Training Data

Claude.ai can draft a plan in seconds, but speed is not the problem. The real question is whether the plan is grounded in your fitness, recent load, goals, and schedule.

Connect for free

Why generic Claude plans break down

A generic plan can look clean and convincing while still missing the things that make or break real training: current weekly volume, recent fatigue, realistic pace targets, race goals, and how much training you can actually fit into your life.

That is why two runners can ask Claude for “a 10K plan” and receive plans that sound equally smart, even when one is ready for threshold work and the other needs basic aerobic consistency first.

What Claude needs to build a usable plan

Your current training load

Without a real baseline, mileage progression and intensity are just guesses.

Recent workout history

Claude needs to know what you actually did last week, not what you hope you did.

Goals and rules

Race target, available days, and personal constraints change the whole structure of the week.

Your existing calendar

A useful rewrite has to look at what is already planned, not start from a blank sheet every time.

What STAS adds

STAS gives Claude your real athlete context from Intervals.icu plus the profile information you keep on stas.run. That means the plan can be built from actual training, not from templates alone.

It also makes plan work more practical: Claude can inspect the current calendar, rewrite around fatigue or schedule changes, and send the updated plan back to Intervals.icu.

Recent workouts and trends instead of manual summaries
Goals, rules, and athlete profile carried across sessions
Current plan context before rewriting the week
A direct path back into the Intervals.icu calendar

Prompt patterns that work well

These usually produce much better planning than “make me a plan.”

Build next week’s running plan from my current fitness, goals, and rules.
Look at my current plan in Intervals.icu and rewrite it for 4 workouts this week.
Review my recent workouts first, then decide whether next week should build, hold, or deload.
Rewrite my current week around fatigue and keep the race goal in focus.

Generic plan vs plan built with STAS context

Claude.ai without STAS

  • Clean output, but built from partial context
  • Easy to miss realistic volume and fatigue
  • No reliable view of what is already in the calendar
  • Harder to trust the progression week to week

Claude.ai with STAS

  • Builds from recent training and current fitness
  • Uses goals, rules, and calendar context together
  • Can rewrite instead of only generating from scratch
  • Makes it much easier to turn the answer into a real week

Related guides

Give Claude your workouts, goals, and calendar

Once Claude sees your real training through STAS, the plan becomes realistic and usable — not another polished template.

Connect Intervals.icu

No credit card required