Is it recommended to generate the full set of main specs upfront for an in-progress project?

[Yannis-01]

Would it be advisable to pre-generate complete main specs for ongoing development projects?

[HowardYan888]

Are you trying to generate specifications based on an existing project?

[Fj-ivy]

Are you trying to generate specifications based on an existing project?

I have the same question. When adopting OpenSpec in a project for the first time, is it recommended to generate specs based on existing business modules, or to establish specs incrementally during development?

• If generating in one go, how can we generate specs based on existing business modules?

Besides, how to generate the config.yaml file? Do you have a recommended template for its main contents?

[clay-good]

Good question, and the docs now take a clear position: no, do not pre-generate them.

From Using OpenSpec in an Existing Project: "Resist the urge to back-fill everything. Writing specs for code you aren't changing feels productive and usually isn't. Those specs go stale, because nothing forces them to track reality."

Build them incrementally instead. Every archived change merges its delta into openspec/specs/, so the areas you actually touch end up documented, and the rest stays honestly blank rather than confidently wrong.

@Fj-ivy that covers your follow-up too. Guide shipped in #1237 (v1.6.0), so closing.