一键在 Manus 中运行任何 Skill

operations

星标3

分支0

更新时间2026年6月19日 12:37

Start here to run software in production after it ships — observability, incident response, and operational continuity. Use to monitor a live service, handle an incident, write a runbook, or close the loop from production back to the backlog.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

douglance

douglance/sdlc-plugin

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

What to run

Observability — logs, metrics, and traces, with SLOs that define "healthy" and alerts that fire before users notice.
Incident management — detect, triage by impact, mitigate, resolve, and write a blameless postmortem. Every incident yields a prevention item.
Runbooks — a written procedure for each routine operation and recovery path, so response doesn't depend on one person's memory.
Continuity — backup, failover, and rollback that have actually been tested, not assumed.
Close the loop — route defects to debugging-and-error-recovery, recurring toil to maintenance, and new needs to requirements-gathering.

What to produce

An operations plan and runbooks, the monitoring and SLOs in place, incident records with postmortems, and the feedback items routed back into the lifecycle. Definitions: ../../GLOSSARY.md.

同仓库更多 Skills

同仓库

api-and-interface-design

douglance/sdlc-plugin

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

2026-06-193

debugging-and-error-recovery

douglance/sdlc-plugin

Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.

2026-06-193

deployment

douglance/sdlc-plugin

Start here to ship built-and-tested code to its target safely — release steps, rollout, smoke checks, and rollback.

2026-06-193

design

douglance/sdlc-plugin

Start here to settle how a non-trivial change will be built — interfaces, contracts, file-level structure, and trade-offs.

2026-06-193

documentation-and-adrs

douglance/sdlc-plugin

Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

2026-06-193

documentation

douglance/sdlc-plugin

Start here to document what shipped — READMEs, API docs, ADRs, and usage — once a feature lands or an interface changes.

2026-06-193

name	operations
description	Start here to run software in production after it ships — observability, incident response, and operational continuity. Use to monitor a live service, handle an incident, write a runbook, or close the loop from production back to the backlog.
context	fork
agent	sre

Keep the shipped software healthy in the real world. Stand up observability, respond to incidents, and feed what production teaches you back to maintenance and requirements.

Shipping is the start of operations, not the end of the work. Hope is not a strategy — instrument first.

What to run

Observability — logs, metrics, and traces, with SLOs that define "healthy" and alerts that fire before users notice.
Incident management — detect, triage by impact, mitigate, resolve, and write a blameless postmortem. Every incident yields a prevention item.
Runbooks — a written procedure for each routine operation and recovery path, so response doesn't depend on one person's memory.
Continuity — backup, failover, and rollback that have actually been tested, not assumed.
Close the loop — route defects to debugging-and-error-recovery, recurring toil to maintenance, and new needs to requirements-gathering.

What to produce

An operations plan and runbooks, the monitoring and SLOs in place, incident records with postmortems, and the feedback items routed back into the lifecycle. Definitions: ../../GLOSSARY.md.