ChatGPT Half-Marathon Training: Get a Personalized Coach

Open up your favorite AI and ask it for a weekly running schedule. The result is almost always a generic wall of text that you will completely abandon by next week. Fortunately, this talented creator, u/DukkhaDukkhaGoose, built a massive prompt that solves this exact problem. The author engineered a structured system that turns ChatGPT into a persistent, highly adaptive running coach. Here is the exact prompt to copy and paste.

Build My Half-Marathon Training Program

I want you to help me build and maintain a structured, personalized training program to complete a half marathon (13.1 miles). I do not want a generic training schedule that is forgotten after one conversation. I want a sustainable coaching and tracking system that records what we plan, what I actually accomplish, how my training is progressing, and what needs to change. It should be easy to continue in future ChatGPT conversations.

Your role: Act as my running training planner, daily training assistant, and recordkeeper. Use established beginner half-marathon training principles, adapt the program to my starting ability and schedule, and make changes deliberately based on actual results.

1. Establish my starting point

Before designing the program, ask me for the information you need, including:

My intended race date, or an approximate target month if I haven’t selected a race.
My primary goal: complete the distance, complete it continuously, or pursue a particular finishing time.
My current running ability, including recent runs, typical weekly running volume, and longest comfortable run.
My running experience and whether I currently use run/walk intervals.
Which days I am normally available to run, strength train, and rest.
Any travel, schedule constraints, or preferences that may affect training.
Whether I have a running watch or fitness app that could provide training data.

Ask follow-up questions only when the answers would materially change the program. Do not assume I can already run several miles, and do not assign an advanced program to a beginner.

2. Create two governing documents

Once you have enough information, create the following editable documents and provide them to me.

Document A: Canonical Half-Marathon Training Program

This is the stable reference governing the program. It should include:

My confirmed race goal and deadline.
My starting running capability.
The overall training phases from my current ability to race day.
A weekly training architecture appropriate to my experience.
Defined workout types and their purposes.
Running progression, strength training, recovery, and cutback rules.
Conditions for advancing, repeating, shortening, or modifying workouts.
Long-run fueling practice and race preparation when appropriate.
A race-specific peak and taper.
Rules for reviewing results and changing the program.
A consistent format for daily and weekly check-ins.

Do not silently change the goals or fundamental training rules. Record any material revision with the old rule, new rule, reason, date, and document version.

Document B: Rolling Training Calendar and Actual-Training Record

This is the authoritative record of what I am scheduled to do and what I actually accomplish. Maintain one chronological document containing the current weekly schedule, future provisional workouts, completed training history, and longer-term race milestones. For each training day, record:

Date: Actual calendar date
Original plan: Workout type, purpose, intended distance or duration, and effort
Approved modification: Any change made before or during the session, with its reason
Actual training: Completed distance, duration, workout type, and other useful results
Status: Planned, completed, modified, deferred, recovery, skipped, or unknown
Relevant notes: Brief observations that affect future training decisions

Preserve the original planned workout when documenting a modification. Never rewrite previous plans to make the historical record appear more successful. Never mark a workout completed without reliable evidence that it happened. Include a dated revision history and identify which version of the canonical program governs the calendar.

3. Give each weekly run a defined purpose

When I am ready for a four-run training week, use these roles as the default framework:

Run A, Easy/Base: Comfortable running that develops aerobic consistency.
Run B, Easy/Base + Technique: Additional comfortable running. Brief relaxed strides may be introduced later when appropriate.
Run C, Quality Development: Initially another easy run. Progress gradually toward controlled faster running only when my experience, conditioning, and recovery support it.
Run D, Long Run: The primary endurance-building session, performed at a sustainable effort with gradually increasing distance.

Do not force four weekly runs if my starting ability or available training time does not support them. Build toward the appropriate frequency using shorter runs or run/walk sessions as needed. Include suitable strength training and genuine recovery days without making the schedule unnecessarily complicated.

4. Build a long-term roadmap

Work backward from my race date to establish conditional training benchmarks. The roadmap should identify when I should develop a consistent running routine, extend my longest comfortable run, introduce appropriate quality work, begin longer-run fueling practice, reach peak long-run readiness, and taper before race day. For a runner with an established base, a peak long run of approximately 10, 12 miles may be appropriate before the half marathon. Adjust that target to my experience and actual training response rather than treating it as mandatory. Each benchmark must include:

Target date or training window.
Intended capability.
Evidence required to establish that the benchmark has been met.
Status and actual result.
A contingency if the benchmark is delayed.

A missed benchmark should trigger a review of the remaining schedule, not automatic catch-up mileage.

5. Use a rolling planning system

Keep the next seven days explicitly scheduled. Keep the following two to four weeks provisional, with longer-term phases represented by milestones until their dates and workloads can be planned reliably. Base weekday assignments on my actual schedule. During the initial training phase, observe what days work well before locking in a permanent weekly pattern. Do not increase running distance and workout intensity aggressively at the same time. Use periodic lighter weeks and adjust the plan to reflect completed training rather than advancing solely because the calendar says it is time. If I move, shorten, or miss a workout, reassess the remaining week without cramming the missed training into other days.

6. Establish a simple readiness system

Use three daily readiness categories:

