Why was Spec Kit removed, and is it still recommended for spec-driven cloud agent workflows?

[jcooklin]

Hi! I noticed that PR #9224 appears to remove references/support for Spec Kit, and I wanted to ask for clarification on the intended direction.

Could you share the rationale for removing Spec Kit from this project? In particular, I’m trying to understand whether this was removed because:

• Spec Kit is no longer recommended for this workflow,
• the integration was not ready / not intended to be maintained here,
• there is a different preferred approach for spec-driven development with gh-aw,
• or the removal was unrelated to the broader recommendation around Spec Kit.

My use case is a spec-driven design/development workflow where the initial interaction may happen from a laptop, but the actual agent execution is intended to run in cloud agents on self-hosted runners.

For that kind of workflow, is GitHub Spec Kit still a recommended approach, or is there another recommended path for defining specs and running agentic workflows with gh-aw / GitHub-hosted or self-hosted runner infrastructure?

Any guidance on the intended architecture or roadmap would be appreciated. Thanks!

[pelikhan]

Agentic Workflows is a generic tool to create human agent processes. It can automate / enrich parts of most spec driven development systems.

Speckit was an experiment but we are not really using this project. This question is more for the Speckit project.

[pelikhan]

So the recommendation is to take your favorite desktop spec driven development and automate parts of it. So if you are a Speckit user, you could use AW to automate parts of it. And also this applies to many other SDD "kits".