governance

Create Architecture Decision Records and Change Requests with Markdown templates.

3|Updated Jan 26, 2026

Search Tags:#workflow #architecture #templates #documentation #governance #ADR #CR

Ready to run

npx skills add https://github.com/desek/governance --skill governance-desek

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: governance
Source: https://github.com/desek/governance/tree/main/skills/governance
Command: npx skills add https://github.com/desek/governance --skill governance-desek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Governance teams often struggle to capture architectural decisions and requirement changes in a consistent, auditable format. This skill provides templates and workflows to create ADRs and CRs that are easy to review, version, and trace.

Core Features & Use Cases

ADR creation for architectural decisions to document context, options, and rationale.
CR creation for requirement changes to capture scope, impact, and acceptance criteria.
Lifecycle guidance with standard frontmatter, naming conventions, and traceability links to related ADRs/CRs.

Quick Start

Use the governance skill to open a new ADR or CR with a descriptive title, populate required frontmatter, and set the initial status to "proposed".

Frequently Asked Questions about governance

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

FAQPage Schema

How do I document architectural decisions using ADR templates?▼

To document architectural decisions using ADR templates, create a new record with a descriptive title, populate the required structured frontmatter, and set the initial status to proposed to capture context, options, and rationale.

What is the best way to track requirement changes and scope impact?▼

The best way to track requirement changes and scope impact is by creating Change Requests (CRs) that capture scope, impact, and acceptance criteria using standardized Markdown templates and lifecycle workflows.

How do ADRs and CRs maintain traceability across software projects?▼

ADRs and CRs maintain traceability across software projects by applying standardized naming conventions, structured frontmatter, and lifecycle guidance with traceability links connecting related records.

Can I use governance workflows for organizational change requests?▼

Yes, you can use these governance workflows for organizational change requests because the ADR and CR lifecycle guidance applies across both software projects and organizational governance to document technology choices and scope changes.

What frontmatter and naming conventions are required for ADR creation?▼

ADR creation requires structured frontmatter and standardized naming conventions to ensure records are easy to review, version, and trace throughout their lifecycle from proposed to accepted status.