docs-governance-organization

Audit and organize Markdown documentation repositories with governance and indexing rules.

5|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill docs-governance-organization
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-governance-organization
Source: https://github.com/rafael-fae/agent-ops-worflow/tree/main/archive/skills/operacao/docs-governance-organization
Command: npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill docs-governance-organization

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams audit and organize Markdown documentation in planning repositories, especially when files are scattered, unindexed, or mixed with code. It preserves existing content while establishing structure, traceability, and safe navigation across documents.

Core Features & Use Cases

  • Documentation Audits: Inventory Markdown files, classify directories, and detect repositories that contain code where planning docs should live.
  • Governance & Standards: Define frontmatter rules, index requirements, cross-link policies, and two-tier documentation architecture between active docs and historical references.
  • Safe Reorganization: Create master indexes, bridge documents, and organizational rules before moving files to avoid broken links and accidental loss.
  • Real-World Use Case: A planning repository grows messy over time, with deep-dive docs, refinements, prompts, and legacy references spread across multiple folders; this Skill helps catalog everything, set rules, and produce a safer structure for ongoing work.

Quick Start

Ask the skill to audit a documentation repository, identify valid Markdown planning assets, and produce an organized governance plan with indexes, rules, and cross-link guidance.

Frequently Asked Questions about docs-governance-organization

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

FAQPage Schema
How do I organize scattered Markdown documentation in a planning repository?

Auditing Markdown documentation involves inventorying files, classifying directories, and detecting mixed code and documentation assets to establish structure, traceability, and safe navigation across documents without losing existing content.

What is the best way to enforce documentation governance and prevent content drift?

Enforcing documentation governance requires defining frontmatter rules, index requirements, and cross-link policies, alongside creating a two-tier architecture separating active docs from historical references to prevent drift.

How do I safely reorganize Markdown files without breaking cross-links?

Safely reorganizing Markdown files without breaking cross-links requires creating bridge documents, master indexes, and organizational rules before moving files to avoid accidental loss and navigation errors.

Can I audit a repository with mixed code and legacy planning docs?

Yes, you can audit a repository with mixed code and legacy planning docs by inventorying Markdown files, classifying directories, and identifying valid planning assets to catalog everything for a safer structure.

When do I need a two-tier documentation architecture for my Markdown files?

A two-tier documentation architecture for Markdown files is needed when managing a planning repository with deep-dive docs, refinements, and legacy references spread across multiple folders requiring active and historical separation.