docs-generator-sermas

Detect Sermas doc types and orchestrate Google Docs creation or updates from templates.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/BinPar/skills --skill docs-generator-sermas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-generator-sermas
Source: https://github.com/BinPar/skills/tree/main/docs-generator-sermas
Command: npx skills add https://github.com/BinPar/skills --skill docs-generator-sermas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Converts and maintains official Sermas Word/Google Docs templates (DPE, GEN, ACR, MAN) by automating content generation, section updates, and version tracking, ensuring consistent branding and conformance across projects.

Core Features & Use Cases

  • Detects document type (DPE / GEN / ACR / MAN) from user prompts and routes to the corresponding create or update flow.
  • Duplicates canonical templates, fills placeholders, and composes content per section with structured formatting for multi-profile manuals.
  • Bumps the Change Log, preserves governance around deliverables, and returns the final Google Docs URLs for review.

Quick Start

Provide a prompt like generate a Sermas DPE for project GES-29112 to start creating a Google Doc from the canonical templates.

Frequently Asked Questions about docs-generator-sermas

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

FAQPage Schema
How do I generate a Google Doc from a Sermas template automatically?

To generate a Google Doc from a Sermas template, the system detects your document type (DPE, GEN, ACR, MAN) from the prompt, duplicates the canonical template, fills placeholders, and composes content per section to produce a versioned file.

Can I update specific sections of an existing Sermas document without rewriting the whole file?

Yes, you can update existing Sermas documents with per-section editing. The workflow supports targeted content substitution, prompts for missing data, requires user confirmation for updates, and automatically bumps the Change Log to maintain version history.

What is the best way to create multiple Sermas documents at once?

The best way to create multiple files is using the multi-document generation feature. It orchestrates end-to-end creation from canonical templates, supports multi-profile MAN manuals, and returns the final Google Docs URLs for each generated file for review.

Does Google Docs support automated version tracking for Sermas project deliverables?

Google Docs supports automated version tracking for Sermas deliverables by enforcing a versioned Change Log within the document. The workflow duplicates canonical templates and bumps this log during updates to ensure consistent governance across projects.

What happens if I provide a prompt with missing data for a Sermas document generation?

When your prompt has missing data for Sermas document generation, the system ensures safety by pausing the workflow and prompting you for the necessary information before proceeding with placeholder substitution and file creation.

How does the system know which Sermas document type to create from my prompt?

The system detects the Sermas document type, such as DPE, GEN, ACR, or MAN, directly from your natural language prompt, then automatically routes the request to the corresponding create or update workflow in Google Docs.