constitution

Define durable governance rules for AI-driven development projects.

3|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/xiongxianfei/rigorloop --skill constitution-xiongxianfei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: constitution
Source: https://github.com/xiongxianfei/rigorloop/tree/main/.codex/skills/constitution
Command: npx skills add https://github.com/xiongxianfei/rigorloop --skill constitution-xiongxianfei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and maintain durable governance for AI-driven development projects, clarifying rules, responsibilities, and decision rights to prevent drift and ambiguity across teams.

Core Features & Use Cases

  • Establishes a formal project constitution with sections for project purpose, source of truth order, spec-driven rules, test-driven rules, architecture boundaries, security and privacy, compatibility, verification, review, documentation, agent behavior, and fast-lane exceptions.
  • Guides teams through codifying standards and governance: onboarding a new project, onboarding a brownfield codebase, or evolving an existing project with recurring governance gaps.
  • Provides a single source of truth that can be referenced by proposals, specs, plans, and code changes to ensure alignment and auditability.

Quick Start

Draft a concise constitution that includes project purpose, source-of-truth order, and the major governance rules, then update AGENTS.md and CONSTITUTION.md.

Frequently Asked Questions about constitution

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I establish project governance rules for AI-driven development?

To establish project governance, draft a formal constitution covering project purpose, source of truth, spec-driven rules, and architecture boundaries. This creates stable rules preventing drift and ambiguity across AI-driven development teams.

What is a project constitution and how does it manage codebase quality?

A project constitution is a durable governance document that codifies standards for quality, security, and compliance. It serves as a single source of truth referenced by proposals, specs, and code changes to ensure alignment and auditability.

How do I onboard a brownfield codebase with existing governance gaps?

Onboard a brownfield codebase by codifying standards into a formal constitution that defines source-of-truth order, test-driven rules, and architecture boundaries. This evolves existing projects by closing recurring governance gaps and clarifying decision rights.

What sections should a developer-facing project constitution include?

A developer-facing project constitution should include project purpose, source of truth order, spec-driven rules, test rules, architecture boundaries, verification, documentation, agent behavior, and fast-lane exceptions to satisfy governance requirements.

How do I define architecture boundaries and spec-driven rules for AI agents?

Define architecture boundaries and spec-driven rules by updating AGENTS.md and CONSTITUTION.md with formal governance sections. This dictates agent behavior and establishes a verifiable source of truth for AI-driven code generation.

Can I use a project constitution for ongoing compliance and security verification?

Yes, a project constitution supports ongoing compliance by defining security, privacy, and verification rules within its governance structure. This provides a durable framework that satisfies auditability requirements for continuous development.