diff --git a/docs/blog/2026/03/release-0.12.0.html b/docs/blog/2026/03/release-0.12.0.html
index f9ffb6f1..f55f2cb7 100644
--- a/docs/blog/2026/03/release-0.12.0.html
+++ b/docs/blog/2026/03/release-0.12.0.html
@@ -549,11 +549,11 @@ <h2>Conclusions</h2>
 <p><img src="/cursor-rules-java/images/2026/3/subagents.png" alt="" /></p>
 <p><strong>Source:</strong> <a href="https://code.claude.com/docs/en/agent-teams">https://code.claude.com/docs/en/agent-teams</a></p>
 <p>When you talk with people using these technologies, you notice that software delivery has increased—but design and requirements gathering must keep pace on quality too. If you accelerate delivery without investing in requirements, you end up with fast products that conceal potential design flaws.</p>
-<pre><code>------------- Design phase ----------- | Planning  | ------ Delivery -----
+<pre><code>------------- Design phase ----------- | Planning  | ----- Development -----
 
 Jira / Github / Azure Devops / RedMine &gt; Plan Mode &gt; Agent Mode to deliver
 
-             EA, PO, BA, SA            |  TL, SWE  |        SWE, SE
+           EA, PO, BA, SA, TL          |  TL, SWE  |       TL, SWE, SE
 </code></pre>
 <p>Reviewing in perspective, this kind of products has improved so much the performance, now you can pick a complex feature and if the requirements are complete, the execution using techniques like <code>Plan mode</code> will help so much in the execution without the bad experience from the <a href="https://jabrena.github.io/101-cursor/v010/index.html#/10/15">past (Madrid Jug - May 2025)</a>.</p>
 <h2>Do you still have questions about the project?</h2>
diff --git a/docs/feed.xml b/docs/feed.xml
index abdd1ec3..87c7047d 100644
--- a/docs/feed.xml
+++ b/docs/feed.xml
@@ -2,7 +2,7 @@
 <feed xmlns='http://www.w3.org/2005/Atom' xml:lang='en'>
   <id>https://jabrena.github.io/cursor-rules-java/</id>
   <title>Cursor rules and Skills for Java</title>
-  <updated>2026-03-08T14:14:06+0100</updated>
+  <updated>2026-03-08T18:06:37+0100</updated>
   <link rel="alternate" type="text/html" href="https://jabrena.github.io/cursor-rules-java/" />
   <link rel='self' type='application/atom+xml' href='https://jabrena.github.io/cursor-rules-java//feed.xml' />
   <entry>
diff --git a/site-generator/content/blog/2026/03/release-0.12.0.md b/site-generator/content/blog/2026/03/release-0.12.0.md
index 0f529b8e..9df2ef8b 100644
--- a/site-generator/content/blog/2026/03/release-0.12.0.md
+++ b/site-generator/content/blog/2026/03/release-0.12.0.md
@@ -585,11 +585,11 @@ If you followed the article, the project is evolving from `System prompts` to `S
 When you talk with people using these technologies, you notice that software delivery has increased—but design and requirements gathering must keep pace on quality too. If you accelerate delivery without investing in requirements, you end up with fast products that conceal potential design flaws.
 
 ```
-------------- Design phase ----------- | Planning  | ------ Delivery -----
+------------- Design phase ----------- | Planning  | ----- Development -----
 
 Jira / Github / Azure Devops / RedMine > Plan Mode > Agent Mode to deliver
 
-             EA, PO, BA, SA            |  TL, SWE  |        SWE, SE
+           EA, PO, BA, SA, TL          |  TL, SWE  |       TL, SWE, SE
 ```
 
 Reviewing in perspective, this kind of products has improved so much the performance, now you can pick a complex feature and if the requirements are complete, the execution using techniques like `Plan mode` will help so much in the execution without the bad experience from the [past (Madrid Jug - May 2025)](https://jabrena.github.io/101-cursor/v010/index.html#/10/15).