# Runtime Validation

> Use when an implementation slice touched runtime, container, compose, broker, or service-startup behavior and that behavior must be proven running: real startup of affected services, real endpoint checks, broker topology inspection, producing runtime validation evidence and operational risk notes. This is the runtime_validation action of the implementation stretch — one Agent-tool dispatch with subagent_type devops-ops — proving 'it started', never accepting 'it should start'.

- Skill: `bhangeef16/runtime-validation` (Agent Skill)
- Install (CLI): `npx skillmds@latest add bhangeef16/runtime-validation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bhangeef16/runtime-validation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: BhangeeF16 (https://skillmd.com/u/bhangeef16)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/bhangeef16/runtime-validation

---


# Runtime Validation

Prove the changed runtime behavior by running it. A container that reports running has not passed this action — a real endpoint answered, a real log line observed, a real queue inspected has.

## Dispatch

One synchronous `Agent`-tool call, `subagent_type: devops-ops`.

## Required inputs

- The slice's runtime or compose changes.

## Required outputs (all mandatory)

- Runtime validation evidence — the specific checks performed (configuration validation, service startup, health/real-endpoint checks, broker inspection where messaging changed) with their observed output, not a pass/fail assertion alone.
- Operational risk notes — anything left unverified and why, stated plainly.

## Result

Report each required output produced (with its location), the result (pass / pass_with_risks / blocked / failure), and blocking questions as an explicit list (empty list stated explicitly).