<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Roadmap on Start AI Tools - Presented by Intent Solutions</title><link>https://startaitools.com/tags/roadmap/</link><description>Recent content in Roadmap on Start AI Tools - Presented by Intent Solutions</description><generator>Hugo</generator><language>en-US</language><copyright>Intent Solutions. All rights reserved.</copyright><lastBuildDate>Sat, 18 Apr 2026 22:44:05 -0500</lastBuildDate><atom:link href="https://startaitools.com/tags/roadmap/index.xml" rel="self" type="application/rss+xml"/><item><title>Four Primitives, Three Reviews: How a Contributor PR Reshaped a Roadmap</title><link>https://startaitools.com/posts/collaboratively-shaped-roadmap/</link><pubDate>Sat, 18 Apr 2026 08:00:00 -0500</pubDate><guid>https://startaitools.com/posts/collaboratively-shaped-roadmap/</guid><description>&lt;h2 id="tldr"&gt;TL;DR&lt;/h2&gt;
&lt;p&gt;&lt;code&gt;claude-code-slack-channel&lt;/code&gt; v0.4.0 shipped Casey Margell&amp;rsquo;s &lt;code&gt;allowBotIds&lt;/code&gt; PR on 2026-04-18. The merge forced a direction question the roadmap hadn&amp;rsquo;t yet answered: with peer bots now able to deliver into the channel, what is the project &lt;em&gt;becoming&lt;/em&gt;? Four issues were filed in response — thread-scoped sessions (#32), a declarative policy engine (#29), a threaded action journal (#30), and a bot-manifest protocol (#31). Before writing a single line of code, the project ran the four proposals through prior-art research and three independent review passes. The reviews converged on a narrower v0.5.0 than the issues proposed: ship #32 first, then #29, defer #30 with a reframed scope, push #31 to a later release conditional on external signals. This post is a case study in that process — not the roadmap itself, but how the roadmap got reshaped.&lt;/p&gt;</description></item></channel></rss>