# Cypress Coverage Plan Generation

> Coverage-planning skill for Cypress work. Use when Codex needs to turn confirmed requirements into a structured, risk-aware Cypress coverage plan with scenarios, execution types, priorities, and traceability.

- Skill: `jovd83/cypress-coverage-plan-generation` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add jovd83/cypress-coverage-plan-generation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jovd83/cypress-coverage-plan-generation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: jovd83 (https://skillmd.com/u/jovd83)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jovd83/cypress-coverage-plan-generation

---


## 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)

# Functional Coverage Plan Generation

Use this skill after the requirements are clear enough to plan against.

## 1. Prerequisite

- Start from confirmed requirements or a clearly labeled analysis baseline.
- If major assumptions remain, keep them visible in the plan instead of burying them.

## 2. Generate the Scenarios

- Aim for meaningful functional completeness, not mechanical scenario inflation.
- Cover the paths that change confidence: core success paths, important variations, failure handling, boundary conditions, permissions, and role differences when relevant.
- Avoid duplicate scenarios that test the same risk with different wording.
- Choose the lowest-cost execution type that still validates the behavior well.

Recommended scenario classes:

1. Happy paths
2. Important variations
3. Negative and error handling
4. Boundary and resilience behavior

## 3. Formatting the Plan

Produce a coverage plan table like this:

| Priority | Requirement ID | Scenario | Coverage Type | Execution Type | Risk Covered | Notes |
|---|---|---|---|---|---|---|

Use `Execution Type` values such as `UI`, `API`, or `Component`.

Use `Coverage Type` values such as `happy-path`, `variation`, `negative`, `edge`, or `resilience` when helpful.

## 4. Next Step

Use dispatcher intent `review_cypress_coverage_plan` when explicit review or sign-off is needed before implementation or documentation.

If dispatcher routing is unavailable, use `cypress-coverage-plan-review`.