versioning-constitutions

What problem does it solve?

This Skill addresses the challenge of managing evolving architectural rules, tech stack changes, and foundational patterns without losing historical context or breaking existing references. It ensures that changes to core project governance are explicit, auditable, and easily reversible.

Core Features & Use Cases

• Immutable Versioning: Creates new, immutable snapshots of architectural rules (constitutions) whenever foundational patterns or tech stack elements change, preserving a clear history.
• Automated Migration: Handles the creation of new version directories, copying existing content, and updating symlinks to ensure seamless transitions between versions.
• Change Documentation: Mandates thorough documentation of all changes in meta.md, including the "what" and "why," to maintain context for future reference.
• Use Case: When your team decides to adopt a new error handling library or deprecate an old pattern, use this Skill to create a new constitution version, update the relevant files, and automatically document the change, ensuring all developers are aware and historical context is maintained.

Quick Start

Check current version

cat docs/constitutions/current/meta.md

Create new version (e.g., v2)

mkdir -p docs/constitutions/v2 cp docs/constitutions/current/*.md docs/constitutions/v2/

Update symlink

rm docs/constitutions/current ln -s v2 docs/constitutions/current