wellapp-ai/well

Overview

This skill converts verified QA Contract criteria (G#N and AC#N) into permanent automated tests so passing scenarios become regression checks. It produces Jest backend tests, Storybook state stories, and Playwright end-to-end specs, then runs the suites to confirm tests pass.

How this skill works

The skill ingests a Verification Report listing passed G#N scenarios and AC#N acceptance criteria. It categorizes each criterion by test type, checks for existing tests, and generates missing Jest tests, Storybook stories, or Playwright specs using standardized templates. Finally it runs the relevant test runner commands and produces a Test Hardening Report summarizing created files and results.

When to use it

• After qa-commit returns GREEN for a commit
• After a debug session fixes an issue (Phase 7: Harden)
• Before merging a PR to ensure all verified criteria have tests
• Manually when you want to convert verified criteria into regressions
• During release prep to lock verified behaviors into tests

Best practices

• Include the original criterion ID (G#N or AC#N) as a comment in each generated test
• Prefer small, focused tests that assert one behavior per case
• Skip generation when an existing test already references the scenario or criterion
• Run the specific test runner (Jest/Storybook/Playwright) after generation to ensure tests are passing
• Add a brief regression note linking to the debug session or issue when hardening a bug fix

Example use cases

• A backend API G#3 that returned correct invoice totals is converted into a Jest test under apps/api/**/__tests__
• A UI AC#2 that describes the loading state is added as a Storybook story variant for the component
• An interaction AC#5 (form submission) becomes a Playwright spec in tests/e2e to prevent regressions
• After a debug session reproduces a flaky invoice-parsing bug, generate a regression test referencing the debug steps
• Before pushing a release, run the skill to ensure every green QA criterion has an automated test