'runbook' 검색 결과

Product-launch command desk (Busabase App-in-Skill) built on the RAMP discipline — Research / Assemble / Mobilize / Prove. The agent assembles the launch checklist and drafts launch assets, channel submissions (Product Hunt / Hacker News / directories), press pitches, and the launch-day runbook; the human approves the launch-readiness gate and steers launch day in a review UI. Use when the user invokes $kelly-launch or /kelly-launch, or mentions launching / shipping a product, a launch checklist or runbook, launch readiness, RAMP, Product Hunt / Show HN / press-kit / launch-email drafting, or wants to review and approve launch assets and channel submissions before they go public. This is launch OPERATIONS — the checklist, assets, submissions, and runbook — not a launch video (for a promo video use product-launch-video).

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

Translate an approved experiment spec into a launch runbook — platform binding (PostHog primary), feature flag setup, assignment unit, exposure event definition, instrumentation QA, dashboard wiring, ramp plan, monitoring, and rollback procedure. Platform-agnostic core with one strong PostHog adapter shipped; GrowthBook, Statsig, LaunchDarkly, Optimizely, and Eppo documented as a single mapping table the user adapts. Load when a spec is approved and ready to launch, or when the user says "set up the experiment", "wire this up in PostHog", "implement the test", "create the runbook", "launch checklist for this test", or when the experimentation orchestrator routes here.

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

Creates step-by-step incident response runbooks for common outages with actions, owners, rollback procedures, and communication templates. Use for "incident runbook", "outage response", "incident management", or "on-call procedures".

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

Create reusable procedures for responding to security incidents, from detection and containment to recovery. Define decision points, responsibilities, escalation rules, and workflows for security automation platforms so teams can follow a consistent response process.

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

• Establishing an incident response program
• Documenting phishing or ransomware response procedures
• Designing automated security response workflows

Write and maintain technical documents for different readers, including READMEs, API references, operational procedures, architecture explanations, and onboarding guides. Organize practical examples, setup steps, design decisions, and recovery instructions around what each audience needs.

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

• Create a README with a quick start
• Document API requests and responses
• Write operational and rollback procedures

Plans, executes, and validates Google Kubernetes Engine upgrades for Standard and Autopilot clusters. Creates environment-specific upgrade plans, checklists, and command-based runbooks, with guidance on maintenance timing, node upgrade strategies, workload readiness, and stalled upgrades.

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

• Planning a GKE version upgrade
• Choosing release channels and maintenance schedules
• Preparing node pool upgrades for databases or GPU workloads

Define reliability targets for production services and calculate error budgets, the allowed amount of failure. Create monitoring rules, incident response runbooks, capacity plans, and automation scripts, with failure experiments to check recovery behavior.

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

• Define service reliability targets and error budget policies
• Design monitoring dashboards and actionable alerts
• Prepare incident response runbooks and postmortems

Create Dockerfiles, automated build and deployment pipelines, Kubernetes configurations, and infrastructure templates. The skill also prepares deployment checks, rollback procedures, and incident response runbooks to support application releases and production operations.

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

• Setting up automated build and deployment pipelines
• Packaging applications with Docker
• Managing Kubernetes and cloud infrastructure as code

Write and maintain technical documents for different readers, including READMEs, API references, operational procedures, architecture explanations, and onboarding guides. Organize practical examples, setup steps, design decisions, and recovery instructions around what each audience needs.

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

• Create a README with a quick start
• Document API requests and responses
• Write operational and rollback procedures

Have a fast, conversational analysis with the AWS DevOps Agent. Use for cost optimization, architecture review, topology mapping, knowledge / runbook discovery, security audits, dependency questions, and quick diagnostics — anything that needs a 5-30 second answer rather than a 5-8 minute deep investigation. Trigger words include cost, optimize, review, architecture, topology, what runbooks, show me, compare, audit, what if.

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

Incident response runbook for Apple Notes automation failures. Trigger: "apple notes incident".

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

