Menu
Use for metrics, logs, traces, dashboards, alerting, SLI/SLO design, OpenTelemetry, Prometheus, Grafana, Loki, ELK, OpenSearch, Tempo, Jaeger, production diagnostics, and alert noise reduction.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Audit any product surface against accessibility standards: WCAG 2.2 AA for web, Apple UIKit/SwiftUI Accessibility for iOS, Android TalkBack/AccessibilityService for Android, Microsoft UIA for Windows, AT-SPI for Linux, game-specific readability and remappable-controls patterns, and voice/chat AI surfaces with appropriate alternative modes. Produces a per-criterion status, automated test suggestions, manual test scripts, screen-reader transcripts, contrast measurements, and a release-gate verdict that names the fixed and outstanding findings. Use after ux-design and before release on every surface with user interaction.
Design or review the operational harness around single-agent, multi-agent, and tool-using AI systems. Use when building agent platforms, routing layers, tool interfaces, memory systems, evaluation harnesses, human checkpoints, permission boundaries, cost controls, or agent-computer interfaces that must remain observable, testable, and safe under real project work.
Run an AI-augmented Product Development Lifecycle that treats every phase as a hypothesis to test, not a deliverable to push: research, hypothesis, plan-by-phases, prototype, validate, implement under TDD, harden against the matching security track (OWASP/MASVS) and CVE risk, and ship with rollback and post-launch evaluation. Use as the strategic spine when a project is greenfield, a brownfield refactor, an experiment, or a feature whose value is not yet proven; cooperates with sdlc-orchestrator (operational chain) and hypothesis-validator (evidence).
Analyze an existing repository in read-only mode to reconstruct current behavior, architecture, dependency clusters, build and test health, hotspots, tech debt, ownership boundaries, integration points, and current-vs-target gaps. Use for existing-product improvement, migration planning, code archaeology, risky refactors, unfamiliar repositories, or artifacts `80-current-state-scan.md` through `85-migration-plan.md` before writing code.
Design or review software architecture using system context, container, component, runtime, deployment, data, API, integration, crosscutting concepts, and ADR artifacts. Use before large implementation, service-boundary changes, infrastructure changes, API or data contract changes, migrations, reliability work, security-sensitive design, or architecture artifacts `14-system-context.md` through `22-adr-index.md`.
Use for CI/CD, pipeline automation, GitHub Actions, GitLab CI, Jenkins, Argo, Azure DevOps, build-test-scan-package-deploy flows, release orchestration, protected environments, approvals, and rollback.
| name | observability-operations |
| description | Use for metrics, logs, traces, dashboards, alerting, SLI/SLO design, OpenTelemetry, Prometheus, Grafana, Loki, ELK, OpenSearch, Tempo, Jaeger, production diagnostics, and alert noise reduction. |
You make systems diagnosable. Your work should help engineers answer what is broken, who is affected, why it happened, and what action is safe next.
references/workflow.md.../../routing/principal-operating-model.md before moving from analysis to implementation.Provide signal goals, documentation validation status, instrumentation/config changes, dashboard and alert behavior, validation steps, privacy/cost risks, and assumptions.
For incidents, pair with incident-troubleshooting. For Kubernetes monitoring, pair with kubernetes-operations. For CI/deploy telemetry, pair with cicd-automation.
references/workflow.md for observability design and validation checklist.