
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>matthelam Sitecore Blog</title>
      <link>https://matthelam-sitecore-blog.vercel.app/blog</link>
      <description>A blog documenting my trials and tribulations during my circumnavigation of the Sitecore-sphere.</description>
      <language>en-us</language>
      <managingEditor>matthewlam@aceik.com.au (Matthew Lam)</managingEditor>
      <webMaster>matthewlam@aceik.com.au (Matthew Lam)</webMaster>
      <lastBuildDate>Wed, 11 Feb 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://matthelam-sitecore-blog.vercel.app/tags/sitecoreai/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://matthelam-sitecore-blog.vercel.app/blog/the-ai-project-lifecycle-hiding-in-plain-sight-inside-sitecore-agentic-studio</guid>
    <title>The AI Project Lifecycle Hiding in Plain Sight Inside Sitecore Agentic Studio</title>
    <link>https://matthelam-sitecore-blog.vercel.app/blog/the-ai-project-lifecycle-hiding-in-plain-sight-inside-sitecore-agentic-studio</link>
    <description>Sitecore Agentic Studio follows a structured AI workflow that most people skip straight past. Here is what I found when I stopped treating it like a content generator and started looking at how the pieces actually connect.</description>
    <pubDate>Wed, 11 Feb 2026 00:00:00 GMT</pubDate>
    <author>matthewlam@aceik.com.au (Matthew Lam)</author>
    <category>sitecore</category><category>ai</category><category>agentic-studio</category><category>sitecoreai</category><category>agents</category><category>workflow</category><category>strategy</category><category>campaigns</category><category>context-engineering</category>
  </item>

    </channel>
  </rss>
