sparq:generate-e2e

Generate Playwright or Cypress end-to-end test suites from Jira tickets and requirements.

27|4|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-generate-e2e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sparq:generate-e2e
Source: https://github.com/STUkh/sparq-assistant/tree/main/claude/skills/sparq-generate-e2e
Command: npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-generate-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze and convert feature or bug tickets and requirements into ready-to-run end-to-end test suites, reducing manual testing work and accelerating delivery.

Core Features & Use Cases

  • Analyze Jira-like tickets and requirements to scaffold Playwright or Cypress tests
  • Generate page objects, fixtures, and spec files aligned with project conventions
  • Support checkpoint-based approvals and optional linting to ensure reliability across repos

Quick Start

Run /sparq:generate-e2e with a Jira ID or description to generate an E2E test suite against your configured framework.

Frequently Asked Questions about sparq:generate-e2e

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

FAQPage Schema
How do I automate E2E test generation from Jira tickets?

Automating E2E test generation from Jira tickets requires analyzing ticket descriptions to scaffold framework-ready tests. This skill processes Jira-like tickets and requirements to automatically generate ready-to-run Playwright or Cypress test suites, including page objects, fixtures, and spec files aligned with project conventions.

Can I generate Playwright and Cypress tests from feature requirements?

Generating Playwright and Cypress tests from feature requirements is fully supported. The skill analyzes your requirements and bug tickets to scaffold test suites across multiple frameworks, producing framework-ready spec files, page objects, and fixtures that align with your existing project patterns.

What is checkpoint-based approval in E2E test automation?

Checkpoint-based approval in E2E test automation is a validation mechanism ensuring deterministic generation and reliability. The skill supports checkpoint-based approvals during test suite creation, allowing you to review and validate generated page objects, fixtures, and spec files before finalizing the framework-ready output.

Does automated E2E test generation work with existing project conventions?

Automated E2E test generation works with existing project conventions through repository scanning and configuration validation. The skill scans your repository to generate page objects, fixtures, and spec files that integrate with your existing test patterns, framework configurations, and software project components.

How to scaffold page objects and fixtures from bug tickets?

Scaffolding page objects and fixtures from bug tickets involves converting ticket requirements into framework-ready E2E suites. The skill analyzes Jira-like bug tickets to automatically generate spec files, page objects, and fixtures, applying deterministic generation and optional linting to ensure reliability across repositories.