Create Architecture Decision Records and Change Requests with Markdown templates.
npx skills add https://github.com/desek/governance --skill governance-desek
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
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.
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".
High-intent search queries and answers about installing and using this skill.
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.
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.
ADRs and CRs maintain traceability across software projects by applying standardized naming conventions, structured frontmatter, and lifecycle guidance with traceability links connecting related records.
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.
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.
heimeshoffGuide a Socratic brainstorm to produce vision.md and an initial context map.
joshbandValidate YAML frontmatter metadata and generate auditable change history for LocusQ documentation.
jpoutrinAutomate PRD and FRD lifecycle management with naming, status, and archival rules.
Clay-HHKRoute code changes to a reviewer workflow for pre-merge quality assurance.
