Original Summary

I got tired of the same loop: ask the agent for something real, it goes quiet, hands back a finished thing, and now the work is mine. Did it understand what I meant? What did it actually change? Is something wrong in a way I'll only notice next week? So I built a small workflow layer called kaizen. It puts two checkpoints in that gap: Before anything is built, you see a plan and say yes or no. It states what it thinks the deliverable is, what "done" means, and what "wrong" would look like, so you correct a reading instead of filling in a form. After, a second agent that never saw the first one's reasoning reviews the work and lists what it found, numbered and severity-tagged. You pick what gets fixed. Some things that turned out to matter: - It's not only for code. The same five stages run for an email, a runbook, a research memo, a chapter. The planner works out what kind of work it is from the request; you're never asked to categorise. - All state is plain files in a .kaizen/ folder, so a run can be resumed later, by another session, or by a different tool. Claude Code, Codex, and Antigravity all follow the same spec. - There's a board. TUI in the terminal, or kaizen web for a mouse-first version in the browser (loopback only). Ideas on the left, runs under the stage they're actually in, redraws as agents write to disk. You can start a run from an idea with one click. - Zero dependencies. Bun is the only prerequisite. Install is one line: curl -fsSL https://bun.sh/install | bash && ~/.bun/bin/bunx kaizen-agent Then /kaizen <what you want done> in any project. Repo: https://github.com/hfadhlullah/kaizen npm: https://www.npmjs.com/package/kaizen-agent Happy to answer questions or hear where it gets in the way.   submitted by   /u/Odd-Afternoon-8043 [link]   [comments]

  • 情报分类：工作与职业机会
  • 分类依据：内容涉及招聘、求职或职业发展
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/15 10:24:12