operations-manual-creator

Create structured operations manuals with STEP procedures and ANSI Z535 notes.

5|4|Updated Nov 9, 2025
One-click install
npx skills add https://github.com/takusaotome/claude-skills-library --skill operations-manual-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: operations-manual-creator
Source: https://github.com/takusaotome/claude-skills-library/tree/main/skills/operations-manual-creator
Command: npx skills add https://github.com/takusaotome/claude-skills-library --skill operations-manual-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Create clear, consistent operations manuals and SOPs that users can follow safely, including structured STEP procedures, standardized caution/warning notes, and troubleshooting guidance.

Core Features & Use Cases

  • STEP-based procedure writing: Produces detailed, unambiguous steps using Specific/Target/Expected/Proceed format.
  • Safety note classification (ANSI Z535-inspired): Adds DANGER/WARNING/CAUTION/NOTE callouts before the relevant steps with clear consequences.
  • Troubleshooting & escalation: Builds symptom–cause–resolution tables, decision trees, and an L1→L2→L3 escalation path.
  • Bilingual output (JA/EN): Assembles complete manuals in Japanese and English from reusable templates, including screenshot placeholders.

Quick Start

Ask Claude to draft an operations manual for your system by providing the target system name, operations to cover, and the intended audience skill level (beginner, intermediate, or advanced).

Frequently Asked Questions about operations-manual-creator

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

FAQPage Schema
How do I write an operations manual with standardized safety notes and troubleshooting tables?

To write an operations manual with standardized safety notes, use STEP-based procedure writing and ANSI Z535-inspired caution/warning classifications. This generates structured SOPs with symptom–cause–resolution tables and clear escalation workflows for safe system operations.

What is the STEP format for writing standard operating procedures?

The STEP format for standard operating procedures structures each instruction using Specific, Target, Expected, and Proceed components. This ensures detailed, unambiguous steps that users can follow safely while maintaining consistency across all documented business system operations.

Can I generate bilingual Japanese and English SOPs with screenshot placeholders?

Yes, you can generate bilingual Japanese and English SOPs with screenshot placeholders. The system assembles complete manuals in both languages from reusable templates, producing full operations manuals or procedure subsets tailored to the intended audience skill level.

How do I create a troubleshooting guide with L1 to L3 escalation paths?

Create a troubleshooting guide with escalation paths by building symptom–cause–resolution tables and decision trees. The system maps dependencies and generates an L1→L2→L3 escalation workflow, ensuring clear resolution procedures for each documented operational issue.

What is the best way to document business system operations for beginners versus advanced users?

Documenting business system operations for beginners versus advanced users requires specifying the intended audience skill level before drafting. The system then adjusts the STEP procedure detail and safety note classification depth to match the target reader's technical proficiency.

When should I use DANGER, WARNING, CAUTION, and NOTE callouts in an SOP?

Use DANGER, WARNING, CAUTION, and NOTE callouts in an SOP based on ANSI Z535-inspired severity classification. The system inserts these safety notes before relevant steps with clear consequences, ensuring operators understand critical hazards and precautionary information during procedures.