add-robot-tests

To generate Robot Framework tests from feature descriptions, provide the target URL and feature details to consume shared e2e-plan artifacts like feature maps and coverage plans into executable test suites.

Yes, you can convert exploration artifacts into Robot test suites by consuming shared e2e-plan files like exploration reports and coverage plans to drive test generation and ensure feature traceability.

The best way to structure a split testing workflow for Robot tests is to apply gated review and validation phases that generate, author, review, and verify tests against shared feature maps and test cases.

Yes, you need shared artifacts like feature maps and exploration reports to provide the necessary context for generating, authoring, and validating production-grade Robot Framework tests within the workflow.

Robot test generation handles codebase analysis and flaky test fixes by enforcing delegation to shared skills such as analyze-test-codebase, write-robot-code, review-test-cases, and fix-flaky-tests.

Generating Robot tests without exploration reports limits traceability from feature requests to executable tests, reducing the ability to validate coverage plans and enforce gated review steps effectively.