Ops Readiness.prompt

GPTClaudeDeepSeek··▲ 194 copies·updated 2026-07-14

ops-readiness-prompt.prompt

---
description: 'Assess operational readiness across observability, runbooks, failure handling, and supportability.'
name: ops-readiness
argument-hint: '[service, component, or release scope]'
agent: tester
tools:
  - read
  - search
---
Assess operational readiness across observability, runbooks, failure handling, and supportability.

Use evidence from code, tests, docs, and runbooks.

Output exactly in this format:

## Ops Readiness Scorecard

- observability: READY | PARTIAL | MISSING
- alerting: READY | PARTIAL | MISSING
- runbooks: READY | PARTIAL | MISSING
- failure handling: READY | PARTIAL | MISSING

## Gaps

For each gap:

- area
- finding
- risk if unresolved
- owner role

## Must-Fix Before Release

- blocker
- required evidence

## Follow-up Actions

- action
- owner role
- target milestone

<!-- AUTO-GENERATED — maintained by vstack, do not edit directly -->
<!-- VSTACK-META: {"artifact_name":"ops-readiness","artifact_type":"prompt","artifact_version":"20260513009","generator":"vstack","vstack_version":"3.6.0"} -->

when to use it

Community prompt sourced from the open-source GitHub repo eschaar/vstack (MIT). A "Ops Readiness.prompt" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.