create-doc

Create project documentation files with standardized YAML frontmatter and duplicate detection.

41|7|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/DGouron/review-flow --skill create-doc-dgouron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-doc
Source: https://github.com/DGouron/review-flow/tree/main/.claude/skills/create-doc
Command: npx skills add https://github.com/DGouron/review-flow --skill create-doc-dgouron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create documentation that adheres to project standards while preventing duplicates, reducing manual drafting time and confusion from overlapping content.

Core Features & Use Cases

  • Automates the creation of new documentation files that follow project standards.
  • Detects overlap with existing docs before creating new ones.
  • Supports documenting features, concepts, or components with a consistent structure.

Use Case: When documenting a new feature in a codebase, the skill will add a skeleton doc and link it to related files.

Quick Start

Create a documentation file by specifying the subject and audience; the skill will detect duplicates and generate a standardized doc skeleton.

Frequently Asked Questions about create-doc

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

FAQPage Schema
How do I create markdown documentation that follows project standards?▼

To create markdown documentation that follows project standards, use the /create-doc command to generate a skeleton file with standardized YAML frontmatter, including title, scope, related, and last-updated fields.

How do I prevent duplicate documentation when adding new files?▼

Preventing duplicate documentation is handled by built-in overlap detection, which scans existing docs before creating a new file to ensure the subject is not already covered and reduce confusion from overlapping content.

What is the best way to document a new feature without manual formatting?▼

The best way to document a new feature without manual formatting is to automate the process by specifying the subject and audience, which generates a standardized doc skeleton linked to related files.

Do I need YAML frontmatter in my documentation files?▼

Yes, YAML frontmatter is required in your documentation files. The creation process enforces a standardized frontmatter block containing title, scope, related, and last-updated fields to maintain project documentation standards.

Can I use this for documenting both concepts and components?▼

Yes, you can use this for documenting both concepts and components. It supports documenting features, concepts, or components by generating a consistent structure and applying the project's naming conventions to the new file.

Why does my documentation overlap with existing project files?▼

Documentation overlap with existing project files occurs when multiple docs cover the same subject. Using an automated overlap detection check before creation prevents this by identifying duplicate coverage early.