AutoGen vs GitHub Spec Kit — what it is, in its own words?

AutoGen: A framework for multi-agent AI applications. "AutoGen is a framework for creating multi-agent AI applications that can act autonomously or work alongside humans.". GitHub Spec Kit: An open source toolkit that gives AI coding agents structured processes, reusable templates, and documented outcomes. The README was rewritten after this row was read on 13 September 2026. It now opens "Spec Kit is an open source toolkit that gives AI coding agents structured processes, reusable templates, and documented outcomes." The repository heading reads "Spec Kit. Build with a spec, fix a bug, or assess an idea, with your coding agent." The earlier line "define what to build before building it" is gone from the page. Read from github.com and github.com on 2026-09-18.

AutoGen vs GitHub Spec Kit — what its readme says about its own maintenance?

AutoGen: Maintenance mode, with a named successor. "⚠️ Maintenance mode. AutoGen is now in maintenance mode. It will not receive new features or enhancements and is community managed going forward. New users should start with Microsoft Agent Framework. Existing users are encouraged to migrate using the AutoGen → Microsoft Agent Framework migration guide." The only one of the five that publishes its own status at all. GitHub Spec Kit does not state it on github.com. No maintenance statement, deprecation notice or successor. The README does carry an "Experimental goals" section describing what its authors are researching, which is a statement about direction rather than about whether the project is being maintained. Read on the repository's own front page on 14 August 2026. Read from github.com and github.com on 2026-09-18. What its README says about its own maintenance here means whether the project's front page tells a reader that it is still being developed, has stopped, or has a successor — as distinct from what its commit graph implies.

AutoGen vs GitHub Spec Kit — how you install it?

AutoGen: pip install autogen-agentchat. "AutoGen requires Python 3.10 or later." Installed as `autogen-agentchat` plus an extension package for the model client; `autogenstudio` is published separately as a no-code GUI. GitHub Spec Kit: uv tool install specify-cli. Installed from a pinned release tag — "Replace vX.Y.Z with the latest release tag from Releases — keep the leading v (for example, v0.12.11, not 0.12.11)" — or from PyPI. The only one of the five whose install instructions pin a version. Read from github.com and github.com on 2026-09-18.

When should I pick AutoGen, and when GitHub Spec Kit?

AutoGen — You already have AutoGen in production and you are deciding whether to move. Then read its own README first, because it answers the question for you: it is in maintenance mode, it "will not receive new features or enhancements", and Microsoft names the successor — "new users should start with Microsoft Agent Framework", with a published migration guide. A framework that tells you plainly it has stopped is more useful to a maintainer than one that has quietly stopped and says nothing, and that candour is a real reason to trust the code you already depend on while you migrate off it. GitHub Spec Kit — The thing going wrong is that the agent builds the wrong thing, not that it builds it badly — and you want a process rather than a runtime. Spec Kit is the only one of the five that is agent-agnostic by design, "an open source toolkit for building high-quality software with any AI coding agent", and the only one whose premise is inverting the artifact: "specifications become executable, directly generating working implementations rather than just guiding them". It also runs beside whatever framework you already have, because it produces specs rather than processes.

Board / 2 compared, every cell read off its own repository on September 18, 2026, rescored September 13, 2026

AutoGen vs GitHub Spec Kit

The same 6 criteria for both, with the page each figure came from and the day it was read.

The verdict

what to pick, and what the answer rests on

On what it is, in its own words, AutoGen is A framework for multi-agent AI applications and GitHub Spec Kit is An open source toolkit that gives AI coding agents structured processes, reusable templates, and documented outcomes. On what its readme says about its own maintenance, AutoGen is Maintenance mode, with a named successor and GitHub Spec Kit does not publish it. On how you install it, AutoGen is pip install autogen-agentchat and GitHub Spec Kit is uv tool install specify-cli. On licence, AutoGen is MIT, plus CC-BY-4.0 and GitHub Spec Kit is MIT. On who publishes it, AutoGen is microsoft and GitHub Spec Kit is github. On what it sells alongside, AutoGen does not publish it and GitHub Spec Kit does not publish it. StillShipping sells neither of these and takes no referral fee on either. It scores them. Every figure was read off the named company's own page on or since 2026-09-18; the URLs and the dates are at the foot of this page, and a job re-fetches each one on a schedule and fails when a figure is no longer on the page it came from.

