sdd-constitution

Define project governance with semantic versioning and change-management procedures.

143|10|Updated Feb 24, 2026

Search Tags:#templates #versioning #specifications #compliance #constitution #governance #process

Ready to run

npx skills add https://github.com/pgermishuys/opencode-weave --skill sdd-constitution-pgermishuys

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-constitution
Source: https://github.com/pgermishuys/opencode-weave/tree/main/examples/config/github-speckit/skills/sdd-constitution
Command: npx skills add https://github.com/pgermishuys/opencode-weave --skill sdd-constitution-pgermishuys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a formal, reusable Constitution for governing project principles, versioning, and change management across specifications, plans, and tasks.

Core Features & Use Cases

Template-driven governance with MUST/SHOULD language to enforce consistent decision-making.
Versioning guidance and change-management procedures for semantic versioning of artifacts.
Templates and governance procedures for audit, compliance, and onboarding new teams.

Quick Start

Define your project constitution by creating a SKILL with frontmatter name/description and a template for governance.

Frequently Asked Questions about sdd-constitution

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

FAQPage Schema

What is project governance and why do I need a formal constitution for my software specifications?▼

Project governance through a formal constitution enforces consistent decision-making using MUST/SHOULD language, ensuring strict versioning, compliance, and change-management workflows across all software specifications, plans, and tasks.

How do I enforce semantic versioning rules across project plans and tasks?▼

You enforce semantic versioning by implementing a frontmatter-based skill entry that defines strict versioning rules and change-management procedures, applying structured governance templates to your project plans and tasks.

Can I use template-driven governance for onboarding new teams and audit compliance?▼

Yes, template-driven governance provides standardized procedures and MUST/SHOULD enforcement language specifically designed to facilitate audit compliance, standardize decision-making, and onboard new teams to project principles.

What's the best way to formalize project principles and change-management workflows?▼

The best way to formalize project principles is creating a structured constitution with frontmatter-defined metadata that documents governance procedures, enforces semantic versioning, and applies consistent templates across artifacts.

Do I need specific dependencies or components to set up a project constitution?▼

No specific dependencies or components are required to set up a project constitution; it relies on frontmatter-based skill entries with name and description fields to define and enforce governance procedures natively.

When should I not use a formal constitution for governing project specifications?▼

A formal constitution is not ideal for projects lacking strict compliance requirements or those needing rapid, flexible iteration, as its MUST/SHOULD governance language and rigid change-management workflows enforce strict versioning control.