I want to start using GitHub’s Spec Kit in a monorepo (frontend + backend). From what I understand each new feature request/development, automatically generates a set of documents: a feature specification (spec.md), a technical plan (plan.md), and a breakdown of tasks (tasks.md), along with a shared constitution.md.
The constitution file stays the same across features, but the spec/plan/tasks are created anew even for minor changes.

That's why I would like to clarify a few things:

1. Should we commit all these generated files to the repo, or only keep the core docs (e.g. constitution.md and the high-level spec) and ignore the rest?
2. Do you typically include the full feature folder (spec, plan, tasks) in version control, or just parts of it?
3. How do you avoid repository bloat while still retaining useful documentation of each feature’s spec and plan?

I’m looking for how others handle this workflow and what best practice might be.

Insights on how teams manage these auto‑generated docs (especially for minor changes / bugs fixes) would be very helpful.