skills.rest
STUkh
STUkhCOMMUNITY
Explore all skills by this author →
GitHub

sparq:generate

Generate manual and automated E2E tests from Jira feature requirements.

27|4|Updated Feb 27, 2026
Search Tags:#automation#e2e#qa#test-generation#generate#requirements-analysis#manual-tests
One-click install
npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-generate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sparq:generate
Source: https://github.com/STUkh/sparq-assistant/tree/main/claude/skills/sparq-generate
Command: npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-generate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate both manual test cases and end-to-end automated tests from requirements, unifying QA planning and execution in a single pipeline to save time and improve coverage.

Core Features & Use Cases

  • Batch analysis with per-ticket workflows to plan complete test coverage.
  • Simultaneous generation of manual tests and E2E automation with consolidated checkpoints.
  • Outputs include manual test cases, E2E specs, page objects, fixtures, and coverage metadata.

Quick Start

Run /sparq:generate EP-142 to create a complete manual and E2E test suite for a feature.

Frequently Asked Questions about sparq:generate

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

FAQPage Schema
How do I generate manual test cases and E2E automation code from feature requirements?▼

Automated test generation from feature requirements is done by running the sparq:generate command with a ticket ID like EP-142, which produces manual test cases, E2E specs, page objects, and fixtures in a single pass.

Can I batch analyze Jira tickets to plan complete test coverage for multiple features?▼

Yes, batch analysis with per-ticket workstreams allows you to plan complete test coverage across multiple Jira tickets, generating unified manual tests and automated E2E tests with consolidated phase checkpoints.

What artifacts are output when generating E2E tests and manual tests from requirements?▼

Test generation outputs include manual test cases, E2E specs, page objects, fixtures, and coverage metadata, stored within .sparq folders, E2E directories, and test registries.

Does test generation work with SparQ config and phase checkpoints for QA planning?▼

Yes, the generation pipeline supports integration with SparQ config and phase checkpoints, unifying QA planning and execution by applying consolidated checkpoints to both manual and automated E2E outputs.

What is the best way to unify manual QA test planning and E2E test automation in one workflow?▼

Unifying QA planning and E2E test automation is achieved by generating both manual test cases and automated E2E code from feature requirements simultaneously, ensuring complete coverage and saving execution time.

Are there limitations when generating automated E2E tests from feature requirements for complex features?▼

The generation process relies on the detail level within feature requirements to output accurate E2E specs and page objects, meaning incomplete or ambiguous ticket descriptions may limit the quality of the resulting automated tests.

Related Skills

Explore More Software Engineering Skills→
Space-DinosaursSpace-Dinosaurs
12

implement-ticket

Coordinate ticket-to-PR workflows across Linear, Jira, or freeform inputs.

Official
Advanced
semicolon-devteamsemicolon-devteam

coverage-guide

Executes Gradle builds and collects JVM-based project coverage with Surefire/Failsafe reports.

Official
Advanced
ArogyaReddyArogyaReddy

e2e-testing-patterns

Automate Playwright and Cypress end-to-end testing workflows with page objects and fixtures.

Community
Advanced
JaylaelikeJaylaelike

senior-qa

Generate test suites, analyze coverage, and scaffold E2E tests for ReactJS, NextJS, and NodeJS apps.

Community
Advanced