<?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>Forem: Mohammed Zameer</title>
    <description>The latest articles on Forem by Mohammed Zameer (@zameermfm).</description>
    <link>https://forem.com/zameermfm</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3799010%2F9c55d0d0-c841-4585-8a91-9a73e7970471.png</url>
      <title>Forem: Mohammed Zameer</title>
      <link>https://forem.com/zameermfm</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/zameermfm"/>
    <language>en</language>
    <item>
      <title>Giving Specs Their Own Home: Why We Built mdspec</title>
      <dc:creator>Mohammed Zameer</dc:creator>
      <pubDate>Sat, 14 Mar 2026 05:14:28 +0000</pubDate>
      <link>https://forem.com/zameermfm/giving-specs-their-own-home-why-we-built-mdspec-5g8e</link>
      <guid>https://forem.com/zameermfm/giving-specs-their-own-home-why-we-built-mdspec-5g8e</guid>
      <description>&lt;p&gt;In modern software development, our repositories are suffocating. While Git is the undisputed king of versioning code, it wasn't built for the "messy middle" of thinking. As I started building with AI agents in VS Code, Cursor, and Antigravity, one thing became clear: our current workflow for engineering specs is broken. Our repos are drowning in WIP clutter, our project histories are noisier than ever, and &lt;strong&gt;specs—which are now critical infrastructure for AI-driven development—are often duplicated, scattered, and lost.&lt;/strong&gt; I built mdspec to remove this "Repository Pressure" and give our specs their own home.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Problem: Repository Pressure
&lt;/h2&gt;

&lt;p&gt;Every developer has felt it: that hesitation before committing a half-baked idea. It’s the visual noise of 500-line Markdown files cluttering your &lt;code&gt;docs/&lt;/code&gt; folder, and the pain of cross-team coordination when a spec lives in a repository half the stakeholders can't access. When specs live strictly inside your repo, they create a bottleneck:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;WIP Clutter&lt;/strong&gt;: Your Git history gets littered with "draft" commits that add no value to the code.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fragmentation&lt;/strong&gt;: Discussions across teams become long, disconnected, and hard to track.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reuse Friction&lt;/strong&gt;: Specs are often duplicated across features or projects without tedious copy-pasting.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Most importantly, repository pressure steals our freedom to explore. It forces us to be "done" before we've even started. By moving specs to a parallel platform, we unlock the ability for both developers and AI agents to explore alternative scenarios, perform deep codebase analysis, and even prototype new tooling out of existing logic—all without the drag of repository constraints. Whether you're using an AI agent within your IDE for complex system work or manually mapping out a new architectural path, mdspec gives you the space to be messy and analytical until you're right.&lt;/p&gt;

&lt;h2&gt;
  
  
  Enter mdspec: A Parallel Universe for Your Specs
&lt;/h2&gt;

&lt;p&gt;mdspec is a specification management platform designed for AI-driven development. It is built to work &lt;strong&gt;in parallel with Git&lt;/strong&gt;, not replace it. It gives you a space to think, explore, and iterate on Markdown specs without the weight of the repository.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Clean Repos, Clear Minds
&lt;/h3&gt;

&lt;p&gt;We know specs grow exponentially. With mdspec, you can reduce repository clutter by moving your md files out of the code and onto the platform. Your repository stays lean. When you need a spec for reference or context, you pull it via the CLI. When you're done, it’s back in its home.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Durable Context for AI Agents
&lt;/h3&gt;

&lt;p&gt;AI agents perform best when they have a stable, structured "source of truth." mdspec centralizes your specs into a durable infrastructure that agents can query directly, providing the context they need to build correctly without hunting through unrelated code.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Section-Level Clarity
&lt;/h3&gt;

&lt;p&gt;To solve the problem of fragmented discussions, mdspec introduces &lt;strong&gt;Section-Level Comments&lt;/strong&gt;. Anchor your discussions, @mentions, and resolution tracking to specific sections of your spec. When feedback is anchored to the content, teams move faster without losing alignment.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Version Control Independence
&lt;/h3&gt;

