Overview

This skill orchestrates expanding test automation coverage by selecting sub-workflows based on user intent (e.g., PL for plan). It operates under the Master Test Architect and Quality Advisor (Murat) as the TEA module. After execution, it requires validation against the checklist to ensure thorough coverage.

How This Skill Works

The skill interprets user intent to pick a sub-workflow trigger (PL maps to ./workflow-plan.md) and follows the corresponding sub-workflow file. It then instructs the user or system to Read and follow the selected sub-workflow, and upon completion, validates the result against ./checklist.md.

When to Use It

• The user says to expand test coverage or asks to automate tests (e.g., lets expand test coverage or I want to automate tests).
• You need to plan a structured test automation expansion using the predefined sub-workflow (PL -> ./workflow-plan.md).
• Starting a new feature or module requires a test automation plan before implementation.
• You want to ensure compliance by validating results against the checklist after executing a sub-workflow.
• You need to trigger a TEA workflow iteration to widen automation across the codebase.

Quick Start

1. Step 1: User states an intent to expand test coverage (e.g., lets expand test coverage or I want to automate tests).
2. Step 2: The system maps to the PL trigger and loads ./workflow-plan.md for planning.
3. Step 3: Read and follow the selected sub-workflow, then validate results against ./checklist.md.

Best Practices

• Use the PL trigger to initiate a formal plan via ./workflow-plan.md before implementing automation steps.
• Always read and follow the selected sub-workflow file to ensure consistent execution.
• Validate completion strictly against ./checklist.md to confirm coverage goals are met.
• Keep sub-workflows modular and editable to accommodate new modules without breaking the plan.
• Document decisions and updates resulting from the plan for traceability and audits.

Example Use Cases

• A team asks to expand test coverage for a new feature; initiate with PL and follow the workflow-plan.md plan.
• QA wants to automate tests across multiple components by selecting the appropriate sub-workflow and validating with the checklist.
• Onboarding a new module, the TEA workflow is triggered to create a plan before test automation implementation.
• Completed automation expansion is verified by cross-checking against ./checklist.md for completeness.
• A project refactors tests; the plan ensures coverage remains aligned with the updated codebase and passes the checklist.

Frequently Asked Questions