Workflow control for AI coding agents
$git clone https://github.com/nrslib/taktInstalls into the current project.
Install takt by running `git clone https://github.com/nrslib/takt`, then use it for the current task and follow its documentation at https://github.com/nrslib/takt.
| 1 | # TAKT |
| 2 | |
| 3 | <p align="center"> |
| 4 | <a href="https://www.npmjs.com/package/takt"><img src="https://img.shields.io/npm/v/takt?label=npm" alt="npm version"></a> |
| 5 | <a href="https://github.com/nrslib/takt/stargazers"><img src="https://img.shields.io/github/stars/nrslib/takt?logo=github&label=stars" alt="GitHub stars"></a> |
| 6 | <a href="https://github.com/nrslib/takt/actions/workflows/ci.yml"><img src="https://github.com/nrslib/takt/actions/workflows/ci.yml/badge.svg?branch=main" alt="CI"></a> |
| 7 | <a href="./LICENSE"><img src="https://img.shields.io/github/license/nrslib/takt" alt="license"></a> |
| 8 | <a href="https://discord.gg/R2Xz3uYWxD"><img src="https://img.shields.io/badge/dynamic/json?label=discord&query=approximate_member_count&url=https%3A%2F%2Fdiscord.com%2Fapi%2Fv10%2Finvites%2FR2Xz3uYWxD%3Fwith_counts%3Dtrue&suffix=%20members&logo=discord&logoColor=white&color=5865F2" alt="Discord members"></a> |
| 9 | </p> |
| 10 | |
| 11 | <p align="center"> |
| 12 | <a href="./README.md">English</a> | |
| 13 | <a href="./docs/README.ja.md">日本語</a> |
| 14 | </p> |
| 15 | |
| 16 | **Stop babysitting AI coding agents.** |
| 17 | |
| 18 | TAKT is an open-source CLI that turns AI coding agents into repeatable development workflows. Define planning, implementation, review, fix loops, human checkpoints, permissions, and output contracts in YAML, then run tasks with isolated worktrees and traceable logs. |
| 19 | |
| 20 | Instead of asking one agent to remember the whole process, TAKT gives each step its own role, context, and transition rules. Agents can code, but the workflow decides what happens next. |
| 21 | |
| 22 | - Run plan → implement → review → fix loops as explicit workflow steps |
| 23 | - Keep context focused with step-specific personas, policies, knowledge, instructions, and output contracts |
| 24 | - Execute queued tasks in isolated worktrees and inspect logs and reports afterward |
| 25 | - Use Claude Code, Claude SDK, Codex SDK, OpenCode SDK, Cursor, GitHub Copilot CLI, or Kiro as providers |
| 26 | |
| 27 | **T**AKT **A**gent **K**oordination **T**opology orchestrates multiple AI agents with structured review loops, managed prompts, and guardrails. |
| 28 | |
| 29 | Talk to AI to define what you want, queue it as a task, and run it with `takt run`. Planning, implementation, review, and fix loops are defined in YAML workflow files, so the process is not left to the agent's discretion. TAKT coordinates Claude Code, Codex, OpenCode, Cursor, GitHub Copilot CLI, and Kiro CLI as agents with different roles, permissions, and context. |
| 30 | |
| 31 | TAKT is built primarily for AI coding workflows, but the same model applies beyond coding: any task where multiple AI agents need to coordinate, or where review, judgment, and feedback loops can improve task quality. |
| 32 | |
| 33 | TAKT is built with TAKT itself (dogfooding). |
| 34 | |
| 35 | ## Why TAKT |
| 36 | |
| 37 | AI coding agents are powerful, but they do not automatically create a stable development process. In long-running work, they forget instructions, accumulate polluted context, blur implementation and review responsibilities, and often force humans to repeat the same feedback again and again. That wears people down. |
| 38 | |
| 39 | Adding more rules to prompts, `CLAUDE.md`, or skills can help, but it cannot enforce the process. Whether the rules are followed is still left to the agent's behavior. |
| 40 | |
| 41 | TAKT treats AI agents as something to be controlled from the outside, not simply trusted. |
| 42 | |
| 43 | Workflows define the phases, and each step receives its own persona, policy, knowledge, instruction, and output contract. TAKT manages implementation, review, fix, and re-review flows declaratively. By separating responsibilities, knowledge, and constraints, then giving each agent only what it needs for the current step, TAKT improves task quality without bloating context. |
| 44 | |
| 45 | Reviews cannot be silently skipped. Findings route work back to fix steps, and human judgment can be requested when needed. Tasks run in isolated worktrees, and each step leaves logs and reports so the path from task to PR remains traceable. |
| 46 | |
| 47 | At its core, TAKT runs reusable agent processes built from roles, phases, judgments, and feedback loops. |
| 48 | |
| 49 | The goal is simple: make developme |