docs-manager

Manage project documentation and standards in the .maister/docs/ repository.

199|26|Updated Nov 27, 2025
One-click install
npx skills add https://github.com/SkillPanel/maister --skill docs-manager-skillpanel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-manager
Source: https://github.com/SkillPanel/maister/tree/main/plugins/maister-copilot/skills/docs-manager
Command: npx skills add https://github.com/SkillPanel/maister --skill docs-manager-skillpanel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This internal engine manages project documentation and technical standards within the .maister/docs/ directory. It handles operations like INDEX.md generation and integration with .github/copilot-instructions.md, and is invoked by maister-init, standards-update, and standards-discover skills.

Core Features & Use Cases

  • INDEX.md generation and maintenance: keeps the master documentation map up to date.
  • Documentation integration: ensures .github/copilot-instructions.md references current docs for AI-assisted workflows.
  • Internal orchestration: coordinates documentation structure and loading during project setup and standards discovery.

Quick Start

Follow the engine's prompts to refresh documentation state and align tooling with the latest standards and INDEX map.

Frequently Asked Questions about docs-manager

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

FAQPage Schema
How do I automate project documentation and keep the master INDEX.md up to date?

Project documentation automation works by coordinating the .maister/docs/ directory structure, refreshing the INDEX.md master map, and enforcing layout standards so your documentation stays organized and current.

What is the best way to integrate AI tooling with project documentation standards?

The best way is to link .github/copilot-instructions.md directly to your current documentation structure, ensuring AI-assisted workflows automatically reference accurate standards and INDEX maps.

How does documentation structure enforcement work during project initialization?

Documentation structure enforcement works by applying standardized layout rules across initialization workflows, coordinating the .maister/docs/ directory setup and INDEX.md generation to establish consistent project standards from the start.

Can I use this documentation automation approach with existing project documentation?

Yes, you can use this approach with existing documentation through the discovery workflow, which scans your current layout, refreshes the INDEX.md master map, and aligns standards without requiring a full rebuild.

When should I not use automated documentation index generation?

You should avoid automated documentation index generation when your project does not use the .maister/docs/ directory structure or .github/copilot-instructions.md integration, as the engine relies on these specific paths to function correctly.