Enforce YAML frontmatter and structured sections for project documents.
npx skills add https://github.com/doancan/mags --skill doc-management
Please help me install this Agent Skill. Skill: doc-management Source: https://github.com/doancan/mags/tree/main/skills/doc-management Command: npx skills add https://github.com/doancan/mags --skill doc-management
Document teams often struggle to keep consistent formatting, lifecycle management, and discoverability across project docs. This skill enforces standardized frontmatter, structured sections, and cross-referencing to reduce drift and confusion.
Create your first document in your docs/ folder following the frontmatter and heading structure and update the created/updated fields accordingly.
High-intent search queries and answers about installing and using this skill.
Enforce consistent frontmatter by applying standardized YAML rules with required fields like title, description, status, created, updated, author, and tags. This ensures uniform metadata across all project docs, reducing drift and confusion among team members.
Manage document lifecycle states by using DRAFT, REVIEW, and LOCKED statuses within your markdown frontmatter. This governance approach prevents unapproved changes to technical guides, reference docs, and ADRs until they pass formal review.
Structure markdown headings by prescribing a strict H1/H2/H3 layout for ADRs, reference docs, and guides. This section structure guidance improves readability and navigation across software project documentation, ensuring cross-references remain logically organized.
No specific dependencies are required to standardize markdown formatting. The governance rules apply natively to your docs/ folder by enforcing YAML frontmatter standards and structured sections without external components or libraries.
Yes, you can apply document lifecycle governance to changelogs, writing guides, reference docs, and ADRs within software projects. The standardized frontmatter and lifecycle statuses ensure consistent formatting and discoverability across all project documentation types.
Inconsistent frontmatter causes documentation drift because missing or varied metadata fields prevent automated tracking and cross-referencing. Enforcing required YAML fields like status, updated, and author standardizes discoverability and formatting across teams.
fabioc-alohaConvert .docx files to Markdown with image extraction and pandoc cleanup.
copilot-ldRender Markdown documentation into static HTML sites with Mustache templates.
lbliiiMigrates static site and Markdown content to Bengal format.
SethGammonMaintain a markdown knowledge base with interlinked topics and an index.
