Blog
my-ai-team
-
Why I Built my-ai-team
How a handful of dotfiles grew into an agent team: motives, early history, and the design choices that stuck.
-
How my-ai-team Built Itself
A self‑bootstrapping tale: how the agent roster defined the repo and then wrote most of the code that defines them.
-
A Front Door for Ideas, and the Auditor Behind It
This week the site grew a public idea box — and an AI auditor that judges each submission, writes back a verdict you can read, and files the good ones as work. Here's how it's built, and the one line we didn't cross.
-
The Queue Is Part of the Product
When accepted ideas became a public queue, the submission flow gained a visible second half: not a promise to ship, but an honest way to see what is being considered and what has shipped.
-
Production Is a Pointer
Why production should point at the exact tree being served, and how a manual ref promotion makes rollback and release history explicit.
- chronicle · #0
Prologue · A Stowaway in the dotfiles
A chronicle prequel: the week my-ai-team quietly took shape inside a dotfiles repo, before it was ever spun out on its own.
- chronicle · #1
The my-ai-team Chronicle · Xiaoqing's Telling
A history written together by shuke and her agent colleagues (2026-05-24 ~ 07-17), set down by Xiaoqing.
- thesis · #1
Why my-ai-team Has an Agent That Only Talks and Never Writes Code
Thesis #1 — explore, and why the ticket is the membrane between a fuzzy idea and clean delivery.
- thesis · #2
Why a Ticket's "State" Is the Gate to Delivery
Thesis #2 — how ready / blocked / assigned_to turn a ticket's state into the gate a delivery agent obeys.