&lt;p&gt;One of the core strengths of mdspec is the ability to &lt;strong&gt;go cross-team without version control dependence.&lt;/strong&gt; You can link and share specs across independent repositories—no monorepo required, no copy-pasting needed. Whether it's syncing API docs between Frontend and Backend or coordination with Compliance and Security, mdspec keeps everyone in sync regardless of their repo structure.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Native Developer Experience
&lt;/h3&gt;

&lt;p&gt;We didn't want to build "another web tool" that takes you away from your editor. mdspec is built for the terminal and the IDE:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;VS Code Extension&lt;/strong&gt;: Edit and sync specs directly from your workspace.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Robust CLI&lt;/strong&gt;: Integrate mdspec into your CI/CD pipelines or agentic automation.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The Documentation Lifecycle
&lt;/h2&gt;

&lt;p&gt;Documentation is a living thing that evolves at a different pace than your code. By treating specs as first-class citizens and giving them their own home, mdspec lets you manage that lifecycle with the same precision you apply to your software.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Stop committing doc noise. Give your specs a home.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://mdspec.dev" rel="noopener noreferrer"&gt;visit mdspec.dev&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>ai</category>
      <category>documentation</category>
    </item>
    <item>
      <title>Why AI Agents Need Specs: The Birth of MDSpec</title>
      <dc:creator>Mohammed Zameer</dc:creator>
      <pubDate>Sat, 28 Feb 2026 23:33:20 +0000</pubDate>
      <link>https://forem.com/zameermfm/why-ai-agents-need-specs-the-birth-of-mdspec-290e</link>
      <guid>https://forem.com/zameermfm/why-ai-agents-need-specs-the-birth-of-mdspec-290e</guid>
      <description>&lt;p&gt;mdspec is an open source spec management platform. &lt;/p&gt;

&lt;p&gt;And a spec is a md (markdown) file within your projects.&lt;/p&gt;

&lt;p&gt;As we are building with AI agents either via Cursor, VScode or Antigravity, we can see md files or specs (software term for md files) are fast becoming AI infrastructure. A communication layer. &lt;/p&gt;

&lt;p&gt;I have used specs mainly for,&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Developing spec for a new feature or a bug, generally a new development artifact and discuss the specs with the technical teams. AI agents are good at exploring the features in technical depth, costs, security aspects etc. that can be in one document or more. If there are changes, we can ask the AI agents to change them.&lt;/li&gt;
&lt;li&gt;If we need an analysis from a codebase that we need like a compliance analysis on a certain part. Spec that is filtered for the understanding of the target audience or a tool. I have built cost simulation tools based on the codebase, where I built yaml based infrastructure specs that fed into simulation tool. Beauty of these solutions are, the target audience doesn’t need access to whole codebase.   
I think spec driven engineering is enabled only by AI agentic era. It was there before but it was time consuming and not scalable.
 In essence,&lt;/li&gt;
&lt;li&gt;Specs give AI agents the context they need to build correctly.&lt;/li&gt;
&lt;li&gt;They also give teams clarity into why and how something was implemented.&lt;/li&gt;
&lt;li&gt;Specs are filtered to provide as inputs to other tools or analysis&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;But AI agentic development is really fast. As with all fast things, we could see two problems were emerging:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Discussions across teams became long and fragmented. Compliance needs those specs. Design needs those specs. Risk Modeling needs those specs.&lt;/li&gt;
&lt;li&gt;Specs were duplicated, scattered, and hard to reuse across projects. &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I built mdspec to remove that friction. I made it open source to make sure anyone can bend it any way they see fit for their own use cases.&lt;/p&gt;

&lt;p&gt;mdspec is a specification management platform designed for fast phased AI-driven development. It helps you:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Create structured, reusable specs&lt;/li&gt;
&lt;li&gt;Link specs across features and projects&lt;/li&gt;
&lt;li&gt;Maintain clarity as development speed increases&lt;/li&gt;
&lt;li&gt;Give AI agents reliable, durable context&lt;/li&gt;
&lt;li&gt;When specs become first-class citizens, teams move faster, without losing alignment.&lt;/li&gt;
&lt;li&gt;Go cross team securely.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>agents</category>
      <category>ai</category>
      <category>documentation</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
