<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tinkerbee blog</title>
    <link>https://tinkerbee.io/blog</link>
    <atom:link href="https://tinkerbee.io/blog/rss.xml" rel="self" type="application/rss+xml" />
    <description>Notes from the Skcript R&amp;E team on Specs, coding agents and how we build Tinkerbee.</description>
    <language>en</language>
    <item>
      <title>Specs with no gaps: why we built Tinkerbee</title>
      <link>https://tinkerbee.io/blog/specs-with-no-gaps</link>
      <guid>https://tinkerbee.io/blog/specs-with-no-gaps</guid>
      <pubDate>Fri, 20 Nov 2026 09:00:00 GMT</pubDate>
      <description>Coding agents fill every gap in a Spec with a guess. Tinkerbee grills the Spec against your code until no gap is left, then hands your agent the answers.</description>
    </item>
    <item>
      <title>How Tinkerbee turns a Spec into tickets your agent can read</title>
      <link>https://tinkerbee.io/blog/spec-to-tickets-over-mcp</link>
      <guid>https://tinkerbee.io/blog/spec-to-tickets-over-mcp</guid>
      <pubDate>Fri, 20 Nov 2026 09:00:00 GMT</pubDate>
      <description>A Ready Spec becomes thin tickets in blocked-by order. A read-only MCP server lets Claude Code, Cursor and Codex pull each ticket with its Spec, Decisions, Glossary and ADRs.</description>
    </item>
    <item>
      <title>Built in a day by a swarm of agents: what worked and what broke</title>
      <link>https://tinkerbee.io/blog/built-in-a-day-by-a-swarm-of-agents</link>
      <guid>https://tinkerbee.io/blog/built-in-a-day-by-a-swarm-of-agents</guid>
      <pubDate>Fri, 20 Nov 2026 09:00:00 GMT</pubDate>
      <description>We built the first Tinkerbee from 21 tickets with one coding agent per ticket, in parallel. Here is the setup that kept them out of each other's way, and the four things that broke.</description>
    </item>
  </channel>
</rss>
