Is spec-kit still relevant today for brownfield projects?

[lance2k]

I started the MVP with spec-kit but for new features I don't see myself using spec-kit. My current workflow is to use Plan Agent (copilot built-in agent) with GPT 5.4 then use Sonnet 4.6 to implement or use Agent with Opus 4.6. Using spec-kit takes more development time by creating and reviewing the generated specs etc.

What are your thoughts on this? Also if I'm not using spec-kit anymore, should I remove the mvp specs or just keep it updated? thanks

[mnriem]

You can most definitely use Spec Kit for brownfield projects as illustrated by the Community Walkthroughs listed on the main README. Also note that because we have opened up Spec Kit for extensions and presetes there are quite a few additional extensions available that can be used for various things beyond the core workflow (e.g reviews, other workflows, organization overrides, etceteras). Also as Spec Kit is agent agnostic you can pick whichever integration you desire

[lance2k]

I see, I might use spec-kit again when things are slowing down. It just that for new features I find that using /specify -> /plan -> /task -> /implement takes more time reviewing than the built in Plan -> Implement workflow.

[mnriem]

And when you say built-in you are referring to IDE / CLI you are using of course

[lance2k]

yes, github copilot now has a built-in Planning Agent

[mnriem]

Yes it does. Just wanted folks reading this see that you are using a specific capability in GitHub Copilot