explore-and-generate

Explores a live UI to find untested user flows and outputs a Gherkin test plan.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/tetianna/ai-assisted-qa-automation-2 --skill explore-and-generate-tetianna
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: explore-and-generate
Source: https://github.com/tetianna/ai-assisted-qa-automation-2/tree/main/.cursor/skills/explore-and-generate
Command: npx skills add https://github.com/tetianna/ai-assisted-qa-automation-2 --skill explore-and-generate-tetianna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When there is no Jira ticket defining what to test, QA engineers struggle to identify which user flows lack automation coverage. This Skill systematically explores a live application UI, diffs supported flows against existing Playwright tests, and produces a ready-to-implement Gherkin test plan for the highest-value coverage gap. ## Core Features & Use Cases - Coverage Mapping: Reads existing specs under tests/ to list already-automated user flows so gaps are measurable. - Accessibility-Tree Crawling: Authenticates with DIDAXIS_EMAIL/DIDAXIS_PASSWORD (or reuses playwright/.auth/user.json) and inspects the UI via the accessibility tree rather than screenshots. - Gap Analysis and Prioritization: Diffs supported flows against covered flows and selects one highest-value uncovered flow per run, with a stated rationale. - Gherkin Plan Output: Produces one happy-path and one edge-case scenario with assertable Then steps, ready for a test-writer to implement. - Use Case: Ask the agent to explore the Didaxis settings page for untested flows; it returns a Gherkin feature covering an uncovered flow such as locale switching, plus a list of deferred gaps for later runs. ## Quick Start Ask the agent to explore the settings page for untested flows and generate a Gherkin coverage plan.

Frequently Asked Questions about explore-and-generate

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

FAQPage Schema
How do I find untested user flows in my web app?▼

Run this Skill against a target page: it reads your existing Playwright specs, crawls the live UI through the accessibility tree, and diffs supported flows against covered ones. It then outputs a Gherkin plan for the single highest-value uncovered flow.

How to generate Gherkin test scenarios without a Jira ticket?▼

This Skill is designed exactly for that case: it explores the UI, picks one uncovered flow, and writes a Gherkin feature with one happy-path and one edge-case scenario. If a ticket already exists, use the jira-ticket-to-gherkin skill instead.

Does the exploration require login credentials?▼

Yes. It authenticates using DIDAXIS_EMAIL and DIDAXIS_PASSWORD from .env via the UI login at /login, or reuses the stored session in playwright/.auth/user.json created by tests/auth.setup.ts.

Can this skill write or modify Playwright test specs?▼

No. It is strictly read-only: it explores the UI and produces a Gherkin plan only. Writing or editing Playwright specs, page object models, or application source is explicitly out of scope and left to a separate test-writer step.

Why does the skill only plan one flow per run?▼

Batching multiple plans reduces quality and focus, so the skill selects a single highest-value uncovered flow per invocation based on risk, frequency, and blast radius. Other uncovered flows are listed as deferred for later runs.