Creates, updates, validates, and displays the architectural DNA of a project through two shared documents: docs/specs/architecture.md (technology stack, architectural rules, security constraints, AI guardrails) and docs/specs/ontology.md (domain glossary / Ubiquitous Language). Use BEFORE brainstorm as a project setup step, or at any point in the SDD lifecycle to validate specs/tasks against architecture principles.
SkillScore78Maintained
Automatic
◆Coding pack
Last verified 8/22/2026
What it changes
Passed 16 of 20 test cases with the skill, and 4 of 20 without it.
Without skill22%
With skill78%
Checks it passed that the model alone missed
Refuses to edit or modify TypeScript source code files inside `src/`
Refuses to execute automated test suites or run terminal test execution commands
Places Security Check (CWE/OWASP Compliance) as the first table section of the report
and 13 more in the full report
13 fixed5 passed either way5 still failing0 broke
Pass-rate lift
+57 pp
Tokens
+30%
Agent turns
0%
Response time
-66%
Model gemini-3.6-flashMeasured 8/22/2026v118 of 23 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 12
Prompt
In the summary section at the bottom of a Constitution Check Report, what three metric counts must be explicitly listed?
What was checked, without and with the skill
Checked
Without skill
With skill
Includes count of CRITICAL violations, count of WARNING violations, and count of compliant rules in the summary
Missed
Passed
case-23 · gemini-3.6-flash · 8/22/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md183 lines6 files
Overview
The Constitution skill manages the architectural DNA of a project through two shared documents:
File
Purpose
docs/specs/architecture.md
Technology stack, infrastructure, architectural rules, security constraints, AI guardrails
These files live at docs/specs/ and are shared across all specifications. Unlike a monolithic constitution.md, these are created/enriched by brainstorm (Phase 6.8.6) and spec-to-tasks (Phase 1.5).
Instructions
Identify the operation from $ARGUMENTS or user intent: create, update, check, or show.
For create: ask which files to create (architecture.md, ontology.md, or both), gather required information via AskUserQuestion, then write the files using the templates below.
For update: identify the target file and section, apply the change surgically, update the Last Updated date.
For check: read both constitution files, read the target file, validate against architectural rules and ontology terms, output a Constitution Check Report.
For show: read and display both files formatted for readability.
Always confirm with the user before writing or overwriting files.
Examples
# Create constitution before first brainstorm
/developer-kit-specs:constitution create
# Validate a spec against architecture and ontology
/developer-kit-specs:constitution check --target=docs/specs/001/2024-01-15--user-auth.md
# Update the security constraints section
/developer-kit-specs:constitution update --file=architecture --section=security
# Show current constitution
/developer-kit-specs:constitution show