Head to head

what each one publishes about itself, read off its own repository on September 18, 2026

AutoGen vs GitHub Spec Kit, on what each project publishes about itself
Axis	AutoGen	GitHub Spec Kit
What it is, in its own words	A framework for multi-agent AI applications"AutoGen is a framework for creating multi-agent AI applications that can act autonomously or work alongside humans."read September 18, 2026	An open source toolkit that gives AI coding agents structured processes, reusable templates, and documented outcomesThe README was rewritten after this row was read on 13 September 2026. It now opens "Spec Kit is an open source toolkit that gives AI coding agents structured processes, reusable templates, and documented outcomes." The repository heading reads "Spec Kit. Build with a spec, fix a bug, or assess an idea, with your coding agent." The earlier line "define what to build before building it" is gone from the page.read September 18, 2026
What its README says about its own maintenancewhether the project's front page tells a reader that it is still being developed, has stopped, or has a successor. As distinct from what its commit graph implies	Maintenance mode, with a named successor"⚠️ Maintenance mode. AutoGen is now in maintenance mode. It will not receive new features or enhancements and is community managed going forward. New users should start with Microsoft Agent Framework. Existing users are encouraged to migrate using the AutoGen → Microsoft Agent Framework migration guide." The only one of the five that publishes its own status at all.read September 18, 2026	Not publishedNo maintenance statement, deprecation notice or successor. The README does carry an "Experimental goals" section describing what its authors are researching, which is a statement about direction rather than about whether the project is being maintained. Read on the repository's own front page on 14 August 2026.read September 18, 2026
How you install it	pip install autogen-agentchat"AutoGen requires Python 3.10 or later." Installed as `autogen-agentchat` plus an extension package for the model client; `autogenstudio` is published separately as a no-code GUI.read September 18, 2026	uv tool install specify-cliInstalled from a pinned release tag. "Replace vX.Y.Z with the latest release tag from Releases. Keep the leading v (for example, v0.12.11, not 0.12.11)". Or from PyPI. The only one of the five whose install instructions pin a version.read September 18, 2026
Licence	MIT, plus CC-BY-4.0The repository's file navigation lists two: a CC-BY-4.0 licence and an MIT licence, with a separate LICENSE-CODE file. The only dual-licensed project of the five.read September 18, 2026	MITShown in the repository's own file navigation alongside its code of conduct, contributing guide and security policy.read September 18, 2026
Who publishes it	microsoftPublished from Microsoft's own organisation, which is also what makes its maintenance notice load-bearing: the successor it names is another Microsoft product.read September 18, 2026	githubPublished from GitHub's own organisation. Of the five this is the one whose survival depends least on a single company's product line and most on a platform team's continued interest.read September 18, 2026
What it sells alongside	Not publishedThe README publishes no paid tier, hosted plan or commercial suite for AutoGen itself. What it names instead is a successor framework rather than a product sold alongside this one. Read on the repository's own front page on 14 August 2026.read September 18, 2026	Not publishedNo paid tier, hosted plan or commercial suite is published on the README. Read on the repository's own front page on 14 August 2026.read September 18, 2026
Why you would pick itEach project’s own case, in its own words.	You already have AutoGen in production and you are deciding whether to move. Then read its own README first, because it answers the question for you: it is in maintenance mode, it "will not receive new features or enhancements", and Microsoft names the successor. "new users should start with Microsoft Agent Framework", with a published migration guide. A framework that tells you plainly it has stopped is more useful to a maintainer than one that has quietly stopped and says nothing, and that candour is a real reason to trust the code you already depend on while you migrate off it.	The thing going wrong is that the agent builds the wrong thing, not that it builds it badly. And you want a process rather than a runtime. Spec Kit is the only one of the five that is agent-agnostic by design, "an open source toolkit for building high-quality software with any AI coding agent", and the only one whose premise is inverting the artifact: "specifications become executable, directly generating working implementations rather than just guiding them". It also runs beside whatever framework you already have, because it produces specs rather than processes.

What the board says tonight

