skills.rest
bennybennison
bennybennisonCOMMUNITY
Explore all skills by this author →
GitHub

document-ownership

Establish document ownership hierarchies and prevent duplication across governance documents.

Updated Apr 11, 2026
Search Tags:#documentation#ownership#audit#governance#hierarchy#matrix
One-click install
npx skills add https://github.com/bennybennison/agent-toolkit --skill document-ownership
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: document-ownership
Source: https://github.com/bennybennison/agent-toolkit/tree/main/skills/document-ownership
Command: npx skills add https://github.com/bennybennison/agent-toolkit --skill document-ownership

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizations often accumulate multiple governance documents that overlap, contradict, or become stale, leading to confusion and duplicated effort.

Core Features & Use Cases

  • Ownership Matrix: Defines a single owner for each document type and establishes a clear hierarchy of truth.
  • Duplication Prevention: Provides rules and checklists to ensure lower‑level documents reference higher‑level ones instead of repeating content.
  • Audit Checklist: Enables quarterly reviews to verify ownership, references, and document length limits.
  • Use Case Example: When onboarding a new team, run the skill to generate the ownership matrix and audit checklist, ensuring every document has an assigned owner and no duplicated content.

Quick Start

Request a document ownership matrix for the current project.

Frequently Asked Questions about document-ownership

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

FAQPage Schema
How do I prevent duplication and conflicts across software governance documents?▼

Prevent duplication by establishing a document ownership matrix that defines a single owner for each governance layer and enforces reference rules where lower-level documents cite higher-level ones instead of repeating content.

What is a document ownership matrix and how does it establish a hierarchy of truth?▼

A document ownership matrix is a governance framework that assigns a single owner to each document type and establishes a clear hierarchy, ensuring higher-level documents like CONSTITUTION take precedence over lower-level specifications and change logs.

How do I audit existing governance documents for stale content and reference violations?▼

Audit governance documents by running a quarterly review checklist that verifies assigned ownership, validates that lower-level documents reference higher-level ones, and checks that document length limits are maintained.

Can I use this approach to manage onboarding documentation for a new software team?▼

Yes, you can generate an ownership matrix and audit checklist during team onboarding to ensure every governance document, from specifications to change logs, has an assigned owner and contains no duplicated content.

What types of documentation layers are supported by this hierarchy governance model?▼

This governance model supports documentation layers such as CONSTITUTION, AGENTS, SKILL, specifications, and change logs across software development projects, applying reference rules to eliminate overlap and contradictions.

Related Skills

Explore More Product & Management Skills→
castrojocastrojo
2

governance-subprojects

Documents CNCF project subprojects including ownership, scope, and leadership in a GOVERNANCE-subprojects.md file.

Community
Intermediate
tommygeocotommygeoco
20

ui-audit

Audit UI designs against UX principles for hierarchy, accessibility, and usability issues.

Community
Intermediate
hex0xdeadbeefhex0xdeadbeef
47

code-review-rules

Enforce severity, decision matrix, and escalation rules during code reviews.

Community
Advanced
k1lgork1lgor
4

verification-before-completion

Run automated tests, linters, type checks, and build processes before task completion.

Community
Intermediate