Skip to main content
skill CX Codex

speckit-constitution — Claude Code skill: project constitution

This skill writes and updates the project constitution in .specify/memory/constitution.md, turning your principles into a versioned governance doc.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add dceoy/speckit-agent-skills --skill speckit-constitution -a claude-code
Open on GitHub

What speckit-constitution does

The skill maintains the constitution — the document of principles that other Spec Kit commands read at runtime. You pass principles or values as the argument, and it maps them onto the template: a name line, the non-negotiable rules, a rationale. If .specify/memory/constitution.md already exists, it loads the current values and amendments, then preserves what still applies.

Scope is deliberately narrow. Feature work, code generation, refactoring and deployment requests are not executed; the skill extracts them as deferred intents and lists a follow-up command such as /speckit-specify under Next Actions. Application source files, routes, components and tests stay untouched. So asking it to fix a route while it edits the constitution gets you nothing.

Before the update it checks .specify/extensions.yml for hooks.before_constitution. Mandatory hooks run and the skill waits for the result; optional ones are printed with the command to invoke by hand. The project needs the Spec Kit structure with a .specify/ directory and .specify/scripts/bash/resolve-template.sh — if template resolution fails, the skill stops instead of continuing on a partial scaffold. Version bumps follow semver: MAJOR for removed or redefined principles, MINOR for a new section, PATCH for wording fixes.

What it helps with

  • pin project principles into one document
  • amend the constitution without losing earlier values
  • keep constitution edits separate from feature code
  • bump the constitution version by semver rules
  • check extension hooks before amending governance

Example prompts for the agent

  • update the constitution with three principles: testability, simplicity, backward compatibility
  • add a mandatory review-before-merge principle to the constitution
  • review the project constitution and propose a new version

How to install speckit-constitution

1Skills CLI (Vercel)

npx skills add dceoy/speckit-agent-skills --skill speckit-constitution -a claude-code

2Manually: put the files in place

~/.claude/skills/speckit-constitution/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/speckit-constitution/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about speckit-constitution

How do I install speckit-constitution in Claude?

Run npx skills add dceoy/speckit-agent-skills --skill speckit-constitution -a claude-code. The skill file then sits at ~/.claude/skills/speckit-constitution/SKILL.md.

What does speckit-constitution do?

It creates or updates the project constitution at .specify/memory/constitution.md from the principles you supply, bumps the version by semver and checks hooks before writing.

What does the skill need to run?

A Spec Kit project structure with a .specify/ directory. The constitution template is resolved through .specify/scripts/bash/resolve-template.sh, and the skill halts with a resolution error if that fails.

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set10

speckit-plan Executes implementation planning workflows inside spec-kit projects to produce research notes and interface contracts. CX Codex +1 2,500installs speckit-specify Turns a plain-language feature description into a spec folder: short name, number, spec.md from the template, and a path saved in .specify/feature.json. CX Codex +1 2,600installs speckit-implement Executes development tasks from tasks.md in spec-kit projects. It validates readiness checklists, triggers pre-implementation hooks, and configures ignore files. CX Codex +1 2,400installs speckit-tasks This skill turns plan.md and spec.md into a tasks.md ordered by dependencies and user stories. Useful when the feature is already described in spec-kit but the work queue is not. CX Codex +1 2,400installs speckit-clarify Scans a feature spec for gaps, asks up to 5 targeted questions and writes the answers back into the spec file. CX Codex +1 2,200installs speckit-taskstoissues Turns tasks from tasks.md into dependency-ordered GitHub issues. The skill is marked deprecated and points to a replacement extension. CX Codex +1 1,500installs speckit-baseline This skill reads your source files and turns them into a framework-agnostic feature spec with user stories and requirements. Useful when a codebase exists but written requirements do not. CX Codex +1 1,500installs speckit-checklist Generates a custom requirements-quality checklist for a feature specification. It helps reviewers catch ambiguous phrasing and missing edge cases before coding starts. CX Codex +1 1,500installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor