Your whole software factory fits in one file.
t25.yaml says who runs each role, how far a task can go and where it stops. It lives in your repository, next to the code.
fig. 1: excerpts from the T25 repository’s t25.yaml, read when this page is built
A preference list per role: the first available CLI takes over. If it is missing, the next one steps in.
routing: analyst: [codex, pi]Business interview, before the task exists. triage: [codex, pi]Type, risk and scope of the task. planner: [codex, pi]Spec and plan. research: [codex, pi]Repository context. dev-frontend: [codex, pi]Implementation in the task worktree. dev-backend: [codex, pi]Implementation in the task worktree. qa-frontend: [codex, pi]Browser, tests and verdict. qa-backend: [codex, pi]Tests and verdict. reviewer: [codex, pi]Reads the diff. security: [codex, pi]Secrets, dependencies and risks. docs: [codex, pi]Documentation. release: [codex, pi]Prepares the pull request.Where T25 stops, by risk level. With sandbox: docker, implementation and QA run in a container.
risk: low: { approval: none, sandbox: docker }Automatic PR, no merge. medium: { approval: plan, sandbox: docker }You approve the plan. high: { approval: plan_and_pr, sandbox: docker }You approve the plan and the PR. critical: { approval: human_required, sandbox: docker }Never automates deployment.The brake on an agent that will not stop.
limits: max_same_error_retries: 2Same error twice? It comes back to you. max_files_changed: 40Limit on files changed per task. max_diff_lines: 2000Limit on lines changed per task.Budget per task and per day.
cost: defaultBudgetUsd: 5Limit for each task, in dollars. periodBudgetUsd: 0Daily limit (UTC). Zero turns it off. warnRatio: 0.8Warns at 80% of the limit. stop: pauseAt the limit, the task pauses and keeps its work.General behaviour of T25.
t25: worktrees_dir: .t25/worktreesEach task in its own worktree. max_task_minutes: 60Maximum time for a stage, unless a role overrides it. require_plan_approval: trueHuman gate before the build starts.Twelve roles, each with its own agent.
Each role has its own fallback list, model and effort. QA can run on a different agent from the one that wrote the code.
analyst, triage- Understand the request and set type, risk and scope.
planner, research- Write the spec and plan from the repository context.
dev-frontend, dev-backend- Implement in the task’s isolated worktree.
qa-frontend, qa-backend- Exercise the delivery and give the verdict.
reviewer, security- Read the diff for defects and risk.
docs, release- Update the docs and prepare the pull request.