speckit-constitution
Skill2 starsChanged 31 days agoMITView on GitHub
Create or update the project constitution.
133 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- raojiacui/prompt-lenstheir own version, first seen Nov 16, 2026
- finolabs/vibebiztheir own version, first seen Nov 15, 2026
- jaroslawherod/micold-ai-idetheir own version, first seen Nov 15, 2026
- Kemetra/Seshat-BItheir own version, first seen Nov 15, 2026
- Azure/agent-landing-zonetheir own version, first seen Nov 14, 2026
- Azure/GPT-RAGtheir own version, first seen Nov 14, 2026
Used with
Projects with it also use speckit-agent-context-update, speckit-baseline and 5 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Microsoft AzureSkillspeckit-agent-context-update
Refresh the managed Spec Kit section in coding agent context file(s)
Also in 13 projects that use this
patterson-agentsSkillspeckit-baseline
Generate feature specifications by analyzing existing source code.
Also in 3 projects that use this
patterson-agentsSkillclaude-command-converter
Convert Claude Code commands (.claude/commands/*.md) to standard Agent Skills (skills/*/SKILL.md). Use when migrating slash commands to portable skill format, creating skills from existing commands, or standardizing command definitions across AI runtimes.
Also in 3 projects that use this
arkanSkillreview-animations
Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.
Also in 3 projects that use this
Microsoft AzureSkillagentic-workflows
Route gh-aw workflow design/create/debug/upgrade requests to the right prompts.
Also in 3 projects that use this
VercelSkillemil-design-eng
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
Also in 3 projects that use this
Other versions133 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- aetna000/atmem★ 1498% same
Wrote their own version · 132
- pmndrs/react-spring★ 29ksame name
- unoplatform/uno★ 10ksame name
- elsa-workflows/elsa-core★ 7.9ksame name
- hhyo/Archery★ 7.1ksame name
- pamburus/hl★ 3.3ksame name
- nornir-automation/nornir★ 1.6ksame name
- cloudposse/atmos★ 1.4ksame name
- Azure/agent-landing-zone★ 1.2ksame name
- Azure/GPT-RAG★ 1.2ksame name
- dotCMS/core★ 972same name
122 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-convergeSkill
- speckit-git-commitSkill
- speckit-git-featureSkill
- speckit-git-initializeSkill
- speckit-git-remoteSkill
- speckit-git-validateSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- cosmionSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 131 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
If an instruction could be either constitution content or a non-governance intent, ask for clarification before making changes.
- Very specific: line 34
After updating the constitution, list each deferred intent in a Next Actions section with an appropriate follow-up Spec Kit command, such …
- Very specific: line 41
Create or update the project constitution and store it in .specify/memory/constitution.md.
“Common” is measured: kept by at least 6 in 10 of the 131 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Speckit Constitution Skill
User Input
$ARGUMENTSScope Guard
This command's own work is limited to creating or updating the project constitution and propagating constitution-driven changes to dependent Spec Kit artifacts.
- Classify every part of the user input as constitution content or a separate non-governance intent. Feature implementation, code generation, refactoring, build, and deployment requests are examples of non-governance intents.
- You MUST NOT execute any non-governance intent. Defer each one to
Next Actions. - You MUST NOT create, modify, or delete application source files or other artifacts unrelated to the constitution workflow.
- If an instruction could be either constitution content or a non-governance intent, ask for clarification before making changes.
- After updating the constitution, list each deferred intent in a
Next Actionssection with an appropriate follow-up Spec Kit command, such as/speckit-specify, but do not invoke it. - Omit
Next Actionswhen there are no non-governance intents.
Outline
- Create or update the project constitution and store it in
.specify/memory/constitution.md.- Project name, guiding principles, non-negotiable rules
- Derive from user input and existing repo context (README, docs)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

