governancelisted

Use when deciding which document canonically owns a topic, whether it is safe to mark documentation or an implementation plan Completed/Archived/Deprecated, whether a documentation change is acceptance-ready, or when running the structure/metadata/old-path/manifest/reindex audits before accepting a change. Also use when a state record (a target README's `## Status` block, or `process-state.yaml`) may have drifted, when deciding whether async messaging/orchestration/auth/external-provider work needs a Mermaid sequence diagram before it can be accepted, or when checking a change against the documentation stop conditions before treating it as done. Covers both canonical-ownership/lifecycle policy (`documentation-governance.md`) and the acceptance-blocking quality gates and stop conditions built on top of it (`quality-gates.md`) — the two are companion documents in this workspace's own governance/README.md and are not meant to be applied separately.
BhangeeF16/kaizen · ★ 0 · Data & Documents · score 67

Install: claude install-skill BhangeeF16/kaizen

# Governance This is a meta-skill: a rule that applies across every stage rather than belonging to one. It covers two tightly coupled documents this workspace's own `governance/README.md` names as companions — `documentation-governance.md` is the canonical owner for ownership/lifecycle policy, `quality-gates.md` is the canonical owner for the acceptance-blocking checks built on top of that policy — read live from this plugin's own source files every time this skill runs, so there is no separate paraphrased copy anywhere for either to drift against. ## Documentation governance (live) !`cat "${CLAUDE_PLUGIN_ROOT}/skills/governance/documentation-governance.md"` ## Documentation quality gates (live) !`cat "${CLAUDE_PLUGIN_ROOT}/skills/governance/quality-gates.md"` ## Instructions 1. Before marking any document `Completed`, confirm acceptance evidence actually exists (Lifecycle Rules above); before marking one `Archived`, confirm active navigation no longer depends on it. Never mark either status because a plan section was merely edited — see the Delivery Gates section above. 2. When a target's state might have drifted, compare the state record against the artifacts it describes and repair both together in the same change set (see the `delivery-governance` meta-skill for the full state contract) — state records are hand-maintained; there is no mechanical writer. 3. Before accepting a documentation change, run the audits named in the Quality Gates content above (structure, m