write-constitution

Extract principles from project documentation and draft them into a constitution document.

1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/g-bastianelli/nuthouse --skill write-constitution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-constitution
Source: https://github.com/g-bastianelli/nuthouse/tree/main/acid-prophet/skills/write-constitution
Command: npx skills add https://github.com/g-bastianelli/nuthouse --skill write-constitution

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the creation of project constitutions, ensuring every spec and audit is held to immutable principles, saving time on governance and compliance.

Core Features & Use Cases

  • Project Constitution Creation: Build a set of immutable articles based on project needs.
  • Spec and Audit Enforcement: Ensures that each article acts as a gate in audits and specs.
  • Use Case: When a project needs to establish and maintain a set of governing principles, this Skill can help draft, ratify, and enforce them.

Quick Start

Invoke the 'write-constitution' skill to generate a constitution for your project.

Frequently Asked Questions about write-constitution

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

FAQPage Schema
How do I create a project constitution for technical governance?

Creating a project constitution involves extracting governing principles from project documentation and drafting them into a single immutable document. This process establishes technical governance by ensuring all project specs and audits adhere to foundational articles.

How do I enforce spec compliance and audit requirements across a software project?

Enforce spec compliance and audit requirements by establishing immutable project principles that act as automated gates. This ensures every specification review validates against the governing constitution, maintaining strict code compliance.

What is technical governance and when do I need a project constitution?

Technical governance is the enforcement of immutable principles across a software project, and you need a project constitution when your tech team requires strict spec audits. It establishes a single source of truth for all code compliance and architectural decisions.

Can I build immutable governing principles from existing project documentation?

Yes, you can build immutable governing principles by extracting articles directly from existing project documentation and repository files. This extracts established norms into a unified technical governance document for spec audits.

What is the best way to automate code compliance audits for a development team?

The best way to automate code compliance audits is to establish a project constitution that acts as an automated enforcement gate. This validates specifications against immutable principles extracted from your repository, saving time on governance.

What are the limitations of using immutable principles for project governance?

A limitation of using immutable principles for project governance is that once articles are ratified, enforcing them requires continuous access to project documentation and the repository. This makes the spec audit process rigid and less adaptable to rapid architectural changes.