Use when creating or updating a Spec Kit project constitution, governance rules, principles, or non-negotiable constraints.
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add me-cedric/agent-compass --skill speckit-constitution --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Speckit Constitution?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/me-cedric-speckit-constitution)More formats (shields.io, HTML) on the badges page.
---
name: speckit-constitution
description: >
Use when creating or updating a Spec Kit project constitution, governance
rules, principles, or non-negotiable constraints.
risk_level: medium
writes_files: true
requires_tools: []
---
# Spec Kit Constitution
Read `AGENTS.md`, `.specify/memory/constitution.md` if present, and
`docs/workflows/spec-driven-development.md`.
## Do
1. Capture durable principles only: product boundaries, security rules, quality
gates, documentation rules, and decision ownership.
2. Keep implementation details out unless they are true governance constraints.
3. Mark unresolved governance choices as open questions.
4. Update downstream specs/plans only when the constitution change affects them.
## Done
- Constitution is updated or reviewed.
- Conflicts with `AGENTS.md` are called out.
- Open questions and validation impact are listed.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
