qa-acceptance-criteria

To generate Playwright tests and acceptance criteria from a workblock, provide the workblock identifier and codebase context. The skill outputs internal and client-facing user-stories markdown docs alongside a tests/{wb}.spec.ts file.

Turn Teamwork tasks and commits into automated QA tests by running this skill with your workblock scope. It grounds each criterion in code, commits, and design references to produce a Playwright spec with one test per criterion.

Creating client-facing user stories for QA acceptance involves translating signed-off scope into plain English criteria. This skill generates a markdown doc matching engineering-focused criteria to ensure alignment and reduce guesswork.

You do not need a Playwright environment to generate the spec file, but running the output tests/{wb}.spec.ts requires one. The skill produces the test file and markdown documents based solely on the provided workblock context.

Yes, you can generate cross-cutting regression coverage sections in a Playwright spec. The skill includes mandatory cross-cutting sections and references to workflow guidance within the output test file to ensure comprehensive coverage.

Generated user stories might mismatch the codebase if the workblock context is incomplete. The skill grounds each criterion in code, recent commits, and Teamwork tasks, so providing accurate identifiers ensures alignment.