qa-stlc-agents

Run the full STLC pipeline for a work item — fetch → test cases → Gherkin → live-captured Playwright → write to Helix-QA.

Set up a Cowork scheduled task that polls for newly-Resolved work items and runs the STLC pipeline on a cadence.

Verify the QA STLC setup — MCP servers reachable, auth working, Playwright MCP available.

Start the headless STLC webhook bridge so ADO / Jira / GitHub state changes trigger the pipeline automatically.

Use when creating or generating manual test cases for an Azure DevOps PBI, Bug, User Story, or Feature. Triggers on: "create test cases", "generate test cases", "link test cases", "manual tests", "TestedBy", "ADO test cases". Never creates test cases for Epics. Always confirms before creating test cases for a Feature.

Use when organising linked manual test cases into an Azure DevOps test plan by creating requirement-based suites under static suites. Triggers on: "requirement based suite", "requirement suite", "test plan suite", "add PBI to test plan", "create suite for work item", "organise test cases in test plan". Runs AFTER manual test cases are created and linked (TestedBy) to a PBI or Bug. Selects the plan by iteration + area path and the static suite by work item type (PBI / Bugs).

MANDATORY pre-flight protocol for every QA STLC agent run. Must be applied BEFORE creating any test cases, Gherkin feature files, Playwright locators, page objects, or step definitions in Azure DevOps. Prevents duplicate test cases, duplicate feature file attachments, and duplicate Playwright code across multiple runs or agents on the same work item. Triggers on any task involving: ADO work items, test cases, feature files, Gherkin BDD, Playwright automation, locators, page objects, step definitions, qa-gherkin-generator, qa-test-case-manager, or qa-playwright-generator tools.

Use when generating Gherkin feature files, BDD scenarios, or .feature files from Azure DevOps or Jira work items. Triggers on: "Gherkin", "feature file", "BDD", "scenarios", "acceptance criteria automation", "Given When Then", "regression suite". Enforces live navigation before writing any scenario and links generated files back to work items. Works with Feature, PBI, and Bug work item types.

Use when generating Playwright TypeScript automation code from Gherkin feature files or ADO work items. Triggers on: "Playwright", "page object", "locators", "step definitions", "automation", "self-healing", "TimingHealer", "VisualIntentChecker", "locator repository". Reads existing files before generating to prevent duplicates. Works with PBI, Bug, and Feature work item types.