Cypress Reporting Stakeholder

Stakeholder-reporting skill for Cypress execution results. Use when Codex needs to turn raw Cypress runs into a concise, non-technical summary of tested scope, release health, business impact, and recommended next actions.

jovd83 Updated

File contents

Telemetry & Logging

[!IMPORTANT] All usage of this skill must be logged via the Skill Dispatcher to ensure audit logs and wallboard analytics are accurate: ./log-dispatch.cmd --skill <skill_name> --intent <intent> --model <model_name> --reason <reason> (or ./log-dispatch.sh on Linux)

Stakeholder Execution Report

Use this skill when the audience is a product manager, QA lead, delivery lead, or another stakeholder who does not want raw runner noise.

Action

Produce a report with:

  • Executive summary
  • Scope covered
  • Overall outcome
  • Known issues and business impact
  • Recommended next actions

Writing rules:

  • Translate technical failures into business language.
  • Call out confidence limits if the run was partial, flaky, blocked, or environment-constrained.
  • Keep stack traces and low-level logs out of the main report unless the user explicitly wants them.

jovd83/Cypress-skill/tree/main/reporting/stakeholder commit 9ba1f8c198

Frequently asked questions

npx skillmds@latest add jovd83/cypress-reporting-stakeholder