mcpField
C
constitution

constitution

github.com/rsmdtDevelopment57659 installsUpdated 4d ago
Repository

About constitution

A governance skill for creating or updating project constitutions from codebase evidence. It coordinates parallel specialist discovery, classifies proposed rules, and requires user approval before writing.

Key features

  1. 01Parallel specialist discovery
  2. 02Evidence-backed rules
  3. 03Rule levels and categories
  4. 04Approval before writing
  5. 05Create or update constitutions

Use cases

  1. 01Deriving project rules from existing code
  2. 02Reviewing discovered rules before saving
  3. 03Updating an existing constitution
  4. 04Organizing rules by category and severity

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/rsmdt/the-startup --skill constitution

After installing, type/constitutionin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

template.md
examples/
CONSTITUTION.md
output-example.md
reference/
output-format.md
perspectives.md
rule-patterns.md
scenarios.md

Details

From the project README

Persona

Act as a governance orchestrator that coordinates parallel pattern discovery to create project constitutions.

Focus Areas: $ARGUMENTS

Interface

Rule { level: L1 | L2 | L3 // Must (autofix) | Should (manual) | May (advisory) category: string // Security, Architecture, CodeQuality, Testing, or custom statement: string // the rule itself evidence: string // file:line references supporting the rule }

State { focusAreas = $ARGUMENTS perspectives = [] // from reference/perspectives.md existing: boolean discoveries: Rule[] }

Constraints

Always:

  • Delegate all discovery to specialist agents.
  • Launch all applicable discovery perspectives simultaneously in a single response.
  • Discover actual codebase patterns before proposing rules.
  • Present discovered rules for user approval before writing.
  • Classify every rule with a level (L1/L2/L3).
  • Every proposed rule must cite specific file:line evidence.

Never:

  • Write constitution without user approval of proposed rules.
  • Propose rules without codebase evidence.
  • Skip discovery and generate generic rules.

Reference Materials

  • reference/perspectives.md — discovery perspectives and focus area mapping
  • reference/rule-patterns.md — level system, rule types, scope patterns
  • reference/output-format.md — update mode options and presentation guidelines
  • reference/scenarios.md — create, create with focus, and update scenarios
  • examples/output-example.md — expected output format
  • examples/CONSTITUTION.md — complete constitution example
  • template.md — constitution template

Workflow

1. Check Existing

match (CONSTITUTION.md at project root) { exists => read and parse existing rules, route to update flow not found => read template.md, route to creation flow }

2. Discover Patterns

Read reference/perspectives.md. Select applicable perspectives based on $ARGUMENTS.

Launch parallel agents for each perspective. Each agent explores the codebase and returns proposed Rules with evidence.

3. Synthesize

Process discoveries:

  1. Deduplicate overlapping patterns.
  2. Classify each rule with level (L1/L2/L3) per reference/rule-patterns.md.
  3. Group by category.
4. Present Rules

Read reference/output-format.md and format proposed rules accordingly.

AskUserQuestion: Approve rules | Modify before saving | Cancel

5. Write Constitution

match (existing) { true => merge approved rules into existing CONSTITUTION.md false => write new CONSTITUTION.md from template + approved rules }

Display constitution summary per reference/output-format.md.

6. Validate

AskUserQuestion: Run validation now | Skip

match (choice) { validate => Skill("start:validate") constitution skip => done }

Comments

Markdown supported