<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blog Posts — tk3.biz</title>
    <link>https://tk3.biz/en/blog/</link>
    <atom:link href="https://tk3.biz/en/rss.xml" rel="self" type="application/rss+xml"/>
    <description>The blog of istb16, a software engineer: what I try out in development and check against public data, plus the apps I build on my own.</description>
    <language>en-us</language>
    <lastBuildDate>Thu, 19 Nov 2026 04:05:00 GMT</lastBuildDate>
    <item>
      <title>[Released] dev-orchestra: A Pre-Design Interview, and Less Work in Reviews v1.4.0</title>
      <link>https://tk3.biz/en/blog/2026-11-19-dev-orchestra-v1-4-0/</link>
      <guid isPermaLink="true">https://tk3.biz/en/blog/2026-11-19-dev-orchestra-v1-4-0/</guid>
      <description>A roundup of dev-orchestra v1.4.0. It adds an interview that asks one question at a time before the design (design.ask_questions: grill). In reviews, reviewers are told what was already decided, minor pre-existing problems stay out of triage, and re-review rounds run fewer reviewers. The CLI also picks the light tier itself, and a workflow can continue in a new session.</description>
      <pubDate>Thu, 19 Nov 2026 04:05:00 GMT</pubDate>
    </item>
    <item>
      <title>I Had dev-orchestra Interview Me Before the Design</title>
      <link>https://tk3.biz/en/blog/2026-11-19-dev-orchestra-grill/</link>
      <guid isPermaLink="true">https://tk3.biz/en/blog/2026-11-19-dev-orchestra-grill/</guid>
      <description>I tried design.ask_questions: grill, new in dev-orchestra 1.4.0, with the same request as part 16: &quot;let tasks have due dates.&quot; It asked one question at a time, eight in all. An answer that added a condition got a follow-up, but a vague answer was interpreted rather than probed, and the intent and success criteria the docs list were never asked.</description>
      <pubDate>Thu, 19 Nov 2026 04:05:00 GMT</pubDate>
    </item>
    <item>
      <title>I Had dev-orchestra Ask Me Questions Before the Design</title>
      <link>https://tk3.biz/en/blog/2026-11-18-dev-orchestra-design-questions/</link>
      <guid isPermaLink="true">https://tk3.biz/en/blog/2026-11-18-dev-orchestra-design-questions/</guid>
      <description>I tried dev-orchestra 1.3.0&apos;s questions before the design (design.ask_questions) with a vague request and a clear one. Under auto, only the vague request got questions; under true, the architect asked four even about the request I thought was clear. When someone is watching, no plan is written until every question is answered.</description>
      <pubDate>Wed, 18 Nov 2026 04:05:00 GMT</pubDate>
    </item>
    <item>
      <title>I Triaged Findings from Several AIs with dev-orchestra and Had Them Fixed</title>
      <link>https://tk3.biz/en/blog/2026-11-13-dev-orchestra-triage/</link>
      <guid isPermaLink="true">https://tk3.biz/en/blog/2026-11-13-dev-orchestra-triage/</guid>
      <description>I sorted 14 findings from four reviewers with dev-orchestra&apos;s review triage into 3 accepted, 9 duplicates and 2 rejected, had the fixer work from fix-brief, and took it through re-testing and re-review. I also checked how duplicates are grouped, where triage notes end up, and the closing whole-change round in 1.3.0.</description>
      <pubDate>Fri, 13 Nov 2026 04:05:00 GMT</pubDate>
    </item>
    <item>
      <title>[Released] dev-orchestra: A Resumed Design Run Now Records Only Its Own Cost v1.3.2</title>
      <link>https://tk3.biz/en/blog/2026-11-12-dev-orchestra-v1-3-2/</link>
      <guid isPermaLink="true">https://tk3.biz/en/blog/2026-11-12-dev-orchestra-v1-3-2/</guid>
      <description>A roundup of dev-orchestra v1.3.2. When a design was resumed and revised, that run&apos;s cost was recorded with the earlier session&apos;s cost added in. This is now fixed; tokens show and similar reports could show the architect costing more than it did.</description>
      <pubDate>Thu, 12 Nov 2026 04:05:00 GMT</pubDate>
    </item>
    <item>
      <title>I Used Only dev-orchestra&apos;s Review to Show My Local Changes to Several AIs</title>
      <link>https://tk3.biz/en/blog/2026-11-09-dev-orchestra-review-only/</link>
      <guid isPermaLink="true">https://tk3.biz/en/blog/2026-11-09-dev-orchestra-review-only/</guid>
      <description>How to use only dev-orchestra&apos;s review, without its design and implementation stages. With three commands, review snapshot, review run and review show, I had Claude and Codex review a local branch. I also cover how to choose --base, the options I use most, and using it to review blog posts.</description>
      <pubDate>Mon, 09 Nov 2026 04:05:00 GMT</pubDate>
    </item>
    <item>
      <title>I Had dev-orchestra Review the Whole Change Once More at the End</title>
      <link>https://tk3.biz/en/blog/2026-11-07-dev-orchestra-whole-change-review/</link>
      <guid isPermaLink="true">https://tk3.biz/en/blog/2026-11-07-dev-orchestra-whole-change-review/</guid>
      <description>I tried the closing review of the whole change (review.whole_change_recheck) added in dev-orchestra 1.3.0 on a small Python package. After a fix-only round came back with nothing, the whole-change round found one clash between the fix and the earlier change. With a fix that clashed on purpose, the fix-only round caught it first.</description>
      <pubDate>Sat, 07 Nov 2026 04:05:00 GMT</pubDate>
    </item>
    <item>
      <title>[Released] dev-orchestra: Start the Review While the Tests Run v1.3.1</title>
      <link>https://tk3.biz/en/blog/2026-10-31-dev-orchestra-v1-3-1/</link>
      <guid isPermaLink="true">https://tk3.biz/en/blog/2026-10-31-dev-orchestra-v1-3-1/</guid>
      <description>A roundup of dev-orchestra v1.3.1. The code review can now start without waiting for the tests to finish (off by default). Plan approval now defaults to auto, which skips the approval when nobody is watching, such as in CI, and the conditions are met. Claude write runs now start with only the tools they use and no MCP servers.</description>
      <pubDate>Sat, 31 Oct 2026 04:05:00 GMT</pubDate>
    </item>
    <item>
      <title>[Released] dev-orchestra: A Closing Review of the Whole Change v1.3.0</title>
      <link>https://tk3.biz/en/blog/2026-10-30-dev-orchestra-v1-3-0/</link>
      <guid isPermaLink="true">https://tk3.biz/en/blog/2026-10-30-dev-orchestra-v1-3-0/</guid>
      <description>A roundup of dev-orchestra v1.3.0. When a review round that looked only at the fix finds nothing above Low, the review now ends with one more round over the whole change. It is on by default, and a Medium finding now calls for another round, so a review can take more rounds than before.</description>
      <pubDate>Fri, 30 Oct 2026 04:05:00 GMT</pubDate>
    </item>
    <item>
      <title>I Measured dev-orchestra: Time per Request, and Findings by Number of Reviewers</title>
      <link>https://tk3.biz/en/blog/2026-10-27-dev-orchestra-measurement/</link>
      <guid isPermaLink="true">https://tk3.biz/en/blog/2026-10-27-dev-orchestra-measurement/</guid>
      <description>With dev-orchestra 1.2.1, I made one small feature request and measured how long it took (about 6 minutes, not counting my approval) and how many findings were reported and accepted with 1, 2, and 4 reviewers. More reviewers meant more accepted findings, but the extra ones were about tests.</description>
      <pubDate>Tue, 27 Oct 2026 04:05:00 GMT</pubDate>
    </item>
    <item>
      <title>Splitting a Plan into dev-orchestra Work Units and Implementing Them Side by Side</title>
      <link>https://tk3.biz/en/blog/2026-10-26-dev-orchestra-work-units/</link>
      <guid isPermaLink="true">https://tk3.biz/en/blog/2026-10-26-dev-orchestra-work-units/</guid>
      <description>I tried the work units added in dev-orchestra 1.2.0. I wrote a ## Units section in a plan, had Claude implement two units side by side in separate git worktrees, merged them into the working tree, and ran the final integration unit in place, with the actual commands and output.</description>
      <pubDate>Mon, 26 Oct 2026 04:05:00 GMT</pubDate>
    </item>
    <item>
      <title>[Released] dev-orchestra: Parallel Work Units and Per-Role Instructions v1.1.0 - v1.2.1</title>
      <link>https://tk3.biz/en/blog/2026-10-26-dev-orchestra-v1-2-1/</link>
      <guid isPermaLink="true">https://tk3.biz/en/blog/2026-10-26-dev-orchestra-v1-2-1/</guid>
      <description>A roundup of dev-orchestra&apos;s changes from v1.1.0 to v1.2.1: running a plan as work units side by side, standing instructions per role, questions before the design, and settings for progress reports. If you capture its output on Windows, note the encoding change.</description>
      <pubDate>Mon, 26 Oct 2026 04:05:00 GMT</pubDate>
    </item>
    <item>
      <title>Giving dev-orchestra Standing Instructions per Role</title>
      <link>https://tk3.biz/en/blog/2026-10-26-dev-orchestra-instructions/</link>
      <guid isPermaLink="true">https://tk3.biz/en/blog/2026-10-26-dev-orchestra-instructions/</guid>
      <description>I tried instructions, added in dev-orchestra 1.2.1. Standing instructions for the implementer or reviewers written in the repository go into every prompt. I check, with real output, how they are shown, where they go, and how a change to the instructions is treated.</description>
      <pubDate>Mon, 26 Oct 2026 04:05:00 GMT</pubDate>
    </item>
    <item>
      <title>Updating dev-orchestra (Claude Code / Codex / Antigravity)</title>
      <link>https://tk3.biz/en/blog/2026-10-25-dev-orchestra-update/</link>
      <guid isPermaLink="true">https://tk3.biz/en/blog/2026-10-25-dev-orchestra-update/</guid>
      <description>I actually updated dev-orchestra from 1.0.0 to 1.1.1 in each of Claude Code, Codex, and Antigravity. In Claude Code, claude plugin update alone did nothing; the marketplace had to be refreshed first. I cover how to check your version, the steps for each CLI, and what to check after updating, plus how to uninstall it.</description>
      <pubDate>Sun, 25 Oct 2026 04:05:00 GMT</pubDate>
    </item>
    <item>
      <title>Connecting My Own Agent to dev-orchestra (Local LLM Edition)</title>
      <link>https://tk3.biz/en/blog/2026-10-23-dev-orchestra-custom-agent/</link>
      <guid isPermaLink="true">https://tk3.biz/en/blog/2026-10-23-dev-orchestra-custom-agent/</guid>
      <description>With dev-orchestra 1.0.0, I wrote my own adapter from scratch and added a local LLM as a reviewer. All it takes is a small CLI that takes a prompt and returns an answer, plus an adapter of about 50 lines. I cover where to put it, checking it with doctor, which roles it can and can&apos;t take, and the cautions.</description>
      <pubDate>Fri, 23 Oct 2026 04:05:00 GMT</pubDate>
    </item>
    <item>
      <title>Rearranging dev-orchestra&apos;s Reviewers and Roles</title>
      <link>https://tk3.biz/en/blog/2026-10-21-dev-orchestra-reviewers-roles/</link>
      <guid isPermaLink="true">https://tk3.biz/en/blog/2026-10-21-dev-orchestra-reviewers-roles/</guid>
      <description>How to set the model for each role in dev-orchestra, how to choose reviewer focuses, and config suggest-roles, which proposes domain specialists. I also showed a change with deliberately planted bugs to 9 reviewers to see what changes as you add more of them.</description>
      <pubDate>Wed, 21 Oct 2026 04:05:00 GMT</pubDate>
    </item>
    <item>
      <title>Comparing dev-orchestra&apos;s quality / standard / fast presets</title>
      <link>https://tk3.biz/en/blog/2026-10-19-dev-orchestra-presets/</link>
      <guid isPermaLink="true">https://tk3.biz/en/blog/2026-10-19-dev-orchestra-presets/</guid>
      <description>I expanded dev-orchestra&apos;s setup presets quality / standard / fast in three environments (Claude Code only, Codex only, and both) and compared them. Here is how the per-role models, the number of reviewers, and how much cost is cut change, and which one to pick.</description>
      <pubDate>Mon, 19 Oct 2026 04:05:00 GMT</pubDate>
    </item>
    <item>
      <title>I tried dev-orchestra in Antigravity</title>
      <link>https://tk3.biz/en/blog/2026-10-17-dev-orchestra-antigravity/</link>
      <guid isPermaLink="true">https://tk3.biz/en/blog/2026-10-17-dev-orchestra-antigravity/</guid>
      <description>I installed dev-orchestra in Antigravity too. It works fine as the place you talk to, but handing design and review to the Antigravity CLI (agy) is limited. Here is what works, what doesn&apos;t, and how I recommend using it.</description>
      <pubDate>Sat, 17 Oct 2026 04:05:00 GMT</pubDate>
    </item>
    <item>
      <title>Using dev-orchestra with Codex</title>
      <link>https://tk3.biz/en/blog/2026-10-16-dev-orchestra-codex/</link>
      <guid isPermaLink="true">https://tk3.biz/en/blog/2026-10-16-dev-orchestra-codex/</guid>
      <description>I installed dev-orchestra in Codex too. It works with Codex alone, but with both Claude Code and Codex installed, it automatically switches to the recommended setup where AIs from different companies review your code. I also summarized the Codex-specific features and caveats at the end.</description>
      <pubDate>Fri, 16 Oct 2026 04:05:00 GMT</pubDate>
    </item>
    <item>
      <title>I installed dev-orchestra in Claude Code and ran development from a single sentence</title>
      <link>https://tk3.biz/en/blog/2026-10-15-dev-orchestra-claude-code/</link>
      <guid isPermaLink="true">https://tk3.biz/en/blog/2026-10-15-dev-orchestra-claude-code/</guid>
      <description>I installed dev-orchestra in a Claude Code-only environment and tried everything from the initial setup to a one-sentence request. Installation is two lines, and on first use you just pick a preset; the reviewers are made up of Claude alone. At the end, I also summarize the features and caveats specific to Claude Code.</description>
      <pubDate>Thu, 15 Oct 2026 04:05:00 GMT</pubDate>
    </item>
  </channel>
</rss>
