observability-driven-test-planner
Purpose
Plan non-functional testing so logs, metrics, traces, dashboards, and alerts produce useful evidence during execution.
Trigger this skill when
- You need this specific non-functional planning or review task rather than a broad testing request.
- You want explicit artifacts, thresholds, and evidence expectations.
- You need an output another agent or developer can execute or extend safely.
Expected inputs
- system telemetry context
- test goals
- available instrumentation
- diagnostic gaps
Deliverables
- observability plan
- telemetry checklist
- evidence queries
- instrumentation gaps
Operating procedure
- Clarify the target non-functional concern, the system boundary, and what would count as evidence.
- Translate vague goals into measurable metrics, thresholds, and observation points.
- Make assumptions, environmental constraints, and known blind spots explicit.
- Produce a compact artifact that can drive test execution or quality review.
Quality gates
- Prefer realistic workloads and failure modes over synthetic but meaningless coverage.
- Tie every scenario to an observable outcome and measurement method.
- State thresholds, assumptions, and residual risks explicitly.
- Do not hide missing telemetry or environment limitations.
Handoff targets
- performance-test-planner
- resilience-test-planner
- nfr-evidence-matrix-builder
Output style
- Be explicit about uncertainty, infeasibility, and residual risk.
- Prefer compact, explainable artifacts over bloated plans.
- Make pass/fail logic and evidence expectations obvious.
- Keep scenarios tied to user impact, system behavior, or operational risk.
Failure modes to avoid
- Do not produce non-functional plans with no measurable thresholds.
- Do not assume production-like behavior without naming environment gaps.
- Do not bury required telemetry, instrumentation, or recovery assumptions.
Minimum output skeleton
## Summary
## Findings
## Structured outputs
## Metrics / thresholds
## Assumptions
## Open questions
## Recommended next skill
1---2name: observability-driven-test-planner3description: observability-driven-test-planner4---5# observability-driven-test-planner67## Purpose8Plan non-functional testing so logs, metrics, traces, dashboards, and alerts produce useful evidence during execution.910## Trigger this skill when11- You need this specific non-functional planning or review task rather than a broad testing request.12- You want explicit artifacts, thresholds, and evidence expectations.13- You need an output another agent or developer can execute or extend safely.1415## Expected inputs16- system telemetry context17- test goals18- available instrumentation19- diagnostic gaps2021## Deliverables22- observability plan23- telemetry checklist24- evidence queries25- instrumentation gaps2627## Operating procedure281. Clarify the target non-functional concern, the system boundary, and what would count as evidence.292. Translate vague goals into measurable metrics, thresholds, and observation points.303. Make assumptions, environmental constraints, and known blind spots explicit.314. Produce a compact artifact that can drive test execution or quality review.3233## Quality gates34- Prefer realistic workloads and failure modes over synthetic but meaningless coverage.35- Tie every scenario to an observable outcome and measurement method.36- State thresholds, assumptions, and residual risks explicitly.37- Do not hide missing telemetry or environment limitations.3839## Handoff targets40- performance-test-planner41- resilience-test-planner42- nfr-evidence-matrix-builder4344## Output style45- Be explicit about uncertainty, infeasibility, and residual risk.46- Prefer compact, explainable artifacts over bloated plans.47- Make pass/fail logic and evidence expectations obvious.48- Keep scenarios tied to user impact, system behavior, or operational risk.4950## Failure modes to avoid51- Do not produce non-functional plans with no measurable thresholds.52- Do not assume production-like behavior without naming environment gaps.53- Do not bury required telemetry, instrumentation, or recovery assumptions.5455## Minimum output skeleton56```md57## Summary58## Findings59## Structured outputs60## Metrics / thresholds61## Assumptions62## Open questions63## Recommended next skill64```