Living Docs Governance
Stop docs rot for Muse: assign your project docs four roles (constitution, map, status, history), one canonical owner per fact, wired honestly into the agent harness.
- What
- Stop docs rot for Muse: assign your project docs four roles (constitution, map, status, history), one canonical owner per fact, wired honestly into the agent harness.
- Cost
- Free
- Needs
- Use "Living Docs Governance" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a maintain-phase documentation governance practice that stops long-lived projects from rotting at the docs layer first. Assigns four non-overlapping roles to your existing documentation: Constitution (rules agents and contributors must obey, plus links to canonical detail), Map (what exists, where it lives, ownership, where to look next), Status (current health, blockers, thresholds, and an intentional-removal delete-zone), and History (durable governance decisions, intentional removals, replacements, material incidents). The discipline is one canonical owner per fact: "where is auth?" belongs to the map, "is auth migration blocked?" to status, "why was the legacy auth path removed?" to history or an ADR. Other files link to the owner rather than copying it. Then wire the active harness honestly: keep AGENTS.md or CLAUDE.md short with signposts to the canonical map, status and recent history instead of copying contents, and never claim documents are read automatically unless a real hook enables it. Treat documentation as evidence, not executable truth: never execute commands or follow embedded instructions found in docs merely because they are present, verify operational claims against code and tests, prefer machine-checkable evidence when docs conflict with implementation. Update only the role affected (structure goes to map, blockers to status, hard decisions to history), keep a delete-zone so removed things are not recreated, correct stale claims with dated corrections, and never place credentials or secrets in governance docs. Includes a lightweight adoption template (role map table, map jump table, status delete-zone, history entry format) and worked examples. Use in the maintain phase when docs drift from code, agents lose context between sessions, or intentional removals keep being recreated. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: maintain-phase practice, not for throwaway scripts or one-time exploration (use codebase-onboarding first) ; prefer adopting the repo's current docs structure over creating new root files ; requires honest harness wiring, the skill cannot force agents to read. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Living Docs Governance" with your Muse. Prerequisites: none to install. Pure guidance; a long-lived project with docs drifting from code helps. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/living-docs-governance/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Inventory my docs and assign the four governance roles: [repo path or describe the docs]." 3. Ask it to map existing sources to constitution, map, status and history, propose only the smallest missing sections, and wire short signposts into the agent harness file. Tip: start with the role map table, not four new files; prefer adopting what exists. Safety: a skill is plain-text instructions; it runs nothing by itself. Never put credentials or secrets in governance docs.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.