OpenParable
Skip to content
← Back to skills

Docs Structure Maintainer

Documents
docs-structure-maintainer

Docs Structure Maintainer is an Agent Skill for documents published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Understand and maintain HuleEdu documentation and task documentation structure. Guides placement, naming, and validation using the canonical specs and management scripts.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/documents/docs-structure-maintainer/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/docs-structure-maintainer, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Documentation Structure Maintainer

Compact skill for reasoning about HuleEdu documentation layout and TASKS structure, and for invoking the right scripts to keep them compliant.

When to Use

Activate when the user:

  • Creates, moves, or renames documentation under documentation/ or TASKS/
  • Asks where a doc should live (operations vs decisions vs how-to vs tasks)
  • Wants to validate or migrate documentation structure
  • Mentions validate_docs_structure.py, migrate_docs_structure.py, task_mgmt, or doc/TASKS specs

Core Capabilities

  • Classify content type and map it to the correct directory:
    • documentation/overview|architecture|services|operations|how-to|reference|decisions|product|research
    • TASKS/ domain taxonomy: programs/, assessment/, content/, identity/, frontend/, infrastructure/, security/, integrations/, architecture/, archive/
  • Suggest compliant filenames and directory names (kebab-case, no spaces; id-based filenames in TASKS/)
  • Ensure required frontmatter for:
    • Runbooks and ADRs (per documentation/DOCS_STRUCTURE_SPEC.md)
    • Task and programme docs (per canonical TASKS spec)
  • Propose concrete commands for:
    • python scripts/docs_mgmt/validate_docs_structure.py [--strict]
    • python scripts/docs_mgmt/migrate_docs_structure.py ...
    • python scripts/task_mgmt/new_task.py ...
    • python scripts/task_mgmt/validate_front_matter.py ...
    • python scripts/task_mgmt/index_tasks.py ...

Quick Workflow

  1. Identify doc intent (architecture, runbook, ADR, how-to, product, task, programme).
  2. Map to the correct directory using DOCS_STRUCTURE_SPEC.md and the TASKS structure spec.
  3. Choose or normalize filename and directory name to match naming rules.
  4. Ensure or suggest correct frontmatter for the doc type.
  5. Recommend validation/migration commands using scripts/docs_mgmt and scripts/task_mgmt.

Reference Documentation

  • Detailed Workflows & Patterns: See reference.md in this directory
  • Real-World Usage Examples: See examples.md in this directory
  • Normative Rules: .claude/rules/090-documentation-standards.md