Problem
The implement command template (templates/commands/implement.md) loads spec, plan, tasks, data-model, contracts, research, and quickstart — but never loads constitution.md.
This means code generation during /speckit.implement is completely unaware of project principles, non-negotiable rules, and governance constraints defined in the constitution.
Meanwhile, /speckit.analyze heavily references the constitution (11+ mentions), treats it as non-negotiable authority, and has a dedicated "Constitution Alignment" detection pass. /speckit.plan also loads it and fills a Constitution Check section.
The result is a broken feedback loop: /speckit.analyze flags constitution violations, but /speckit.implement will re-introduce the same violations on the next cycle because it never sees the rules.
Evidence
templates/commands/implement.md — zero occurrences of "constitution"
templates/commands/analyze.md — 11+ references, dedicated Constitution Alignment pass
templates/commands/plan.md — loads /memory/constitution.md, fills Constitution Check
Expected behavior
/speckit.implement should load constitution.md (when it exists) alongside the other spec artifacts, so that generated code respects project governance constraints without requiring a separate analyze pass to catch violations after the fact.
Suggested fix
Add constitution.md to the file-loading section of templates/commands/implement.md, similar to how plan.md loads it:
- IF EXISTS: constitution.md
This is a 1–2 line template change.
Problem
The implement command template (
templates/commands/implement.md) loads spec, plan, tasks, data-model, contracts, research, and quickstart — but never loadsconstitution.md.This means code generation during
/speckit.implementis completely unaware of project principles, non-negotiable rules, and governance constraints defined in the constitution.Meanwhile,
/speckit.analyzeheavily references the constitution (11+ mentions), treats it as non-negotiable authority, and has a dedicated "Constitution Alignment" detection pass./speckit.planalso loads it and fills a Constitution Check section.The result is a broken feedback loop:
/speckit.analyzeflags constitution violations, but/speckit.implementwill re-introduce the same violations on the next cycle because it never sees the rules.Evidence
templates/commands/implement.md— zero occurrences of "constitution"templates/commands/analyze.md— 11+ references, dedicated Constitution Alignment passtemplates/commands/plan.md— loads/memory/constitution.md, fills Constitution CheckExpected behavior
/speckit.implementshould loadconstitution.md(when it exists) alongside the other spec artifacts, so that generated code respects project governance constraints without requiring a separate analyze pass to catch violations after the fact.Suggested fix
Add
constitution.mdto the file-loading section oftemplates/commands/implement.md, similar to howplan.mdloads it:This is a 1–2 line template change.