constitution-authoring

Guide OAK teams in creating decision-driven engineering constitutions with RFC 2119 compliance.

62|6|Updated Sep 12, 2024
One-click install
npx skills add https://github.com/sirkirby/unifi-network-rules --skill constitution-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: constitution-authoring
Source: https://github.com/sirkirby/unifi-network-rules/tree/main/.claude/skills/constitution-authoring
Command: npx skills add https://github.com/sirkirby/unifi-network-rules --skill constitution-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams in creating robust, decision-driven engineering constitutions that align standards with project reality and stakeholder needs.

Core Features & Use Cases

  • Decision-Driven Constitution Creation: captures core decisions on testing, architecture, documentation, governance, and maintenance.
  • RFC 2119 Language Integration: ensures explicit obligation levels are stated for all requirements.
  • Reality Alignment & Governance: provides guidance on current-state assessment, timelines, amendment processes, and versioning.
  • Structured Documentation: supports a clear, auditable framework for ongoing governance of engineering standards.

Quick Start

Follow the workflow: /oak.constitution-create → Analyze & Gather Decisions → Generate → /oak.constitution-validate

Frequently Asked Questions about constitution-authoring

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

FAQPage Schema
How do I create an engineering constitution for project governance?

An engineering constitution captures core decisions on testing, architecture, documentation, and governance to align standards with project reality. It provides an auditable framework for ongoing engineering standards management and maintenance.

How do I apply RFC 2119 language to engineering documentation?

RFC 2119 language integration ensures explicit obligation levels are stated for all requirements within your engineering constitution. This creates auditable governance by clearly defining mandatory, recommended, and optional behaviors across project standards.

What is the best way to document engineering decisions for auditable governance?

Decision-driven documentation captures core decisions on architecture, testing, and maintenance alongside structured rationale. This yields a clear, auditable framework that supports versioning and ongoing governance of engineering standards across the project lifecycle.

How do I structure a project constitution that aligns with current development reality?

Structure a project constitution by assessing current-state realities and timelines before capturing core decisions. Include amendment processes and versioning to ensure the governance framework adapts to evolving engineering standards and stakeholder needs.

Does decision-driven governance work for existing engineering projects?

Decision-driven governance suits existing engineering projects by performing a current-state assessment before defining standards. It captures existing architecture and testing decisions to establish an auditable constitution that reflects actual project reality.