<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Trail on Benzo.run | Practical Running Tips, Marathon Training &amp; Race Reviews</title>
    <link>https://benzo.run/tags/trail/</link>
    <description>Recent content in Trail on Benzo.run | Practical Running Tips, Marathon Training &amp; Race Reviews</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 </copyright>
    <lastBuildDate>Sat, 18 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://benzo.run/tags/trail/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>The 5 Questions to Answer Before You Ask AI for a Training Plan</title>
      <link>https://benzo.run/posts/2026-07/ai-training-plan-five-questions/</link>
      <pubDate>Sat, 18 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://benzo.run/posts/2026-07/ai-training-plan-five-questions/</guid>
      <description>&lt;p&gt;The first time I asked AI for a training plan, I wasn&amp;rsquo;t training for a marathon. I was trying to figure out how to bridge from marathon fitness into my first ultra trail block, and I wanted the plan to actually account for elevation gain, not just weekly mileage. What came back read like a marathon plan with the word &amp;ldquo;trail&amp;rdquo; swapped in: sixteen weeks, four phases, a taper, all correctly labeled. Nothing about elevation. Nothing about hiking the climbs instead of running them. It didn&amp;rsquo;t know how many miles I was running that month, or whether Saturday or Sunday was my long run day. It didn&amp;rsquo;t know that my left IT band starts complaining somewhere past 90 minutes on flat ground, let alone on descents.&lt;/p&gt;</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://benzo.run/posts/2026-07/ai-training-plan-five-questions/featured.jpeg" />
    </item>
    
  </channel>
</rss>
