doc-writer

Create or update documentation by rendering type-specific templates with runtime context.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/fractary/claude-plugins --skill doc-writer-fractary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-writer
Source: https://github.com/fractary/claude-plugins/tree/main/plugins/docs/skills/doc-writer
Command: npx skills add https://github.com/fractary/claude-plugins --skill doc-writer-fractary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, jq, mustache, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Creates or updates documentation by loading type-specific context at runtime, enabling a single generic writer to manage many doc types.

Core Features & Use Cases

  • Load type context (template, schema, standards)
  • Render content with variable substitution
  • Write dual-format outputs when necessary
  • Increment version and manage frontmatter

Quick Start

Write or update a document by supplying the type and context bundle.

Frequently Asked Questions about doc-writer

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

FAQPage Schema
How do I create documentation from templates with variable substitution?

doc-writer loads type-specific templates and context at runtime, then renders documentation by substituting variables from your merged context bundle. Supply a doc_type, and it writes the output as README.md, auto-incrementing versions on updates.

Can I generate documentation in multiple formats automatically?

When your type's schema.json requires it, doc-writer generates dual-format output—both README.md and JSON—from a single context source, enforcing consistent structure across formats.

What's the best way to manage documentation for different document types?

Store type-specific templates, schemas, and standards in plugins/docs/types/{doc_type}/ directories. doc-writer loads the correct context at runtime, letting one generic writer handle many doc types without hardcoding.

Do I need to manually update version numbers when editing documentation?

No. doc-writer auto-increments versions on updates and manages frontmatter metadata automatically, ensuring your documentation stays versioned without manual intervention.

Can I use doc-writer if my doc types are stored in a custom directory structure?

doc-writer requires type context to exist at plugins/docs/types/{doc_type}/ and validates that the directory exists before rendering. You must organize your types in that structure for the Skill to function.

What happens if template variables don't match my context data?

doc-writer validates context against your template during rendering. Mismatched or missing variables will cause validation to fail, preventing incomplete documentation from being written.