documentation

Generate documentation from approved templates with YAML frontmatter and separation of concerns.

Updated Aug 23, 2026

Search Tags:#templates #documentation #markdown #technical writing #yaml frontmatter #doc generation

Ready to run

npx skills add https://github.com/reeinharddd/impulsa-monorepo --skill documentation-reeinharddd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: documentation
Source: https://github.com/reeinharddd/impulsa-monorepo/tree/main/.github/skills/documentation
Command: npx skills add https://github.com/reeinharddd/impulsa-monorepo --skill documentation-reeinharddd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation and maintenance of project documentation, ensuring adherence to established standards for structure, metadata, and content organization.

Core Features & Use Cases

Template-driven generation: Creates documentation using predefined templates for various types (database, API, ADR, etc.).
Metadata enforcement: Ensures all required YAML frontmatter fields are present and correctly formatted.
Separation of concerns: Guides users to place content in the appropriate document type, preventing cross-contamination of concerns.
Use Case: When a new feature is developed, this Skill can be invoked to generate the necessary feature design document, API documentation, and database schema updates, all following the project's strict guidelines.

Quick Start

Use the documentation skill to create a new feature design document for the 'user-authentication' module.

Frequently Asked Questions about documentation

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

FAQPage Schema

How do I generate structured markdown documentation with YAML frontmatter?▼

Generate structured markdown documentation with YAML frontmatter by using predefined templates that enforce complete metadata fields and strict separation of concerns. This ensures proper structure and adherence to project validation rules.

What is the best way to maintain technical writing standards across project docs?▼

Maintain technical writing standards by enforcing metadata validation rules and predefined templates for database, API, and ADR docs. This prevents cross-contamination of concerns and ensures content organization compliance.

Can I use templates to create multiple types of technical documentation?▼

Yes, you can use templates to create multiple types of technical documentation including feature design, API, database schema, and ADR documents. Each type follows strict guidelines for structure and metadata.

How do I update existing feature design documents without breaking structure?▼

Update existing feature design documents by invoking the documentation generation process with MCP tools for context and search. This leverages approved templates to maintain proper structure and YAML frontmatter compliance.

Does the documentation generation process enforce separation of concerns?▼

Yes, the documentation generation process enforces separation of concerns by guiding content placement into appropriate document types. This prevents cross-contamination between feature design, API, and database schema documentation.

Why does my generated documentation fail validation rules?▼

Generated documentation fails validation rules when required YAML frontmatter fields are missing or incorrectly formatted. Ensure all metadata fields are present and content follows strict separation of concerns guidelines.