Map Jira [QE] acceptance criteria to end-to-end test scenarios.
npx skills add https://github.com/flightctl/ai-workflows --skill e2e-flightctl
Please help me install this Agent Skill. Skill: e2e Source: https://github.com/flightctl/ai-workflows/tree/main/e2e Command: npx skills add https://github.com/flightctl/ai-workflows --skill e2e-flightctl
This Skill removes the guesswork of translating Jira [QE] acceptance criteria into dependable end-to-end test coverage by guiding the full workflow from planning to validation and PR review.
Run the e2e workflow by first instructing the agent to ingest a specific QE story key, then proceed through plan, code, validate, and publish once you approve each phase.
High-intent search queries and answers about installing and using this skill.
To generate e2e tests from Jira acceptance criteria, the Skill ingests QE story keys and maps each acceptance criterion to concrete test scenarios. It then produces implementation code that matches your project's existing test patterns and conventions.
Acceptance criteria coverage verification works by validating generated e2e test scenarios against the original Jira ACs. The workflow checks for test anti-patterns and ensures every acceptance criterion has a corresponding concrete test case before allowing pull request creation.
Yes, you need read-only Jira access to automate e2e test planning. The workflow ingests QE story keys and reads acceptance criteria directly from Jira to map them to concrete e2e test scenarios during the planning phase.
Yes, you can use your existing test framework and lifecycle hooks. The Skill discovers your project's e2e infrastructure, including the runner and abstractions, ensuring generated tests follow your real conventions rather than assumptions.
The best way to structure e2e test scenarios for a GitHub pull request is through the workflow's publish phase. It validates AC coverage, checks for anti-patterns, and prepares the PR for iterative reviewer-driven improvements.
Limitations include mandatory validation before PR creation and strict adherence to discovered project test infrastructure. If the project lacks clear test conventions or Jira access is not read-only, the workflow cannot safely produce consistent test output.
flightctlConvert Jira story acceptance criteria into production code with contract-based tests.
cstarleaAutomate pull request reviews for GitHub Copilot agents with inline comments.
EmergenceAIAutomate Jira issue updates with pull request links and test results.
Rinzler78Generate failing acceptance tests from story criteria with ATDD handoff checklists.
