Integrating specs/ outputs into docs, workflow and prompts?*

[MrHinsh]

Do you continuously integrate outputs from specs/* back into your core documentation and architecture?

Context:

• I maintain a /docs folder covering architecture, CLI, TUI, orchestration, and module-level design
• I also have an .agent folder with guardrails and context definitions

Question:

• After implementation, do you systematically update docs to reflect what was actually built?
• If yes:
  • When does this happen, during the branch, post-merge, or as a separate activity?
  • Is this driven by a dedicated prompt or workflow?
  • Do you treat documentation updates as part of the Definition of Done, or as a follow-on process?

I am specifically trying to understand whether others:

1. Keep docs in lockstep with implementation via prompts in-branch
2. Run a separate consolidation step after implementation
3. Or accept drift and periodically reconcile

Looking for concrete workflows and prompts, not principles.

[mnriem]

As Spec Kt is very flexible now with several ways of working with it have you looked at the available community extensions as per https://github.com/github/spec-kit?tab=readme-ov-file#-community-extensions ?

[MrHinsh]

Yes, and I don't see anything that relates to my ask.

[mnriem]

Please consider writing an extension or a preset if you see a gap! Or continue the discussion here on what you need in more detail so others can chime in

[MrHinsh]

This is a question on procedure with the toling, not an ask abot the tooling itself. The answer would dictate if an extension would be required or desired. However, there is as yet no answer to the questions asked.

[mnriem]

The original Spec Kit process does not address this nor will it, but we would love to hear what the community thinks here. And if they solved it with extensions, presets or workflows

[thompcd]

I've been thinking about the same thing. I'm trying to find a way to use my specs as a living definition of the product's expectations and wanting to figure out the best workflow for a team to do this.

[MrHinsh]

I'm thinking that I just bin each spec folder after I have pulled what's needed out for the docs.

I integrated some of that into the implmentation skill.

[mnriem]

Maybe the community extension named 'Archive Extension' at https://github.com/github/spec-kit?tab=readme-ov-file#-community-extensions could be of use?

[mnriem]

Note that we have just release 0.7.0 that includes Spec Kit workflows

[MrHinsh]

How does that help resolve this ask?

[mnriem]

You are describing a flow with the question "Do you continuously integrate outputs from specs/* back into your core documentation and architecture?"

The original Spec Kit process does not address this as this goes above and beyond that described process. I am suggesting that you could deliver a Spec Kit extension and/or a Spec Kit workflow that will make this possible for you. If you are missing any building blocks we would love to hear about it.