'runbook' 검색 결과

Generate an operational runbook template from a service name. Provide sections for starting, stopping, health checks, incident handling, maintenance, and rollback, so teams can add service-specific commands and build consistent operating procedures.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating an initial runbook for a new service
• Standardizing incident procedures across teams
• Preparing documentation for on-call onboarding

Write an ETL operational runbook. Use when the user says "ETL runbook", "pipeline runbook", "data job runbook", "how to operate this ETL", "on-call guide for data pipelines", "what to do when the data job fails", "pipeline troubleshooting guide", "data ops runbook", or needs to document how to operate, monitor, and recover a data pipeline or ETL job - even if they don't explicitly say "runbook".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create incident response runbooks with ordered recovery steps, severity levels, escalation contacts, and status update templates. Help on-call engineers follow clear procedures during outages, verify recovery, and keep stakeholders informed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing a payment service outage runbook
• Documenting database incident recovery
• Preparing guides for new on-call engineers

Create and review company procedures and operational guides, then audit internal wikis for outdated pages, missing owners, broken connections, and inconsistent terminology. Produce structured drafts, step checks, and a prioritized list of documents to improve.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Drafting procedures for employee onboarding
• Checking operational guides before use
• Prioritizing outdated wiki pages for revision

Write an operational runbook. Use when the user says "write a runbook", "on-call documentation", "how to operate this service", "alert runbook", "troubleshooting guide for ops", "what to do when this alert fires", "operational procedures", or needs to document how to run, troubleshoot, or respond to a service - even if they don't explicitly say "runbook".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turns an engineer's notes, a ticket history or a chat thread into a draft step-by-step runbook with preconditions, stop conditions, numbered steps with checks, verification, rollback and escalation, for the team to validate before use. Commands verbatim, placeholders marked, every gap UNKNOWN; never executes a step or fills a gap from general knowledge. Use when the user asks to "write a runbook from these notes", "turn this resolved ticket into a runbook", "document the steps we ran" or "check this runbook for gaps". Do not use for a business process without commands, use sop-drafter instead; for a knowledge article or known-error record, use knowledge-article-drafter; for the post-incident review, use incident-postmortem-drafter. Drafts for human review; never approves, authorises or signs off.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create a one-page service operations guide in HTML. It organizes service details, alerts and first responses, dashboard links, procedures with copyable commands, an on-call schedule, and an incident checklist so teams can find operational instructions together.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating an operations guide for a service
• Documenting first responses to alerts
• Organizing deployment and rollback procedures

Run isolated E2E tests in devcontainer from ai_docs/tests runbooks. Use this skill whenever the user asks to: run an E2E test, execute a test runbook, validate a feature end-to-end, create a new runbook, or test CLI behavior in isolation. If you need to run a multi-step CLI validation sequence (init → install → sync → verify), this is the skill — it handles ssenv isolation, flag verification, and structured reporting. Prefer this over ad-hoc docker exec sequences for any test that follows a runbook or needs reproducible isolation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan and execute a launch runbook covering pre-launch verification, go-live procedures, DNS cutover, post-launch monitoring, and rollback procedures. Use this skill whenever the user is preparing to launch a website or product, planning a DNS cutover, building a go-live checklist, or executing a launch day. Triggers on launch runbook, go-live, launch day, DNS cutover, deploy to production, site launch, product launch, cutover plan, launch checklist, deployment procedure. Also triggers when a launch is approaching and the team needs structured coordination, even if 'runbook' is not explicitly stated.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create or update a runbook for an operational scenario — an incident an alert fires for, a recurring scheduled task, or a known failure mode on a live service — using a consistent template. Use when writing, drafting, authoring, or updating a runbook for an alert, incident, on-call procedure, scheduled maintenance, or operational SOP. Applies a YAGNI preflight requiring the scenario to be real before producing the runbook. Does not produce feature or system documentation — use project-documentation. Does not record architectural decisions — use architectural-decision-record. Does not create coding standards — use coding-standard.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when authoring, reviewing, or maintaining Salesforce DevOps operational documents — runbooks, environment matrices, deployment guides, and post-deploy validation checklists. Triggers: 'runbook', 'environment matrix', 'deployment guide', 'pre-deploy checklist', 'post-deploy validation', 'how do I document a deployment', 'rollback procedure template'. NOT for what actually belongs on the pre-deploy gate — use devops/pre-deployment-checklist. NOT for release calendar, versioning, or go/no-go governance — use devops/release-management. Also covers: the devops-process YAML artefact (environment ladder, change-request state machine, deploy contract, deploy order, RACI), the deployOptions the runbook must record (checkOnly, testLevel, rollbackOnError, ignoreWarnings, purgeOnDelete, singlePackage, runTests), destructiveChangesPre/Post ordering, and the change-request emergency path.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create or update step-by-step instructions for recurring operational tasks. Document exact commands, expected results, failure responses, verification checks, rollback steps, and escalation contacts so operations teams have a concrete procedure to follow.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Documenting recurring operational tasks
• Turning experienced staff knowledge into written procedures
• Adding troubleshooting and rollback steps to existing instructions

