Is the constitution read during /speckit.specify command?

[arrowwood49]

I'm trying to understand when the constitution is actually read during the spec-kit workflow, as I' have found contradictory documentation. I don't see any reference of reading the constitution in /speckit.specify command or template but README states:
https://github.com/github/spec-kit/blob/main/README.md?plain=1#L536

"This step creates or updates the .specify/memory/constitution.md file with your project's foundational guidelines that the coding agent will reference during specification, planning, and implementation phases."

Does the /speckit.specify command actually read the constitution when generating spec.md?
If not, how do we include project-specific terminology and principles when running the workflow for different features? For example, should architectural principles defined in the constitution be manually referenced in each feature spec, or is there another mechanism to ensure consistency across specifications?

[davesharpe13]

I have noticed that specify doesn't read the constitution. I guess the designers thought the spec will be WHAT/WHY and the constitution relates to HOW of the plan stage, where it is read. I add a reference to constitution.md in my AGENTS.md myself.