GitHub - grothkopp/agentic-team-manifesto: Manifesto for Agentic Teams - better ways of building software by combining human judgment with AI agents · GitHub
/" data-turbo-transient="true" />
Skip to content
Search or jump to...
Search code, repositories, users, issues, pull requests...
-->
Search
Clear
Search syntax tips
Provide feedback
--><br>We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Cancel
Submit feedback
Saved searches
Use saved searches to filter your results more quickly
-->
Name
Query
To see all available qualifiers, see our documentation.
Cancel
Create saved search
Sign in
/;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up
Appearance settings
Resetting focus
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
grothkopp
agentic-team-manifesto
Public
Notifications<br>You must be signed in to change notification settings
Fork
Star
main
BranchesTags
Go to file
CodeOpen more actions menu
Folders and files<br>NameNameLast commit message<br>Last commit date<br>Latest commit
History<br>5 Commits<br>5 Commits
CNAME
CNAME
README.md
README.md
index.html
index.html
View all files
Repository files navigation
Manifesto for Agentic Teams
We are discovering better ways of building software by combining human judgment with AI agents. Through this work we have come to value:
Outcomes over output
More code is not more value. We measure what ships to users, not what ships to the merge queue.
Context over tooling
The best AI tools fail without accessible knowledge. We invest in making our organization's context machine-readable.
Orchestration over execution
Our job is to direct, review, and decide. We delegate production to agents and focus human energy where judgment matters.
Continuous flow over fixed ceremonies
We ship when ready, not when the sprint ends. We plan around review capacity, not production capacity.
Fluid boundaries over team silos
We design for collaboration across team lines: shared context, open channels, people and agents move to where the work is.
That is, while there is value in the items on the right, we value the items on the left more.
Principles
Our highest priority is to deliver value to users. Agents that produce output nobody uses are waste, not progress.
AI is an amplifier, not a miracle. It accelerates what's already there. If the foundation is weak, AI makes it worse faster. We invest in the foundation first.
We treat Context Debt like Technical Debt. Undocumented decisions, tribal knowledge, and stale documentation are liabilities. We pay them down systematically because our agents depend on it.
We measure outcomes, not velocity. Features shipped, problems solved, users served. Not PRs merged, lines generated, or story points completed.
The bottleneck has shifted. Code is cheap, judgment is scarce. We organize our team around review, verification, and decision-making, not around production.
Every agent has an identity, an owner, and a decision log. We don't deploy autonomous systems without accountability. We encode governance into pipelines and guardrails so compliance happens at deployment speed, not committee speed.
We delegate deliberately. The team has shared criteria for what gets delegated to agents, what stays human, and what's a collaboration. This is a team discipline, not an individual preference.
We recognize and reduce AI Waste. Overproduction, review bottlenecks, governance theater, context loss, over-prompting, wrong granularity, unused output, and manual work that should be automated. We audit regularly and fix relentlessly.
Small batches, continuous deployment, automated quality gates. Agent output follows the same engineering standards as human code. No exceptions, no shortcuts.
We build shared knowledge, not individual expertise. Prompt patterns, agent configurations, and delegation criteria belong to the team. When someone leaves, the knowledge stays.
We talk openly about how AI changes roles and identities. Senior engineers design systems instead of writing code. Juniors learn by reviewing agent output and understanding why. We create new narratives, not new anxieties.
We plan in short cycles with honest assessments, measurable goals, and named owners. Review, learn, adjust, repeat. Long-term roadmaps are speculation. Disciplined execution in tight loops is where value lives.
Most waste hides at team boundaries: handoffs, waiting, and context that doesn't travel. We treat cross-team friction like any other bottleneck: we measure it, own it, and reduce it.
Fluid boundaries don't mean no ownership. Every piece of work has a named owner. Owners pull in whoever they need, across teams and roles, and stay accountable for the outcome.
We...