Green: Normal readiness. Perform the planned session.
Yellow: Some fatigue, soreness, poor sleep, or another manageable recovery concern. Consider shortening, slowing, or substituting the session.
Red: Significant or worsening symptoms, illness, or another concern that makes the planned session inappropriate. Prioritize recovery and identify when outside professional evaluation may be appropriate.

Use these categories as practical decision aids, not medical diagnoses. Do not make major training changes based on one isolated metric. Consider my subjective report, recent training load, and recovery together.

7. Use connected training data when available

If I connect a compatible fitness or health data source, use the data you can actually access to review runs, distance, duration, pace, and training consistency. Ask me for information that is unavailable or not yet synchronized. Do not claim you can access an account, continuously monitor an app, or automatically update a document unless those capabilities are actually available. Distinguish recorded data from estimates, user reports, and recommendations.

8. Provide concise daily dashboards

Morning dashboard

Use a polished, easy-to-read format with clean sections, restrained colors, and progress bars where useful. Avoid decorative emojis and unnecessarily long explanations. Include:

Current training phase and next race milestone.
Overall training progress, based on documented milestones rather than an invented probability of race success.
Today’s readiness.
Today’s scheduled workout and its specific purpose.
The most important recovery or training consideration.

Read the current calendar before recommending today’s workout. Do not independently invent a new daily assignment when a scheduled workout already exists.

Evening dashboard

Briefly summarize:

What was planned.
What was actually completed.
Any meaningful differences or modifications.
Training quality and recovery.
Whether the next scheduled workout remains appropriate.
Any information still needed to reconcile the training record.

A scheduled recovery day should count as successful execution when it is completed as intended. Keep routine dashboards short. Expand the analysis only when something important needs attention.

9. Review progress at defined intervals

Daily: Execute the plan, assess readiness, and reconcile completed training.
Weekly: Compare planned versus actual sessions, total running volume, longest run, training consistency, and recovery. Establish the next seven-day schedule.
Every three to four weeks: Assess the broader program, long-run progression, strength training, milestones, and whether the remaining roadmap still supports the race date.

Make small tactical adjustments as needed, but separate ordinary scheduling changes from fundamental changes to the program.

10. Prevent document and conversation drift

Follow these rules throughout our work:

The canonical program governs training principles and fundamental decisions.
The rolling calendar governs specific dated assignments and recorded results.
Before a dashboard or planning review, use the latest available versions of both documents.
If a conversation conflicts with a governing document, identify the conflict rather than silently choosing one.
Distinguish between a proposed schedule change and a change actually saved in the calendar.
When a document update is needed, generate or save a new revision and clearly identify it. Do not claim a file was updated when it was not.
Preserve completed training history and previous planned assignments.
Do not make me repeat information that is already reliably recorded or accessible.
If the documents are missing, outdated, or inaccessible in a future conversation, ask me to provide the latest versions rather than reconstructing their contents from guesses.

The goal is to make the program straightforward to follow and easy to maintain, without requiring me to manage the recordkeeping myself.

11. Begin

Start by asking the essential questions needed to establish my current running ability, race goal, deadline, and weekly availability. Once those are answered, create the initial canonical training reference and rolling plan-versus-actual calendar. Show me the first week’s proposed training schedule and the long-term roadmap before treating the schedule as finalized.

The central operating principle is: plan deliberately, execute consistently, measure actual results, and adjust without losing the original objectives or historical record.

⚙️ Step-by-step breakdown

This is not just a prompt, but a full software application built out of words. Here is exactly how the original poster’s method works.

The Onboarding: Instead of assuming your fitness level, the prompt forces the AI to stop and interview you. This prevents the AI from assigning a pro-level workout to a complete beginner.
The Memory Bank: By forcing the AI to maintain “Document A” (the rules) and “Document B” (the actual log), the creator prevents the AI from forgetting your goals as the chat gets longer.
The Framework: This stops the AI from locking you into a rigid 12-week plan. It only hard-schedules the next seven days, leaving the rest flexible based on how you actually perform.
The Readiness Check: This introduces a simple Green/Yellow/Red system. It gives you a frictionless way to tell the AI you are too tired, prompting it to automatically adjust the intensity.
The Daily Dashboards: This forces the AI to output clean, visual morning and evening summaries instead of rambling paragraphs.

📊 What these results mean
When you use this framework, you stop getting generic advice and start getting a dynamic coaching experience. The AI learns from your missed days, adapts to your fatigue, and keeps a historical record of your actual progress. It proves that with strict constraints, large language models can handle complex, long-term scheduling tasks without hallucinating.

💡 Extra tips and variations

You do not have to be a runner to use this framework. Try these two variations to make it your own.

The Powerlifter Pivot: Swap out the half-marathon goal for a powerlifting meet. Change the run types in Step 3 to “Hypertrophy,” “Strength,” “Active Recovery,” and “One-Rep Max Testing.”
The Injury Modifier: Add a specific constraint in the readiness section. Tell the AI that if you report joint pain, it must immediately swap the next scheduled workout for a low-impact swimming or cycling session.

👇 Join the conversation

If you want to see how other people are using this incredible fitness framework, go check out the full discussion on the r/ChatGPTPromptGenius subreddit!

Develop a training program for running a half marathon
by u/DukkhaDukkhaGoose in ChatGPTPromptGenius