llms.txt
# YAGNI
> Managed Agentic Software Teams. YAGNI sets up and runs Teams of named AI Agents for engineering orgs, inside the customer's own GitHub and tracker: Bailey proposes the next piece of work, Reeve critiques the plan, Wright builds to a draft pull request, Proctor reviews it, Fletcher tests it in a sandboxed browser (beta), and Harper reports what shipped. The customer's engineers approve every plan and merge every pull request. Engagements are scoped on a 30-minute call with the founder and quoted as a flat monthly fee; there is no published price.
YAGNI ("You Ain't Gonna Need It") is a managed service, not a tool to configure. YAGNI sets up the Teams to mirror the customer's engineering teams (a Team is never one repository), connects them to the customer's GitHub and Jira or Linear, writes the Playbook (business rules and guardrails in plain words) with the customer, and runs the Teams week to week: tuning what each Agent takes on, reading the runs, and fixing what goes wrong. The customer's engineers spend their time where judgment matters: approving the plan and merging the pull request.
Two promises hold on every Team. **Your pace, your priorities:** daily pull requests or a weekly batch, features one sprint and an upgrade the next; the customer re-aims a Team whenever priorities move. **Nothing to manage:** YAGNI sets up the Teams, tunes them, and fixes what goes wrong; the customer gets pull requests and a Monday report. Every change passes through the customer: every plan is approved by a person on the customer's team and every pull request is merged by one; an Agent can propose, build, review, and test, but it cannot merge, deploy, or do anything irreversible on its own, and Pause stops every Agent on a Team at once. YAGNI works in the customer's GitHub (through a GitHub App the customer installs) and the customer's tracker; it never hosts the customer's code and never migrates the backlog, so everything it ships is already in the customer's repositories.
The loop for one ticket: Bailey proposes it from the tracker with evidence; a person accepts it; Wright drafts a plan, Reeve critiques it, and a person approves it; Wright builds it in a cloud sandbox to a draft pull request; Proctor reviews it through its checks (deep review, business fit, database, security, tests) and Wright answers the findings; Fletcher walks a test plan in a browser and attaches the video; a person merges; Harper reports what shipped, with the receipts attached. The work a Team takes on includes tickets from the tracker, the pull request review queue, and migrations or other work the team does not have hands for.
## Pages
- [Managed Agentic Software Teams](https://yagni.app/): The offer: the six Agents and the loop, who does what, the two promises, and how engagements work.
- [Book 30 minutes](https://yagni.app/book): The one door. Thirty minutes with the founder to scope the first Team and get a flat monthly quote.
- [Security](https://yagni.app/security): Workspace-scoped data access, encrypted connector credentials, sanitized action auditing, US-hosted inference under zero data retention, isolated sandboxes, SOC 2 Type II in progress, DPA and BAA available, and the trust portal.
- [About](https://yagni.app/about): The company and the founder.
- [Blog](https://yagni.app/blog): Notes from the founder on agentic software teams, AI code review, and managing coding agents.
## The Agents
- Bailey (Product Manager): reads the backlog attached to the Team and proposes the next item with evidence. Never ships; a proposal always waits for a person.
- Reeve (Staff Engineer): critiques the plan before a line is written, against the rules in the Playbook. Never authors the plan and never blocks it.
- Wright (Builder): takes an approved plan to a draft pull request in a cloud sandbox and answers review rounds. Never merges.
- Proctor (Reviewer): reads every pull request through its checks and posts one review. Never merges; an approving review marks the pull request ready for a person to merge.
- Fletcher (QA, beta): boots the app in a sandbox, writes a test plan from the change, walks it in a browser, and attaches video and screenshots. Never changes application code.
- Harper (Chronicler): posts what shipped, what is in flight, and what needs a person to Slack, on the schedule the customer sets, with the receipts attached. Reports only.
## Integrations
YAGNI works in the tools the customer already uses and does not replace them: GitHub (App installation), Jira, Linear, Slack, Confluence, Notion, and Google Workspace, plus MCP servers and databases for in-house tools.
## Resources
- [Privacy policy](https://yagni.app/privacy)
- [Terms of service](https://yagni.app/terms)
## Optional
- [llms-full.txt](https://yagni.app/llms-full.txt): Extended canonical description with the Agents, the loop, who does what, the promises, how engagements work, and security.