Execute incident response procedures for Claude API outages and degradation. Use when Claude API is returning errors, experiencing high latency, or showing degraded performance in production. Trigger with phrases like "anthropic incident", "claude api down", "anthropic outage", "claude degraded", "anthropic runbook".

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

The SRE team's runbook for triaging production latency and error-rate incidents. Use this whenever investigating an incident, a latency spike, elevated error rates, or when asked "what caused X" about a production service.

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

Create operational runbooks and standard operating procedures. Document troubleshooting guides and recovery procedures. Use when documenting operational knowledge.

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

Write an operating runbook from the delivered system and verified procedures. Use when the customer team or a successor needs to operate without the original engineer.

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

Generate operational runbooks from codebase analysis covering deployment, incident response, scaling, and monitoring, with copy-paste commands and rollback steps. Use when bootstrapping ops docs, preparing for on-call, or post-incident.

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

Expert knowledge for Azure Automation development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when building runbooks, DSC configs, Hybrid Runbook Workers, managed identities, or Automation deployments, and other Azure Automation related development tasks. Not for Azure Functions (use azure-functions), Azure Logic Apps (use azure-logic-apps), Azure DevOps (use azure-devops), Azure DevTest Labs (use azure-devtest-labs).

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

Generate detailed service restoration runbooks with step-by-step procedures. Use when someone asks to "create recovery procedures", "restoration runbook", "recovery steps", "how to restore service", or needs tactical step-by-step procedures for recovering from disaster scenarios. This is the execution companion to the DR plan — DR defines what and when, recovery-plan defines exactly how. Requires a DR plan to exist (will prompt to run /pmstudio-dr first if missing).

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

Operational runbook and procedure documentation specialist. Use when creating incident response procedures, operational playbooks, or system maintenance guides.

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

Build, run, and improve a Security Operations Center — alert prioritization, runbook authoring, escalation criteria, on-call structure, alert tuning workflow, MTTD / MTTR / fidelity KPIs, analyst tiering, and shift handoffs. Use when the user mentions 'SOC,' 'security operations,' 'SOC analyst,' 'alert triage workflow,' 'runbook,' 'escalation,' 'on-call,' 'SOC tiering,' 'tier 1 / tier 2,' 'MTTD,' 'MTTR,' 'alert fatigue,' 'alert tuning,' 'shift handoff,' 'SOAR,' or wants to design or improve a security operations team.

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

Creates or updates project documentation for a feature, system, or component and publishes it to a user-specified Confluence location. Use when the user wants feature or system documentation written to Confluence, posted to a Confluence space or page, or synced to a Confluence location. Requires a configured Atlassian MCP server. Does not document to local files only — use project-documentation for that. Does not publish an arbitrary existing markdown file — use markdown-to-confluence for that. Does not plan or specify a new feature to Confluence — use plan-a-feature-to-confluence for that. Does not create architectural decision records — use architectural-decision-record. Does not create coding standards — use coding-standard. Does not produce runbooks — use runbook.

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

Creates and updates coding standards, conventions, rules, and guidelines for the current project. Use when creating new standards from scratch, converting existing documents into coding standards, or updating existing standards. Does not create architectural decision records — use architectural-decision-record for ADRs. Does not write feature or system documentation — use project-documentation for that. Does not research open-ended options — use research. Does not produce runbooks for operational scenarios — use runbook for that.

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

Creates and maintains project documentation for features, systems, and components. Use when documenting how a feature, system, or component works — including writing, updating, or organizing docs. Does not scan or detect the project's technology stack — use project-discovery for repository analysis and config detection. Does not create architectural decision records — use architectural-decision-record for ADRs. Does not create or update coding standards — use coding-standard instead. Does not generate PR descriptions — use update-pr-description for that. Does not produce runbooks for operational scenarios — use runbook for that. Does not rewrite existing prose for readability — use edit-for-readability for that. Does not produce an ephemeral, understand-now overview of code or a PR — use code-overview for that.

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

Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.

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