iikit-00-constitution

You can establish project governance by drafting a CONSTITUTION.md file that defines non-negotiable development rules, quality standards, and amendment procedures. This Skill ensures the document remains technology-agnostic to maintain relevance across future stack changes.

You need project governance principles when starting a new software project to ensure clarity and consistency before any code is written. It establishes foundational development ethics and quality standards that guide all subsequent technical decisions.

A technology-agnostic project constitution should include high-level principles, development rules, quality standards, and amendment procedures. It explicitly excludes technology-specific details to ensure the governance document remains valid during technology stack changes.

To update development rules without technology coupling, this Skill modifies the project constitution while enforcing phase separation. It prevents technology-specific details from being included, ensuring governance principles remain stable across infrastructure changes.

Yes, you can define amendment procedures for project governance rules within the generated constitution document. The Skill specifically structures these foundational rules and modification processes in a technology-agnostic manner for long-term project stability.