gaia-test-automate

To identify gaps in automated test coverage, the Skill analyzes a story's acceptance criteria against the existing test suite to determine missing tests and risks, outputting a machine-readable plan and verdict.

Test-automation planning for story acceptance criteria involves evaluating specific story requirements to find missing tests, dispatching test-coverage expansion tasks to a QA subagent, and generating a traceable test-automation report.

You can generate a machine-readable test plan by providing a story key to trigger test-automation planning, which analyzes acceptance criteria and outputs a prioritized test-expansion plan to update the Review Gate.

Yes, this test generation approach works without external dependencies, using internal scripts to analyze story acceptance criteria and document automated test coverage gaps directly within your existing workflow.

The best way to document missing automated tests is to analyze story acceptance criteria, generate a machine-readable verdict for the Review Gate, and write a report to docs/test-artifacts for full traceability.

You should use an automated test coverage analysis tool when you need to expand automated test coverage for stories, identify coverage gaps and risks, and orchestrate a test-automation plan to improve quality.