mcaf-documentation

Organize repository documentation structure and source-of-truth placement.

4|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/managedcode/MCPGateway --skill mcaf-documentation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcaf-documentation
Source: https://github.com/managedcode/MCPGateway/tree/main/.codex/skills/mcaf-documentation
Command: npx skills add https://github.com/managedcode/MCPGateway --skill mcaf-documentation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses issues with missing, outdated, duplicated, or hard-to-navigate documentation within a repository. It helps establish a clear source-of-truth and improve the quality of durable engineering guidance.

Core Features & Use Cases

  • Documentation Structure: Organizes and refines the overall structure and navigation of repository documentation.
  • Source-of-Truth Placement: Ensures information is located in its most appropriate and canonical place.
  • Writing Quality: Improves the clarity and maintainability of engineering documentation.
  • Use Case: When a project's documentation is scattered, inconsistent, or difficult for new engineers to follow, this Skill can create a clean, navigable structure that accurately reflects the codebase and workflows.

Quick Start

Use the mcaf-documentation skill to clean up the repository's documentation structure.

Frequently Asked Questions about mcaf-documentation

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

FAQPage Schema
How do I structure engineering documentation to fix scattered and outdated docs?

To structure engineering documentation, you refine the repository's overall navigation and writing quality, ensuring each durable fact has a single home and entry pages route readers correctly. This solves issues with missing, stale, or duplicated repository docs.

What is the best way to establish a single source of truth for repository documentation?

The best way to establish a source of truth is to place information in its most canonical location within the repository. This documentation refinement process ensures each durable engineering fact has a single, authoritative home to prevent duplication.

How do I create navigable engineering docs for new engineers?

You create navigable engineering docs by organizing the repository's documentation structure and refining entry pages to correctly route readers. This process cleans up scattered, inconsistent workflows and makes durable guidance easy to follow for new team members.

When should I use a documentation structure skill for my codebase?

You should use a documentation structure skill when your project's docs are missing, duplicated, or hard to navigate. It adds new durable engineering guidance and refines writing quality to ensure entry pages accurately route readers to the correct source of truth.