documentation-management

Name: documentation-management
Availability: InStock
Author: impropersubset

Enforce documentation governance rules for Markdown files and project structures.

1|Updated Jan 4, 2026

Search Tags:#architecture #documentation #skills #governance #ADR #guidelines #link-test

Ready to run

npx skills add https://github.com/ImproperSubset/hh-agentics --skill documentation-management-impropersubset

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: documentation-management
Source: https://github.com/ImproperSubset/hh-agentics/tree/main/cc-governance/skills/documentation-management
Command: npx skills add https://github.com/ImproperSubset/hh-agentics --skill documentation-management-impropersubset

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill encodes documentation governance rules to reduce clutter and ensure consistency across project docs.

Core Features & Use Cases

Clear policy for when to create, archive, delete, or extract patterns into skills.
Naming conventions and recommended structure for guides, ADRs, architecture docs, and skills.
Decision-tree prompts to help teams decide where documentation belongs and how it should be organized.

Quick Start

When starting a new document, determine its type (guide, architecture doc, ADR, or skill) and place it in the appropriate location.
Use the examples in the policy to decide whether to archive or open a new skill, and extract repeating patterns into a Skill.

Frequently Asked Questions about documentation-management

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

FAQPage Schema

How do I organize project documentation to reduce clutter and ensure consistency?▼

To organize project documentation effectively, you should apply documentation governance rules that enforce naming conventions, a standard docs/ structure, and specific templates for guides, architecture docs, ADRs, and skills.

When should I archive, delete, or extract repeating documentation patterns into skills?▼

You should archive, delete, or extract repeating documentation patterns into skills by using decision-tree prompts that help evaluate document type, usage frequency, and long-term value to determine the correct governance action.

What is the recommended directory structure for maintaining architecture docs and ADRs?▼

The recommended directory structure for architecture docs and ADRs uses a standardized docs/ layout with defined locations for guides, architecture documentation, Architecture Decision Records, and skills to maintain consistency.

How do I create templates for guides, architecture docs, and ADRs?▼

You create templates for guides, architecture docs, and ADRs by applying governance rules that define naming conventions and structural patterns, ensuring every new Markdown file follows consistent formatting and location standards.

Does documentation governance work for auditing existing Markdown files?▼

Documentation governance works for auditing existing Markdown files by applying decision-tree prompts and structural policies to evaluate whether current docs should be kept, archived, deleted, or extracted into skills.

What's the best way to decide where new documentation belongs in a project?▼

The best way to decide where new documentation belongs is to identify its type as a guide, architecture doc, ADR, or skill, then place it in the appropriate location based on governance rules and naming conventions.