generate-claude-md

Generate a project-specific CLAUDE.md from workflow-config.yaml and a template.

6|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/navapbc/digital-service-orchestra --skill generate-claude-md-navapbc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-claude-md
Source: https://github.com/navapbc/digital-service-orchestra/tree/main/plugins/dso/skills/generate-claude-md
Command: npx skills add https://github.com/navapbc/digital-service-orchestra --skill generate-claude-md-navapbc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the generation of a CLAUDE.md file by rendering a project-specific template with values sourced from workflow-config.yaml and the Digital Service Orchestra template.

Core Features & Use Cases

  • Template-driven CLAUDE.md generation from workflow-config.yaml and the project template
  • Automatic placeholder substitution to produce a ready-to-use CLAUDE.md
  • Safe merge guidance for updating CLAUDE.md without overwriting project-specific sections

Quick Start

Run /dso:generate-claude-md in your project directory to generate CLAUDE.md using workflow-config.yaml and the template.

Frequently Asked Questions about generate-claude-md

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

FAQPage Schema
How do I auto-generate a CLAUDE.md file from project config?

To auto-generate a CLAUDE.md file, the Skill renders a project-specific template by substituting values from workflow-config.yaml. It loads the config, loads the template, and replaces placeholders to produce a ready-to-use CLAUDE.md.

Can I update CLAUDE.md without overwriting my project-specific sections?

Yes, you can update CLAUDE.md without losing custom content using safe merge guidance. The Skill enforces rules to safely merge newly generated template sections into an existing CLAUDE.md file without overwriting project-specific additions.

What is template-driven CLAUDE.md generation used for?

Template-driven CLAUDE.md generation is used to standardize automation and documentation across multiple repositories. It ensures consistent workflow configuration by automatically substituting project-specific values into a standardized template.

Do I need a workflow-config.yaml file to generate a CLAUDE.md template?

Yes, a workflow-config.yaml file is required to generate a CLAUDE.md template. The Skill sources placeholder values from this configuration file to render the project-specific Digital Service Orchestra template.

What's the best way to standardize Claude Code workflow documentation across repositories?

The best way to standardize Claude Code workflow documentation is by using a template-driven generation approach. This Skill renders a shared template with workflow-config.yaml values to enforce consistent documentation and automation standards.

Why does my CLAUDE.md generation fail to substitute config placeholders?

CLAUDE.md generation fails to substitute placeholders when the workflow-config.yaml file is missing or misconfigured. The Skill requires valid config data to load and render the template properly before merging the output.