Bdd
End-to-end Playwright skill pack for planning, authoring, debugging, documenting, and operationalizing test automation.
npx -y skills add jovd83/playwright-skill --skill bddAssembled 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
Legacy Playwright-specific alias for BDD case formatting. Prefer the standalone `test-artifact-export-skill` skill for Gherkin, BDD, and export-ready case rendering, and use this only when Playwright-local conventions must be preserved explicitly.
SKILL.md
1.8 KB, as published. Nobody here has run it
Playwright BDD Documentation
Use this skill when the user wants executable-style behavioral documentation in Gherkin form.
Output Contract
Produce a .feature-style artifact with:
Feature- optional
Background ScenarioorScenario OutlineExampleswhen data-driven coverage adds value- requirement or suite tags when traceability matters
Writing Rules
- Write behaviors, not UI implementation trivia.
- Keep steps declarative and reusable where possible.
- Use
Scenario Outlineonly when the variation is genuinely the same behavior with different data. - Add negative or resilience scenarios when the requirement carries real risk beyond the happy path.
Scope
- Stop at documentation unless the user also asked for step definitions or Playwright implementation.
- If the source requirements are incomplete, record assumptions in comments or a short note outside the Gherkin body.