cgs.qa.e2e

Generate Playwright E2E test suites from speckit specification artifacts.

1|3|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/CodeGeneration-2020/cgs-team-claude-setup --skill cgs-qa-e2e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cgs.qa.e2e
Source: https://github.com/CodeGeneration-2020/cgs-team-claude-setup/tree/main/.claude/skills/cgs.qa.e2e
Command: npx skills add https://github.com/CodeGeneration-2020/cgs-team-claude-setup --skill cgs-qa-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of end-to-end (E2E) tests for web applications directly from specification documents, significantly reducing manual testing effort and ensuring comprehensive test coverage.

Core Features & Use Cases

  • Automated Test Generation: Converts user stories and acceptance criteria from spec.md files into executable Playwright tests.
  • Test Coverage Enhancement: Scaffolds tests for explicit scenarios, edge cases, and validation requirements.
  • Use Case: After a feature is specified using speckit.specify, this Skill can generate the corresponding E2E Playwright tests, allowing QA engineers to focus on test plan refinement and complex scenarios rather than boilerplate code.

Quick Start

Use the cgs.qa.e2e skill to generate E2E tests for the current feature's specification.

Frequently Asked Questions about cgs.qa.e2e

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate Playwright E2E tests from a specification document?

Playwright E2E tests are generated by parsing user stories and acceptance scenarios from spec.md files into executable test suites. The Skill converts specification artifacts into Playwright test files covering explicit scenarios and edge cases.

Can I generate E2E tests from speckit spec.md and plan.md files?

E2E tests can be generated from speckit artifacts including spec.md, plan.md, and tasks.md files. The tool parses user stories, acceptance scenarios, and edge cases from these files to create executable Playwright test suites.

How do I filter generated E2E tests by user story ID?

Filtering generated E2E tests by story ID is supported during the test generation process. This allows targeting specific user stories from the specification artifacts to create focused Playwright test files.

What is the best way to automate E2E test generation for web applications?

Automating E2E test generation is best handled by converting specification documents directly into executable Playwright tests. This approach scaffolds tests for explicit scenarios, edge cases, and validation requirements, reducing manual boilerplate effort.

Does this E2E test generator work with existing Playwright infrastructure?

The generated E2E tests adhere to project-specific Playwright best practices and infrastructure. Existing tests can also be updated, ensuring the generated test files integrate with the current project setup.

When do I need to regenerate E2E tests from updated acceptance criteria?

E2E tests need regeneration when acceptance scenarios or edge cases in spec.md files change. The Skill can update existing tests to reflect the modified specification artifacts, ensuring test coverage stays aligned with current requirements.