Build a single-page operations guide for engineers on call, the people assigned to respond to service issues. Organize service dependencies, alert thresholds, dashboard links, copyable commands, duty rotations, and an incident response checklist.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Bring service operations information onto one page
• Document alert severity, thresholds, and procedure links
• Prepare commands and checklists for incident response

Use when the user asks to "run my launch day", "build a launch day runbook / war room", or "decide CONTINUE or ROLLBACK after the push"; produces a pre-conditions gate check (launch-readiness-auditor SHIP verdict + the authoritative date in launch-registry — missing either stops the skill), a dated hour-blocked runbook with owners (morning irreversible pushes, daytime monitoring loop, evening consolidation), a forced observation-window verdict after every irreversible action against pre-declared kill criteria, a P0-P3 incident ladder with rollback playbooks, and T-0 status lines for the registry proposal protocol. Not for channel submission content and platform rules — use community-launch-runner; not for media replies — use press-media-relations. 发布日runbook/作战室/观察窗/回滚裁决/发布日指挥

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to incidents, or establishing incident response procedures.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create runbooks, playbooks, and technical documentation for engineering teams. Use when the user wants to document a process, create a runbook, build operational docs, or formalize any repeatable technical procedure. Triggers on requests like "create a runbook for...", "document this process", "write a playbook", or any technical documentation request.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when an EntitySet exposes list_skills, a user requests a UModel or RunbookSet Skill, or an entity task supplies SKILL.md. Triggers: list_skills, list_knowledge, RunbookSet Skill, UModel Skill, execute skill, run skill, 执行技能, 运行技能, Runbook 技能.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates comprehensive operational runbooks for any system or process. Reads codebase, infrastructure config, and deployment scripts to produce structured runbook.md files formatted for on-call engineers. Use when you need operations documentation, incident response guides, deployment procedures, or disaster recovery plans.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create or audit SLOs, SLIs, alert rules, incident response steps, escalation paths, postmortems, operational runbooks, and customer-impact communication. Use when defining production reliability, preparing launch readiness, responding to an outage, writing a runbook, tuning alerts, or closing the loop after an incident.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create operational playbooks for incident response, deployments, and maintenance during PRD v0.8 Deployment & Ops. Triggers on requests to create runbooks, document procedures, or when user asks "how do we handle incidents?", "runbook", "operational procedures", "on-call guide", "incident response", "maintenance procedures". Outputs RUN- entries with step-by-step operational procedures.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guidance for generating OpenStack runbooks with dual task/symptom indexing following NASA procedure standards. Use when creating incident response procedures, operational runbooks, or troubleshooting guides that must be verified against running infrastructure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

On-call 轮值和 Runbook 维护时使用。适用于值班制度设计、操作手册编写、升级路径定义。融合 PagerDuty On-call + Atlassian Runbook。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to incidents, or establishing incident response procedures.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to "run my launch day", "build a launch day runbook / war room", or "decide CONTINUE or ROLLBACK after the push"; produces a pre-conditions gate check (launch-readiness-auditor SHIP verdict + the authoritative date in launch-registry — missing either stops the skill), a dated hour-blocked runbook with owners (morning irreversible pushes, daytime monitoring loop, evening consolidation), a forced observation-window verdict after every irreversible action against pre-declared kill criteria, a P0-P3 incident ladder with rollback playbooks, and T-0 status lines for the registry proposal protocol. Not for channel submission content and platform rules — use community-launch-runner; not for media replies — use press-media-relations. 发布日runbook/作战室/观察窗/回滚裁决/发布日指挥

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.