[best practices] Project overview vs Feature specs

[borcenty]

I love it how I can describe a feature and spec-kit creates a separate sub-folder in specs and all the files there. I'm wondering though.. Should I somewhere have a document with project overview? Like a general description of what we're building so while working on a specific feature - the model actually understands that this feature is a part of much bigger software? Constitution doesn't seem like the right place.. so where?

[adam-paterson]

I put mine in .specify/overview.md or .specify/background.md. Then in the agent steering prompt (CLAUDE.md, AGENTS.md) I'll instruct the agent to gather context from the above write-ups before planning any features.

That seems to be enough for now to keep that instruction fresh and the underlying model is smart enough to realise when we've requested a /specify, /plan or /tasks that it should read that file first.