Analysis
End-to-end Playwright skill pack for planning, authoring, debugging, documenting, and operationalizing test automation.
npx -y skills add jovd83/playwright-skill --skill analysisAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Requirements-analysis skill for Playwright planning and implementation. Use when Codex needs to extract testable behaviors, acceptance criteria, risks, dependencies, or open questions from tickets, specs, markdown docs, or other requirement sources before writing tests or coverage plans.
SKILL.md
2.7 KB, as published. Nobody here has run it
Playwright Requirements Analysis
Use this skill to turn raw product or engineering artifacts into a trustworthy testing baseline.
Inputs
Use the best available sources in this order:
- user-provided tickets, specs, or links,
- repository-local docs such as
docs/, markdown files, issue exports, or feature notes, - adjacent automation or product artifacts that clarify behavior.
Do not keep searching indefinitely once you have enough evidence to form a reliable baseline.
Output Contract
Produce a concise requirements baseline with these sections:
Confirmed behaviorsInferred behaviorsRisks and edge casesOpen questions or missing evidenceSource evidence
When tabular output helps, use:
| Requirement ID | Behavior | Evidence | Confidence | Notes |
|---|
Rules
- Separate confirmed facts from reasonable inference.
- Normalize vague prose into testable behaviors.
- Capture edge cases, authorization rules, data constraints, and failure modes when the source implies them.
- Call out missing or contradictory evidence explicitly instead of hiding it inside the summary.
When to Pause
- Pause for confirmation when the requirements are ambiguous enough to change the downstream plan materially.
- If the user explicitly asked for a baseline only, stop after the analysis.
- If the requirements are clear enough and the user asked for downstream planning in the same request, continue while marking assumptions.
Handoff
Use the output of this skill as the input to dispatcher intent plan_playwright_coverage when planning is needed.
If dispatcher routing is unavailable, use ../coverage_plan/generation/SKILL.md or move directly into implementation work when the scope is already narrow.