Every ticket type, covered

A feature ticket is groomed but sits in the QA backlog for days before anyone writes cases for it.

QEPilot drafts manual test cases the same day the ticket is groomed — mapped to each acceptance criterion — then ships the approved ones as Playwright specs.

A bug is fixed, but no regression test is added, so it quietly comes back two releases later.

QEPilot turns the fix into a traceable manual case and a Playwright spec wired into CI, so the same regression is caught automatically on every future PR.

Acceptance criteria are vague ("export large files"), and testers either guess or stall.

Instead of guessing, QEPilot flags the ambiguity on the ticket and asks — the same thing a careful human QA engineer would do — before writing a case on an assumption.

Whole areas of the product have no automated coverage, and no one has time to backfill it.

Point QEPilot at existing tickets and specs; it works through them steadily, drafting reviewable cases and automating the approved ones without a dedicated project.