Skip to content

The /speckit.implement command does not load constitution.md — governance gap in code generation #2459

@mnriem

Description

@mnriem

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.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions