docs-structure-maintainer

Enforce canonical documentation and TASKS structure with validation and migration scripts.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/paunchygent/docforge --skill docs-structure-maintainer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-structure-maintainer
Source: https://github.com/paunchygent/docforge/tree/main/frontend/.claude/skills/docs-structure
Command: npx skills add https://github.com/paunchygent/docforge --skill docs-structure-maintainer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps classify content under documentation and TASKS, ensuring canonical placement, naming, and frontmatter for runbooks and ADRs, and providing scripts to validate and migrate documentation layout.

Core Features & Use Cases

  • Classify and map content to documentation directories
  • Enforce naming rules (kebab-case) and required frontmatter
  • Validate and migrate with validate_docs_structure.py and migrate_docs_structure.py

Quick Start

Use the docs management scripts to validate and migrate your docs structure:

  • validate: python scripts/docs_mgmt/validate_docs_structure.py
  • migrate: python scripts/docs_mgmt/migrate_docs_structure.py

Frequently Asked Questions about docs-structure-maintainer

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

FAQPage Schema
How do I validate my HuleEdu documentation structure?

Documentation structure validation enforces canonical placement, naming conventions in kebab-case, and required frontmatter for runbooks and ADRs. Run `python scripts/docs_mgmt/validate_docs_structure.py` to check your docs/ and TASKS/ directories against HuleEdu standards and identify non-compliant files.

What naming rules apply to documentation files in HuleEdu?

HuleEdu documentation enforces kebab-case filenames and requires specific frontmatter for runbooks and ADRs. The docs-structure-maintainer Skill classifies content into canonical directories, suggests compliant filenames, and validates adherence to these structural rules.

How do I migrate existing documentation to comply with HuleEdu structure?

Documentation migration maps existing files to canonical directories and applies compliant naming and frontmatter. Use `python scripts/docs_mgmt/migrate_docs_structure.py` to automatically reorganize your documentation/ and TASKS/ content to match HuleEdu structural requirements.

Where should I place new documentation files in HuleEdu?

The docs-structure-maintainer Skill classifies and maps documentation content to the correct directories within documentation/ or TASKS/ based on file type and purpose. It enforces canonical placement rules and suggests the appropriate location before you create or move files.

Can I automate validation and migration of documentation across my project?

Yes, the docs-structure-maintainer Skill provides exact validation and migration commands via `scripts/docs_mgmt` and `scripts/task_mgmt`. These scripts automate structural enforcement across your entire documentation and TASKS directories without manual file-by-file updates.

What frontmatter is required for HuleEdu runbooks and ADRs?

The docs-structure-maintainer Skill enforces required frontmatter for runbooks and architectural decision records (ADRs) within HuleEdu. Validation and migration scripts check and apply these standards; run the validation script to see what frontmatter your files are missing.