<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Mat Leal</title>
    <description>The latest articles on DEV Community by Mat Leal (@mat_leal_54019661bc21ab55).</description>
    <link>https://dev.to/mat_leal_54019661bc21ab55</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4078168%2Fd4e78dcb-aa6f-4c1c-9912-0a206b305c35.png</url>
      <title>DEV Community: Mat Leal</title>
      <link>https://dev.to/mat_leal_54019661bc21ab55</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mat_leal_54019661bc21ab55"/>
    <language>en</language>
    <item>
      <title>I built Mosaic, a local planning studio that makes Codex output reviewable</title>
      <dc:creator>Mat Leal</dc:creator>
      <pubDate>Fri, 14 Aug 2026 20:18:28 +0000</pubDate>
      <link>https://dev.to/mat_leal_54019661bc21ab55/i-built-mosaic-a-local-planning-studio-that-makes-codex-output-reviewable-dj1</link>
      <guid>https://dev.to/mat_leal_54019661bc21ab55/i-built-mosaic-a-local-planning-studio-that-makes-codex-output-reviewable-dj1</guid>
      <description>&lt;p&gt;I’m Matheus, the maker of Mosaic.&lt;/p&gt;

&lt;p&gt;While building products with agents, I wanted the planning work to leave behind more than a useful chat transcript. Product decisions should remain inspectable, revisable, and explicit before implementation begins.&lt;/p&gt;

&lt;p&gt;Mosaic is my attempt at that workflow. Its current &lt;strong&gt;Plan Studio&lt;/strong&gt; alpha runs locally on Apple Silicon Macs and works with a compatible Codex installation.&lt;/p&gt;

&lt;p&gt;A Plan can contain:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;durable Brief, Requirements, Architecture, UX, Test Scenario, and Delivery Plan documents&lt;/li&gt;
&lt;li&gt;self-contained interactive HTML prototypes&lt;/li&gt;
&lt;li&gt;comments anchored to documents or individual prototype elements&lt;/li&gt;
&lt;li&gt;candidate diffs and validation results&lt;/li&gt;
&lt;li&gt;immutable revisions after explicit approval&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The core loop is: ask Codex to revise a Plan, inspect the candidate changes, comment or discard them, and approve only the version worth preserving.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzf7zu9tbxc62vxvleswi.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzf7zu9tbxc62vxvleswi.webp" alt="Mosaic Plan Studio showing Codex chat, product documents, revision controls, and an interactive HTML prototype" width="800" height="501"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Plan-scoped Codex chat, product documents, and a working HTML design in one workspace.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;This is a deliberately limited alpha. It is free to evaluate, unsigned and not notarized, has no cloud sync, and does not yet implement code or handle deployment. Generated artifacts still require human review.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://mosaic-site-wine.vercel.app/" rel="noopener noreferrer"&gt;https://mosaic-site-wine.vercel.app/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you tried this on a real feature, which review checkpoint would matter most before implementation: document diffs, prototype comments, validation results, or approval history?&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>ai</category>
      <category>productivity</category>
      <category>openai</category>
    </item>
  </channel>
</rss>
