# Playwright Coverage Plan Generation

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

- **Type:** Skill
- **Install:** `agentstack add skill-jovd83-playwright-skill-generation`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [jovd83](https://agentstack.voostack.com/s/jovd83)
- **Installs:** 0
- **Category:** [Web & Browser](https://agentstack.voostack.com/c/web-and-browser)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [jovd83](https://github.com/jovd83)
- **Source:** https://github.com/jovd83/playwright-skill/tree/main/coverage_plan/generation

## Install

```sh
agentstack add skill-jovd83-playwright-skill-generation
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Playwright Coverage Plan Generation

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

## Prerequisites

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

## Planning Rules

- Aim for meaningful functional completeness, not mechanical scenario inflation.
- Cover the paths that change confidence: core success paths, important variations, failure handling, boundary conditions, and permissions or 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.

## Output Contract

Produce a coverage plan table like this:

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

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

## Execution-Type Guidance

- `UI`: use for end-user behavior, visual flow, or browser-only interactions.
- `API`: use when the behavior can be validated more directly and more cheaply through service calls.
- `Component`: use for isolated UI states or highly focused component behavior.
- Mixed strategies are valid when one requirement needs more than one confidence layer.

## Scope Control

- High-value or logic-heavy features usually need more than one scenario.
- Simple static content often needs only one direct verification.
- Do not omit important unhappy paths just to keep the plan short.
- Do not add low-signal permutations just to make the plan look comprehensive.

## Next Step

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

If dispatcher routing is unavailable, use [../review/SKILL.md](../review/SKILL.md).

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [jovd83](https://github.com/jovd83)
- **Source:** [jovd83/playwright-skill](https://github.com/jovd83/playwright-skill)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-jovd83-playwright-skill-generation
- Seller: https://agentstack.voostack.com/s/jovd83
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.