the axis the table above cannot carry, read from the GitHub API on the same nightly pass

The tools in this comparison, as this board scored them

AutoGenmicrosoft/autogen	SlowingOrchestrators	35/100	5mo agoApril 15, 2026	0	0	too few	61k
Spec Kitgithub/spec-kit	MaintainedSpec frameworks	100/100	1d agoSeptember 12, 2026	100+	27	too few	136k

Nothing on this row is quoted from anybody. It is the GitHub API, read last night, and it moves without this page being edited.

Questions

4 asked about this comparison

AutoGen vs GitHub Spec Kit. What it is, in its own words?: AutoGen: A framework for multi-agent AI applications. "AutoGen is a framework for creating multi-agent AI applications that can act autonomously or work alongside humans.". GitHub Spec Kit: An open source toolkit that gives AI coding agents structured processes, reusable templates, and documented outcomes. The README was rewritten after this row was read on 13 September 2026. It now opens "Spec Kit is an open source toolkit that gives AI coding agents structured processes, reusable templates, and documented outcomes." The repository heading reads "Spec Kit. Build with a spec, fix a bug, or assess an idea, with your coding agent." The earlier line "define what to build before building it" is gone from the page. Read from github.com and github.com on 2026-09-18.
AutoGen vs GitHub Spec Kit. What its readme says about its own maintenance?: AutoGen: Maintenance mode, with a named successor. "⚠️ Maintenance mode. AutoGen is now in maintenance mode. It will not receive new features or enhancements and is community managed going forward. New users should start with Microsoft Agent Framework. Existing users are encouraged to migrate using the AutoGen → Microsoft Agent Framework migration guide." The only one of the five that publishes its own status at all. GitHub Spec Kit does not state it on github.com. No maintenance statement, deprecation notice or successor. The README does carry an "Experimental goals" section describing what its authors are researching, which is a statement about direction rather than about whether the project is being maintained. Read on the repository's own front page on 14 August 2026. Read from github.com and github.com on 2026-09-18. What its README says about its own maintenance here means whether the project's front page tells a reader that it is still being developed, has stopped, or has a successor. As distinct from what its commit graph implies.
AutoGen vs GitHub Spec Kit. How you install it?: AutoGen: pip install autogen-agentchat. "AutoGen requires Python 3.10 or later." Installed as `autogen-agentchat` plus an extension package for the model client; `autogenstudio` is published separately as a no-code GUI. GitHub Spec Kit: uv tool install specify-cli. Installed from a pinned release tag. "Replace vX.Y.Z with the latest release tag from Releases. Keep the leading v (for example, v0.12.11, not 0.12.11)". Or from PyPI. The only one of the five whose install instructions pin a version. Read from github.com and github.com on 2026-09-18.
When should I pick AutoGen, and when GitHub Spec Kit?: AutoGen. You already have AutoGen in production and you are deciding whether to move. Then read its own README first, because it answers the question for you: it is in maintenance mode, it "will not receive new features or enhancements", and Microsoft names the successor. "new users should start with Microsoft Agent Framework", with a published migration guide. A framework that tells you plainly it has stopped is more useful to a maintainer than one that has quietly stopped and says nothing, and that candour is a real reason to trust the code you already depend on while you migrate off it. GitHub Spec Kit. The thing going wrong is that the agent builds the wrong thing, not that it builds it badly. And you want a process rather than a runtime. Spec Kit is the only one of the five that is agent-agnostic by design, "an open source toolkit for building high-quality software with any AI coding agent", and the only one whose premise is inverting the artifact: "specifications become executable, directly generating working implementations rather than just guiding them". It also runs beside whatever framework you already have, because it produces specs rather than processes.

Where every cell was read

derived from the cells themselves, never listed by hand

Source	Read	Why
AutoGen	September 18, 2026	What it is, in its own words, What its README says about its own maintenance, How you install it, Licence, Who publishes it, What it sells alongside. github.com/microsoft/autogen
GitHub Spec Kit	September 18, 2026	What it is, in its own words, What its README says about its own maintenance, How you install it, Licence, Who publishes it, What it sells alongside. github.com/github/spec-kit

A hand-listed source block drifts from the table the first time a cell’s URL changes, and then the page is citing a page it did not read.