constitution-creation
Establish project governing principles including dev guidelines, code quality standards, testing policies, UX requirements, performance benchmarks, and security constraints.
Best use case
constitution-creation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Establish project governing principles including dev guidelines, code quality standards, testing policies, UX requirements, performance benchmarks, and security constraints.
Teams using constitution-creation should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/constitution-creation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How constitution-creation Compares
| Feature / Agent | constitution-creation | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Establish project governing principles including dev guidelines, code quality standards, testing policies, UX requirements, performance benchmarks, and security constraints.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Constitution Creation ## Overview Establish the project constitution -- the governing document that defines development principles, quality standards, and constraints for all subsequent specification and implementation work. ## When to Use - Starting a new project that needs governance foundations - Formalizing existing project standards into a constitution - Updating governance principles for an evolving project - Before writing specifications for a new feature area ## Distinction from Specification - **Constitution**: Defines project-wide governance (HOW the project operates) - **Specification**: Defines feature-level requirements (WHAT to build) ## Process 1. **Gather context** - Assess project type, audience, compliance needs, existing standards 2. **Define dev guidelines** - Coding standards, branching strategy, review process 3. **Set code quality standards** - Linting, formatting, complexity limits, naming conventions 4. **Establish testing policies** - Coverage thresholds, test types, CI requirements 5. **Specify UX requirements** - Accessibility, responsiveness, performance budgets 6. **Define performance benchmarks** - Load times, throughput, memory limits 7. **Establish security constraints** - Auth, data handling, vulnerability policies 8. **Document architecture principles** - Modularity, dependencies, extensibility 9. **Human review** - Approve constitution before proceeding ## Tool Use Invoke via babysitter process: `methodologies/spec-kit/spec-kit-specification` (constitution phase) Full pipeline: `methodologies/spec-kit/spec-kit-orchestrator`
Related Skills
constitutional-ai-prompts
Constitutional AI and safety guardrail prompts for aligned LLM behavior
Plan Creation
Create a structured task_plan.md with phases, goals, and checkbox tracking for persistent planning.
spec-creation
Feature specification creation from codebase research. Produces requirements, acceptance criteria, architecture decisions, implementation plans, and risk analysis.
Product Brief Creation
Create comprehensive product briefs from market, domain, and technical research.
PRD Creation
Create Product Requirements Documents through structured discovery using Jobs-to-be-Done framework.
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.