accelint-ac-to-playwright

Convert acceptance criteria into validated JSON test plans and Playwright spec files.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/Ahnd6474/Jakal-flow --skill accelint-ac-to-playwright
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: accelint-ac-to-playwright
Source: https://github.com/Ahnd6474/Jakal-flow/tree/main/.skill-staging/skills/accelint-ac-to-playwright
Command: npx skills add https://github.com/Ahnd6474/Jakal-flow --skill accelint-ac-to-playwright

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill requires zod, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Converts human-written acceptance criteria into machine-validated JSON test plans and Playwright spec files so teams can quickly and reliably create automated UI tests without hand-coding the test steps.

Core Features & Use Cases

  • Assessment Mode: Analyze and report whether AC are automation-ready without generating artifacts.
  • Full Conversion: Convert bullet-style Markdown or Gherkin files into JSON plans, validate them against a schema, and translate plans into Playwright spec files.
  • Validation & Safe Workflow: Enforces controlled vocabulary from test-hooks, runs plan-schema validation, and requires explicit output directories and a two-attempt validation+fix retry protocol.
  • Use Case: QA engineers and devs can turn feature files or markdown AC into reproducible Playwright tests and a summary of required test hooks for CI integration.

Quick Start

Ask the skill to "Convert the acceptance criteria file at <path> into validated Playwright tests and write plans, tests, and a summary to the specified output directories."

Frequently Asked Questions about accelint-ac-to-playwright

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

FAQPage Schema
How do I convert acceptance criteria into Playwright tests?β–Ό

Convert acceptance criteria into Playwright tests by transforming bullet-style Markdown or Gherkin feature files into machine-validated JSON test plans and Playwright spec files, automating UI test generation without hand-coding steps.

Can I check if my Gherkin feature files are ready for test automation?β–Ό

Yes, you can run an assessment mode to analyze Gherkin feature files or Markdown acceptance criteria and report whether they are automation-ready, without generating any test artifacts.

Does this acceptance criteria to Playwright conversion process enforce schema validation?β–Ό

Yes, the conversion process enforces schema validation by checking generated JSON plans against a defined plan schema and applying a controlled vocabulary from test hooks, including a two-attempt validation and fix retry protocol.

What is the best way to generate a summary of required test hooks from acceptance criteria?β–Ό

The best way to generate a summary of required test hooks is to convert your acceptance criteria into validated JSON plans, which simultaneously produces a summary of required test hooks for CI integration alongside the Playwright spec files.

Do I need to specify output directories when generating Playwright spec files?β–Ό

Yes, you must explicitly specify user-defined output directories for plans, tests, and summaries, as the workflow only writes generated JSON plans and Playwright spec files to these designated safe locations.