Ways to make spec kit more "enterprise"

[senseicz]

I was wondering whether there are plans to make spec kit more oriented towards enterprise style of development. What I mean is that there are usually number of people involved in a project, spanning multiple roles from business analyst to software engineers. While these are comfortable using AI agents like Github Copilot or Cursor, people that should really write specifications and requirements usually use different set of tools.
Possibly if there is a way how to bridge the gap between Github and M365 Copilots and surface parts of spec kit in Teams or other tool that "enterprise team" use for communication might be interesting way forward. Clear instructions on how to version feature specs would also need to be established. I wonder if recently announced Github app for Teams can be a step in good direction.

[ChrisLeslie]

how about getting the specs from Azure devops via https://learn.microsoft.com/en-us/azure/devops/mcp-server/mcp-server-overview?view=azure-devops #

[senseicz]

Please correct me if I'm wrong but you'd still need VSCode or similar tool to utilize MCP server, which may be considered too much in some "enterprise" environments. I wonder if there is a way to use Azure Devops MCP server as Agent in M365 Copilot, that might be option...

[dragoshont]

@senseicz @ChrisLeslie , I think this is quite critical to have. Added my experience with this upgrade here: #1235
Let me know if that fits your case. I am evaluating if a PR could benefit more folks

[massimogentilini]

While generically speaking I agree with you that the usage of SpecKit in an enterprise environment requires some (or maybe a lot) of fine tuning (I'm starting and it's true) I do not agree on the approach that there should be a multitude of tools.

The point of contact are MD files that AI tools can use to create other MD files and the usage of a GIT repo to store them for their lineage. So the tools are MD+GIT and something that can use AI and templates to elaborate them. All the VSCode and tool integration is nice to have but it's an accessory to the process.

Using VSCode for editing MD files and learning how to use the VSCode IDE for storing them in a repo and run specify commands seems quite easy to me and everyone can learn. If there is a business case to create a specific tool to work on specs using speckit I'm quite sure there will be some startup that will create it.

If, on the other hand, you business is focused on doing things using Office it's because they value more appearance than substance, make them focus more on the "whats" and the "whys" and not in selecting the right color for the PowerPoint background and the Enterprise will be happier (I know it's difficult but AI requires this kind of changes in people mindset to be adopted successfully).