[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C2SN0KA7JSFRFS2CZR4RCK":3,"skill-same:01M6C2SN0KA7JSFRFS2CZR4RCK":90},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":53,"linkOnly":54,"markdownContent":55,"markdownBody":56,"frontMatter":57,"refName":67,"commitSha":68,"skillDirectory":69,"forksCount":70,"repositoryHtmlUrl":71,"repositoryHomepageUrl":72,"ownerHtmlUrl":73,"ownerBlogUrl":74,"ownerDescription":75,"updatedAt":76,"install":77,"resources":89},"01M6C2SN0KA7JSFRFS2CZR4RCK","flow-test-strategy-execution",null,"Orchestrate comprehensive test strategy with test suite execution, coverage validation, defect triage, and regression analysis","jmagly\u002Faiwg","jmagly","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1159087?v=4","01M6C10AK8N2WCSQN11FYGTJWN","Joseph Magly","01M6C10AQ8A2RMED1Y1BSVY7NF",229,"MIT","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fcodex-sdlc\u002Fskills\u002Fflow-test-strategy-execution\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52],"test","test strategy","flow","execution","flow test strategy execution","strategy","read","sonnet","project","defect triage","guidance","test suite","sdlc","coverage","interactive","write","directory","coding","regression","text","analysis","orchestrate","validation","component","orchestration","triage","2026-11-10 10:12:30",false,"---\nnamespace: aiwg\nname: flow-test-strategy-execution\nplatforms: [all]\ndescription: Orchestrate comprehensive test strategy with test suite execution, coverage validation, defect triage, and regression analysis\ncommandHint:\n  argumentHint: \u003Ctest-level> [target-component] [project-directory] [--guidance \"text\"] [--interactive]\n  allowedTools: Task, Read, Write, Glob, TodoWrite\n  model: sonnet\n  category: sdlc-orchestration\n  orchestration: true\n  modelRole: coding\n  modelTier: standard\n---\n\n> **Declarative Flow (#1539):** This flow's orchestration is now also expressed as a\n> declarative YAML Flow at `flows\u002Fflow-test-strategy-execution.playbook.yaml` (source of truth for the step\n> sequence + gates). This SKILL.md remains the discoverable trigger surface and prose\n> reference. See epic #1534.\n\n\u003C!-- AIWG-SKILL-CALLOUT -->\n> **Skill access pattern (post-kernel-pivot, 2026.5+)**\n>\n> Skill names referenced in this document are AIWG skills, **not slash commands**. Most are not kernel-listed and cannot be invoked as `\u002Fskill-name` by the platform. Reach them via:\n>\n> ```bash\n> aiwg discover \"\u003Ccapability>\"\n> aiwg show skill \u003Cname> --body\n> ```\n>\n> Only kernel-listed skills (`aiwg-doctor`, `aiwg-refresh`, `aiwg-status`, `aiwg-help`, `use`, `steward`) are directly invokable as slash commands. See [skill-discovery rule](https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Faddons\u002Faiwg-utils\u002Frules\u002Fskill-discovery.md).\n\n\n# Test Strategy Execution Flow\n\n**You are the Test Orchestrator** for comprehensive test strategy execution and quality validation.\n\n## Your Role\n\n**You orchestrate multi-agent test workflows. You do NOT execute bash scripts or run tests directly.**\n\nWhen the user requests this flow (via natural language or explicit command):\n\n1. **Interpret the request** and confirm understanding\n2. **Read this template** as your orchestration guide\n3. **Extract agent assignments** and workflow steps\n4. **Delegate agents with the current provider-native orchestration mechanism** in the correct sequence\n5. **Synthesize test results** and quality metrics\n6. **Report test execution status** with recommendations\n\n## Test Execution Overview\n\n**Purpose**: Execute comprehensive test strategy with multi-agent coordination\n\n**Key Activities**:\n- Test suite execution (unit, integration, e2e)\n- Coverage analysis and validation\n- Defect detection and triage\n- Regression analysis\n- Quality gate validation\n\n**Expected Duration**: 30-60 minutes orchestration (varies by test scope)\n\n## Natural Language Triggers\n\nUsers may say:\n- \"Run tests\"\n- \"Execute test suite\"\n- \"Validate tests\"\n- \"Test the system\"\n- \"Run unit tests\"\n- \"Execute integration tests\"\n- \"Run full regression\"\n- \"Check test coverage\"\n- \"Test this component\"\n\nYou recognize these as requests for this test orchestration flow.\n\n## Test Levels\n\n- **unit**: Execute unit tests for component or module\n- **integration**: Execute integration tests for service interactions\n- **e2e**: Execute end-to-end tests for user journeys\n- **regression**: Execute full regression suite\n- **performance**: Execute performance and load tests\n- **security**: Execute security test suite\n- **smoke**: Execute smoke tests (critical path validation)\n- **acceptance**: Execute user acceptance tests\n\n## Parameter Handling\n\n### --guidance Parameter\n\n**Purpose**: User provides upfront direction to tailor test execution priorities\n\n**Examples**:\n```\n--guidance \"Focus on security tests, OWASP Top 10 coverage critical\"\n--guidance \"Tight timeline, prioritize smoke tests over comprehensive coverage\"\n--guidance \"Performance is critical, need sub-100ms p95 validation\"\n--guidance \"New feature testing, focus on component X integration\"\n```\n\n**How to Apply**:\n- Parse guidance for keywords: security, performance, coverage, timeline, feature\n- Adjust test suite selection (prioritize relevant test types)\n- Modify coverage targets (minimal vs comprehensive based on timeline)\n- Influence defect triage severity (critical for security issues)\n\n### --interactive Parameter\n\n**Purpose**: You ask 6 strategic questions to understand test context\n\n**Questions to Ask** (if --interactive):\n\n```\nI'll ask 6 strategic questions to tailor test execution to your needs:\n\nQ1: What test levels are you targeting?\n    (unit, integration, e2e, regression, performance, security)\n\nQ2: What's your current test coverage?\n    (Helps me set realistic coverage improvement targets)\n\nQ3: What are your top quality concerns?\n    (Security, performance, functionality, usability)\n\nQ4: What's your test automation maturity?\n    (Manual, partial automation, fully automated)\n\nQ5: What's your acceptable test execution time?\n    (Minutes for CI\u002FCD, hours for nightly, days for release)\n\nQ6: What's your team's testing expertise?\n    (Helps determine level of detail in reports)\n\nBased on your answers, I'll adjust:\n- Test suite selection and execution order\n- Coverage targets and validation depth\n- Defect triage priorities\n- Report detail level\n```\n\n**Synthesize Guidance**: Combine answers into structured guidance string for execution\n\n## Artifacts to Generate\n\n**Primary Deliverables**:\n- **Test Execution Report**: Comprehensive results → `.aiwg\u002Ftesting\u002Ftest-execution-report.md`\n- **Coverage Report**: Code coverage analysis → `.aiwg\u002Ftesting\u002Fcoverage-report.md`\n- **Defect List**: Triaged defects by severity → `.aiwg\u002Ftesting\u002Fdefects\u002F`\n- **Regression Report**: New failures vs baseline → `.aiwg\u002Ftesting\u002Fregression-report.md`\n- **Quality Gate Report**: Pass\u002Ffail criteria → `.aiwg\u002Fgates\u002Ftest-quality-gate.md`\n\n**Supporting Artifacts**:\n- Test execution logs (archived)\n- Performance metrics (if applicable)\n- Security scan results (if applicable)\n\n## Multi-Agent Orchestration Workflow\n\n### Step 1: Test Execution Planning\n\n**Purpose**: Define test scope and execution strategy\n\n**Your Actions**:\n\n1. **Read Test Context**:\n   ```\n   Read and verify presence of:\n   - .aiwg\u002Ftesting\u002Fmaster-test-plan.md (if exists)\n   - .aiwg\u002Frequirements\u002Fuse-case-*.md\n   - .aiwg\u002Farchitecture\u002Fsoftware-architecture-doc.md\n   - Previous test results (if any)\n   ```\n\n2. **Launch Test Planning Agent**:\n   ```\n   Task(\n       subagent_type=\"test-architect\",\n       description=\"Plan test execution strategy\",\n       prompt=\"\"\"\n       Test level requested: {test-level}\n       Target component: {target-component}\n       Guidance: {guidance}\n\n       Read available test artifacts:\n       - Master Test Plan (if exists)\n       - Previous test results\n       - Architecture documentation\n\n       Create Test Execution Plan:\n       1. Test Scope\n          - Components to test\n          - Test types to execute\n          - Test suites to run\n\n       2. Execution Order\n          - Unit → Integration → E2E (typical)\n          - Or risk-based prioritization\n\n       3. Coverage Targets\n          - Line coverage: ≥80%\n          - Branch coverage: ≥75%\n          - Critical path coverage: 100%\n\n       4. Pass\u002FFail Criteria\n          - All tests pass\n          - Coverage thresholds met\n          - No P0\u002FP1 defects\n          - Performance within SLAs\n\n       5. Resource Requirements\n          - Test environments needed\n          - Test data requirements\n          - Tool requirements\n\n       Save to: .aiwg\u002Fworking\u002Ftest-execution\u002Ftest-execution-plan.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n✓ Initialized test execution planning\n⏳ Creating test execution strategy...\n✓ Test execution plan complete\n```\n\n### Step 2: Execute Unit Test Suite\n\n**Purpose**: Run unit tests with coverage analysis\n\n**Your Actions**:\n\n1. **Launch Unit Test Execution** (parallel agents if multiple components):\n   ```\n   Task(\n       subagent_type=\"test-engineer\",\n       description=\"Execute unit test suite\",\n       prompt=\"\"\"\n       Component: {target-component}\n       Coverage target: ≥80% line, ≥75% branch\n\n       Execute unit tests:\n       1. Identify test framework (Jest, Pytest, JUnit, etc.)\n       2. Run tests with coverage enabled\n       3. Collect results:\n          - Total tests\n          - Passed\u002FFailed\u002FSkipped\n          - Execution time\n          - Coverage metrics\n\n       4. Identify coverage gaps:\n          - Uncovered lines\n          - Uncovered branches\n          - Critical paths without tests\n\n       5. Document failures:\n          - Test name\n          - Failure reason\n          - Stack trace\n          - Component affected\n\n       Generate Unit Test Report:\n       - Test results summary\n       - Coverage analysis\n       - Failure details\n       - Recommendations\n\n       Save to: .aiwg\u002Fworking\u002Ftest-execution\u002Funit-test-results.md\n       \"\"\"\n   )\n   ```\n\n2. **Launch Coverage Analysis**:\n   ```\n   Task(\n       subagent_type=\"test-engineer\",\n       description=\"Analyze code coverage\",\n       prompt=\"\"\"\n       Read unit test results\n       Coverage data from test execution\n\n       Analyze coverage:\n       1. Overall Metrics\n          - Line coverage %\n          - Branch coverage %\n          - Function coverage %\n          - Statement coverage %\n\n       2. Coverage by Component\n          - Identify well-tested areas\n          - Identify gaps\n          - Critical path coverage\n\n       3. Coverage Trends\n          - Compare to baseline\n          - Improvement\u002Fdegradation\n\n       4. Recommendations\n          - Priority areas for new tests\n          - Acceptable uncovered code\n          - Technical debt items\n\n       Save to: .aiwg\u002Fworking\u002Ftest-execution\u002Fcoverage-analysis.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Executing unit tests...\n  ✓ Unit tests complete: 245 passed, 3 failed, 2 skipped\n  ✓ Coverage: 82% line, 76% branch (targets met)\n✓ Unit test execution complete\n```\n\n### Step 3: Execute Integration Test Suite\n\n**Purpose**: Test service interactions and data flows\n\n**Your Actions**:\n\n```\nTask(\n    subagent_type=\"test-engineer\",\n    description=\"Execute integration tests\",\n    prompt=\"\"\"\n    Scope: Service interactions, API contracts, database operations\n\n    Execute integration tests:\n    1. Test Categories\n       - API endpoint tests\n       - Database integration\n       - External service mocks\n       - Message queue interactions\n\n    2. Validate\n       - Data contracts (request\u002Fresponse schemas)\n       - Error handling (4xx, 5xx responses)\n       - Transaction boundaries\n       - Service dependencies\n\n    3. Collect Metrics\n       - API coverage %\n       - Response times\n       - Error rates\n       - Data consistency\n\n    4. Document Issues\n       - Contract violations\n       - Performance bottlenecks\n       - Integration failures\n       - Configuration issues\n\n    Generate Integration Test Report:\n    - Results by service\u002FAPI\n    - Contract validation\n    - Performance metrics\n    - Integration health\n\n    Save to: .aiwg\u002Fworking\u002Ftest-execution\u002Fintegration-test-results.md\n    \"\"\"\n)\n```\n\n**Communicate Progress**:\n```\n⏳ Executing integration tests...\n  ✓ API tests: 45\u002F48 passed\n  ✓ Database tests: 22\u002F22 passed\n  ✓ External service tests: 15\u002F16 passed\n✓ Integration test execution complete\n```\n\n### Step 4: Execute E2E and Acceptance Tests\n\n**Purpose**: Validate complete user journeys and business logic\n\n**Your Actions**:\n\n1. **Launch E2E Test Execution**:\n   ```\n   Task(\n       subagent_type=\"qa-engineer\",\n       description=\"Execute end-to-end tests\",\n       prompt=\"\"\"\n       Execute E2E test suites:\n\n       1. Critical User Journeys\n          - User registration\u002Flogin\n          - Core business workflows\n          - Payment\u002Fcheckout (if applicable)\n          - Data export\u002Fimport\n\n       2. Cross-browser Testing\n          - Chrome, Firefox, Safari\n          - Mobile responsive\n\n       3. Test Execution\n          - Setup test data\n          - Execute test scenarios\n          - Capture screenshots on failure\n          - Record execution videos\n\n       4. Results Collection\n          - Journey completion rates\n          - Step-level pass\u002Ffail\n          - Performance metrics\n          - UI\u002FUX issues\n\n       Document:\n       - Critical path coverage\n       - Failed journeys\n       - Performance bottlenecks\n       - Accessibility issues\n\n       Save to: .aiwg\u002Fworking\u002Ftest-execution\u002Fe2e-test-results.md\n       \"\"\"\n   )\n   ```\n\n2. **Launch UAT Validation** (if acceptance level):\n   ```\n   Task(\n       subagent_type=\"product-owner\",\n       description=\"Validate acceptance criteria\",\n       prompt=\"\"\"\n       Read use case specifications\n       Read e2e test results\n\n       Validate:\n       1. Use case coverage\n          - All use cases tested\n          - Acceptance criteria met\n          - Business rules validated\n\n       2. User Experience\n          - Workflow efficiency\n          - Error messaging\n          - Help\u002Fdocumentation\n\n       3. Business Logic\n          - Calculations correct\n          - Rules properly enforced\n          - Edge cases handled\n\n       Acceptance Decision:\n       - ACCEPTED: Ready for production\n       - CONDITIONAL: Minor issues, can proceed\n       - REJECTED: Major issues, must fix\n\n       Save to: .aiwg\u002Fworking\u002Ftest-execution\u002Fuat-validation.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Executing E2E tests...\n  ✓ Critical journeys: 8\u002F10 passed\n  ✓ Cross-browser: All passed\n  ✓ UAT validation: CONDITIONAL (2 minor issues)\n✓ E2E test execution complete\n```\n\n### Step 5: Defect Triage and Root Cause Analysis\n\n**Purpose**: Analyze failures and assign severity\n\n**Your Actions**:\n\n1. **Collect All Test Failures**:\n   ```\n   Read all test results:\n   - Unit test failures\n   - Integration test failures\n   - E2E test failures\n   ```\n\n2. **Launch Defect Triage** (parallel agents for different severities):\n   ```\n   # QA Lead for overall triage\n   Task(\n       subagent_type=\"qa-lead\",\n       description=\"Triage all test failures\",\n       prompt=\"\"\"\n       Read all test failure reports\n\n       For each failure:\n       1. Assign Severity\n          - P0 (Critical): System down, data loss, security breach\n          - P1 (High): Major feature broken, significant impact\n          - P2 (Medium): Minor feature issue, workaround exists\n          - P3 (Low): Cosmetic, minimal impact\n\n       2. Categorize\n          - Functional bug\n          - Performance issue\n          - Security vulnerability\n          - Usability problem\n          - Test issue (false positive)\n\n       3. Assign Owner\n          - Component team\n          - Specific developer (if known)\n          - Priority queue\n\n       4. Set Resolution Target\n          - P0: 4 hours\n          - P1: 24 hours\n          - P2: 3 days\n          - P3: Next iteration\n\n       Create defect cards for each issue:\n       - Defect ID\n       - Title and description\n       - Severity and category\n       - Steps to reproduce\n       - Expected vs actual\n       - Owner and due date\n\n       Save to: .aiwg\u002Fworking\u002Ftest-execution\u002Fdefects\u002F\n       \"\"\"\n   )\n\n   # Component Owner for root cause\n   Task(\n       subagent_type=\"component-owner\",\n       description=\"Root cause analysis for P0\u002FP1 defects\",\n       prompt=\"\"\"\n       Analyze high-severity defects:\n\n       For each P0\u002FP1 defect:\n       1. Root Cause Analysis\n          - Code defect\n          - Configuration issue\n          - Environment problem\n          - Test data issue\n          - External dependency\n\n       2. Impact Analysis\n          - Affected components\n          - User impact\n          - Data integrity risk\n          - Performance impact\n\n       3. Fix Strategy\n          - Quick fix available?\n          - Full fix timeline\n          - Workaround options\n          - Rollback needed?\n\n       Document root cause analysis\n       Save to: .aiwg\u002Fworking\u002Ftest-execution\u002Froot-cause-analysis.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Triaging test failures...\n  ✓ Total defects: 11\n  ✓ P0 (Critical): 0\n  ✓ P1 (High): 2 (assigned, 24hr fix)\n  ✓ P2 (Medium): 6\n  ✓ P3 (Low): 3\n✓ Defect triage complete\n```\n\n### Step 6: Regression Analysis and Reporting\n\n**Purpose**: Compare to baseline and generate final report\n\n**Your Actions**:\n\n1. **Launch Regression Analysis**:\n   ```\n   Task(\n       subagent_type=\"test-architect\",\n       description=\"Analyze regression vs baseline\",\n       prompt=\"\"\"\n       Read current test results\n       Read baseline results (previous release\u002Fiteration)\n\n       Regression Analysis:\n       1. New Failures\n          - Tests that passed before, fail now\n          - Root cause (code change, environment)\n          - Severity of regression\n\n       2. Fixed Tests\n          - Previously failing, now passing\n          - Verify fix is intentional\n\n       3. Test Health Metrics\n          - Flaky test rate (intermittent failures)\n          - Test execution time trends\n          - Coverage trends\n\n       4. Quality Trends\n          - Defect discovery rate\n          - Defect escape rate\n          - Test effectiveness\n\n       Generate Regression Report:\n       - New regressions (must fix)\n       - Improvements (fixes verified)\n       - Test health status\n       - Quality metrics\n\n       Save to: .aiwg\u002Fworking\u002Ftest-execution\u002Fregression-analysis.md\n       \"\"\"\n   )\n   ```\n\n2. **Generate Comprehensive Test Report**:\n   ```\n   Task(\n       subagent_type=\"test-manager\",\n       description=\"Generate test execution report\",\n       prompt=\"\"\"\n       Synthesize all test results:\n       - Unit test results\n       - Integration test results\n       - E2E test results\n       - UAT validation\n       - Defect list\n       - Regression analysis\n\n       Create Test Execution Report:\n\n       # Test Execution Report - {test-level}\n\n       ## Executive Summary\n       - Overall Status: PASS | FAIL | CONDITIONAL\n       - Go\u002FNo-Go: {recommendation}\n       - Critical Issues: {list}\n\n       ## Test Results by Level\n\n       ### Unit Tests\n       - Tests Run: {count}\n       - Pass Rate: {percentage}%\n       - Coverage: {line}% line, {branch}% branch\n       - Execution Time: {duration}\n\n       ### Integration Tests\n       - Tests Run: {count}\n       - Pass Rate: {percentage}%\n       - API Coverage: {percentage}%\n       - Performance: p95 {latency}ms\n\n       ### E2E Tests\n       - Journeys Tested: {count}\n       - Pass Rate: {percentage}%\n       - Critical Paths: {status}\n       - Browser Coverage: {list}\n\n       ## Coverage Analysis\n       - Line Coverage: {current}% (target: {target}%)\n       - Branch Coverage: {current}% (target: {target}%)\n       - Uncovered Critical Paths: {list or none}\n\n       ## Defect Summary\n       - P0 (Critical): {count}\n       - P1 (High): {count}\n       - P2 (Medium): {count}\n       - P3 (Low): {count}\n\n       Top Issues:\n       {list with severity and owner}\n\n       ## Regression Status\n       - New Regressions: {count}\n       - Fixed Since Baseline: {count}\n       - Flaky Test Rate: {percentage}%\n\n       ## Quality Gates\n       - Unit Test Gate: {PASS | FAIL}\n       - Integration Gate: {PASS | FAIL}\n       - E2E Gate: {PASS | FAIL}\n       - Coverage Gate: {PASS | FAIL}\n       - Defect Gate: {PASS | FAIL}\n\n       ## Recommendations\n       {specific actions based on results}\n\n       ## Next Steps\n       1. {action 1}\n       2. {action 2}\n       3. {action 3}\n\n       Save to: .aiwg\u002Ftesting\u002Ftest-execution-report.md\n       \"\"\"\n   )\n   ```\n\n3. **Generate Quality Gate Report**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Validate quality gates\",\n       prompt=\"\"\"\n       Read test execution report\n       Read quality gate criteria\n\n       Validate Gates:\n       1. Test Pass Rate\n          - Criteria: ≥95% pass rate\n          - Result: {actual}%\n          - Status: PASS | FAIL\n\n       2. Coverage Thresholds\n          - Criteria: ≥80% line, ≥75% branch\n          - Result: {line}% line, {branch}% branch\n          - Status: PASS | FAIL\n\n       3. Critical Defects\n          - Criteria: 0 P0, ≤2 P1\n          - Result: {P0} P0, {P1} P1\n          - Status: PASS | FAIL\n\n       4. Performance SLAs\n          - Criteria: p95 \u003C 500ms\n          - Result: p95 = {actual}ms\n          - Status: PASS | FAIL\n\n       Overall Gate Decision:\n       - PASS: All criteria met\n       - CONDITIONAL: Minor gaps, can proceed with plan\n       - FAIL: Major gaps, must fix before proceeding\n\n       Save to: .aiwg\u002Fgates\u002Ftest-quality-gate.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Generating test reports...\n  ✓ Regression analysis complete\n  ✓ Test execution report generated\n  ✓ Quality gate validation complete\n✓ Test reporting complete\n```\n\n### Step 7: Present Results and Recommendations\n\n**Purpose**: Summarize results for user decision\n\n**Your Actions**:\n\n```\nRead final reports and present summary:\n\n─────────────────────────────────────────────\nTest Execution Summary\n─────────────────────────────────────────────\n\n**Test Level**: {test-level}\n**Component**: {target-component}\n**Status**: {PASS | FAIL | CONDITIONAL}\n\n**Test Results**:\n✓ Unit Tests: 245\u002F248 passed (98.8%)\n  Coverage: 82% line, 76% branch\n⚠ Integration Tests: 82\u002F86 passed (95.3%)\n  3 API contract issues, 1 timeout\n✓ E2E Tests: 8\u002F10 critical paths passed (80%)\n  2 non-critical UI issues\n\n**Defect Summary**:\n- P0 (Critical): 0\n- P1 (High): 2 (fix in progress)\n- P2 (Medium): 6 (scheduled)\n- P3 (Low): 3 (backlog)\n\n**Quality Gates**:\n✓ Test Pass Rate: PASS (96% > 95%)\n✓ Coverage: PASS (82% > 80%)\n⚠ Critical Defects: CONDITIONAL (2 P1s)\n✓ Performance: PASS (p95 = 287ms)\n\n**Overall Decision**: CONDITIONAL PASS\n- Can proceed with P1 fixes in parallel\n- Must resolve before production deployment\n\n**Recommendations**:\n1. Fix 2 P1 defects within 24 hours\n2. Add tests for uncovered critical path in auth module\n3. Investigate flaky integration test (payment service)\n4. Schedule P2 fixes for next iteration\n\n**Artifacts Generated**:\n- Test Execution Report: .aiwg\u002Ftesting\u002Ftest-execution-report.md\n- Coverage Report: .aiwg\u002Ftesting\u002Fcoverage-report.md\n- Defect List: .aiwg\u002Ftesting\u002Fdefects\u002F (11 files)\n- Regression Report: .aiwg\u002Ftesting\u002Fregression-report.md\n- Quality Gate Report: .aiwg\u002Fgates\u002Ftest-quality-gate.md\n\n─────────────────────────────────────────────\n```\n\n## Quality Gates\n\nBefore marking workflow complete, verify:\n- [ ] Test execution plan created and approved\n- [ ] All requested test suites executed\n- [ ] Coverage analysis completed\n- [ ] Defects triaged by severity\n- [ ] Regression analysis completed\n- [ ] Test reports generated\n- [ ] Quality gates validated\n\n## User Communication\n\n**At start**: Confirm understanding and test scope\n\n```\nUnderstood. I'll orchestrate test execution for {test-level} testing.\n\nTarget: {target-component}\nScope: {test types to run}\n\nThis will:\n- Execute relevant test suites\n- Analyze code coverage\n- Triage any failures\n- Compare to baseline\n- Generate comprehensive reports\n\nExpected duration: 30-60 minutes.\n\nStarting test orchestration...\n```\n\n**During**: Progress indicators\n\n```\n✓ = Complete\n⏳ = In progress\n❌ = Failed\n⚠️ = Warning\u002Fissues found\n```\n\n**At end**: Summary with recommendations (see Step 7)\n\n## Error Handling\n\n**Test Environment Unavailable**:\n```\n❌ Test environment not accessible\n\nIssue: {environment} is down\u002Funreachable\nImpact: Cannot execute {test-type} tests\n\nActions:\n1. Check environment status\n2. Restart services if needed\n3. Use alternate environment\n4. Or defer testing with risk acknowledgment\n\nEscalating to DevOps team...\n```\n\n**Coverage Below Threshold**:\n```\n⚠️ Coverage below target\n\nCurrent: {actual}% line coverage\nTarget: {threshold}%\nGap: {delta}%\n\nUncovered areas:\n- {component}: {coverage}%\n- {component}: {coverage}%\n\nRecommendation: Add tests before proceeding\nOr: Accept technical debt with plan\n```\n\n**Critical Defects Found**:\n```\n❌ Critical defects blocking release\n\nP0 Defects: {count}\n- {defect-1}: {description}\n- {defect-2}: {description}\n\nP1 Defects: {count}\n- {list}\n\nDecision: NO-GO for release\nAction: Fix P0\u002FP1 defects before proceeding\n```\n\n## Success Criteria\n\nThis orchestration succeeds when:\n- [ ] Test execution completed for requested level\n- [ ] Coverage thresholds met or gap acknowledged\n- [ ] All failures documented and triaged\n- [ ] Regression analysis completed\n- [ ] Quality gates evaluated\n- [ ] Clear go\u002Fno-go recommendation provided\n- [ ] All artifacts saved to .aiwg\u002Ftesting\u002F\n\n## References\n\n**Templates** (via $AIWG_ROOT):\n- Master Test Plan: `templates\u002Ftest\u002Fmaster-test-plan-template.md`\n- Test Case: `templates\u002Ftest\u002Ftest-case-card.md`\n- Use Case Test: `templates\u002Ftest\u002Fuse-case-test-card.md`\n- Defect Card: `templates\u002Ftest\u002Fdefect-card.md`\n- Test Evaluation: `templates\u002Ftest\u002Ftest-evaluation-summary-template.md`\n\n**Related Commands**:\n- `flow-gate-check` - Quality gate validation\n- `flow-risk-management-cycle` - Risk assessment\n- `check-traceability` - Requirements coverage\n\n**Test Strategies**:\n- Test Pyramid (unit > integration > e2e)\n- Risk-Based Testing (prioritize by impact)\n- Shift-Left Testing (early detection)\n- Continuous Testing (automated pipeline)","> **Declarative Flow (#1539):** This flow's orchestration is now also expressed as a\n> declarative YAML Flow at `flows\u002Fflow-test-strategy-execution.playbook.yaml` (source of truth for the step\n> sequence + gates). This SKILL.md remains the discoverable trigger surface and prose\n> reference. See epic #1534.\n\n\u003C!-- AIWG-SKILL-CALLOUT -->\n> **Skill access pattern (post-kernel-pivot, 2026.5+)**\n>\n> Skill names referenced in this document are AIWG skills, **not slash commands**. Most are not kernel-listed and cannot be invoked as `\u002Fskill-name` by the platform. Reach them via:\n>\n> ```bash\n> aiwg discover \"\u003Ccapability>\"\n> aiwg show skill \u003Cname> --body\n> ```\n>\n> Only kernel-listed skills (`aiwg-doctor`, `aiwg-refresh`, `aiwg-status`, `aiwg-help`, `use`, `steward`) are directly invokable as slash commands. See [skill-discovery rule](https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Faddons\u002Faiwg-utils\u002Frules\u002Fskill-discovery.md).\n\n\n# Test Strategy Execution Flow\n\n**You are the Test Orchestrator** for comprehensive test strategy execution and quality validation.\n\n## Your Role\n\n**You orchestrate multi-agent test workflows. You do NOT execute bash scripts or run tests directly.**\n\nWhen the user requests this flow (via natural language or explicit command):\n\n1. **Interpret the request** and confirm understanding\n2. **Read this template** as your orchestration guide\n3. **Extract agent assignments** and workflow steps\n4. **Delegate agents with the current provider-native orchestration mechanism** in the correct sequence\n5. **Synthesize test results** and quality metrics\n6. **Report test execution status** with recommendations\n\n## Test Execution Overview\n\n**Purpose**: Execute comprehensive test strategy with multi-agent coordination\n\n**Key Activities**:\n- Test suite execution (unit, integration, e2e)\n- Coverage analysis and validation\n- Defect detection and triage\n- Regression analysis\n- Quality gate validation\n\n**Expected Duration**: 30-60 minutes orchestration (varies by test scope)\n\n## Natural Language Triggers\n\nUsers may say:\n- \"Run tests\"\n- \"Execute test suite\"\n- \"Validate tests\"\n- \"Test the system\"\n- \"Run unit tests\"\n- \"Execute integration tests\"\n- \"Run full regression\"\n- \"Check test coverage\"\n- \"Test this component\"\n\nYou recognize these as requests for this test orchestration flow.\n\n## Test Levels\n\n- **unit**: Execute unit tests for component or module\n- **integration**: Execute integration tests for service interactions\n- **e2e**: Execute end-to-end tests for user journeys\n- **regression**: Execute full regression suite\n- **performance**: Execute performance and load tests\n- **security**: Execute security test suite\n- **smoke**: Execute smoke tests (critical path validation)\n- **acceptance**: Execute user acceptance tests\n\n## Parameter Handling\n\n### --guidance Parameter\n\n**Purpose**: User provides upfront direction to tailor test execution priorities\n\n**Examples**:\n```\n--guidance \"Focus on security tests, OWASP Top 10 coverage critical\"\n--guidance \"Tight timeline, prioritize smoke tests over comprehensive coverage\"\n--guidance \"Performance is critical, need sub-100ms p95 validation\"\n--guidance \"New feature testing, focus on component X integration\"\n```\n\n**How to Apply**:\n- Parse guidance for keywords: security, performance, coverage, timeline, feature\n- Adjust test suite selection (prioritize relevant test types)\n- Modify coverage targets (minimal vs comprehensive based on timeline)\n- Influence defect triage severity (critical for security issues)\n\n### --interactive Parameter\n\n**Purpose**: You ask 6 strategic questions to understand test context\n\n**Questions to Ask** (if --interactive):\n\n```\nI'll ask 6 strategic questions to tailor test execution to your needs:\n\nQ1: What test levels are you targeting?\n    (unit, integration, e2e, regression, performance, security)\n\nQ2: What's your current test coverage?\n    (Helps me set realistic coverage improvement targets)\n\nQ3: What are your top quality concerns?\n    (Security, performance, functionality, usability)\n\nQ4: What's your test automation maturity?\n    (Manual, partial automation, fully automated)\n\nQ5: What's your acceptable test execution time?\n    (Minutes for CI\u002FCD, hours for nightly, days for release)\n\nQ6: What's your team's testing expertise?\n    (Helps determine level of detail in reports)\n\nBased on your answers, I'll adjust:\n- Test suite selection and execution order\n- Coverage targets and validation depth\n- Defect triage priorities\n- Report detail level\n```\n\n**Synthesize Guidance**: Combine answers into structured guidance string for execution\n\n## Artifacts to Generate\n\n**Primary Deliverables**:\n- **Test Execution Report**: Comprehensive results → `.aiwg\u002Ftesting\u002Ftest-execution-report.md`\n- **Coverage Report**: Code coverage analysis → `.aiwg\u002Ftesting\u002Fcoverage-report.md`\n- **Defect List**: Triaged defects by severity → `.aiwg\u002Ftesting\u002Fdefects\u002F`\n- **Regression Report**: New failures vs baseline → `.aiwg\u002Ftesting\u002Fregression-report.md`\n- **Quality Gate Report**: Pass\u002Ffail criteria → `.aiwg\u002Fgates\u002Ftest-quality-gate.md`\n\n**Supporting Artifacts**:\n- Test execution logs (archived)\n- Performance metrics (if applicable)\n- Security scan results (if applicable)\n\n## Multi-Agent Orchestration Workflow\n\n### Step 1: Test Execution Planning\n\n**Purpose**: Define test scope and execution strategy\n\n**Your Actions**:\n\n1. **Read Test Context**:\n   ```\n   Read and verify presence of:\n   - .aiwg\u002Ftesting\u002Fmaster-test-plan.md (if exists)\n   - .aiwg\u002Frequirements\u002Fuse-case-*.md\n   - .aiwg\u002Farchitecture\u002Fsoftware-architecture-doc.md\n   - Previous test results (if any)\n   ```\n\n2. **Launch Test Planning Agent**:\n   ```\n   Task(\n       subagent_type=\"test-architect\",\n       description=\"Plan test execution strategy\",\n       prompt=\"\"\"\n       Test level requested: {test-level}\n       Target component: {target-component}\n       Guidance: {guidance}\n\n       Read available test artifacts:\n       - Master Test Plan (if exists)\n       - Previous test results\n       - Architecture documentation\n\n       Create Test Execution Plan:\n       1. Test Scope\n          - Components to test\n          - Test types to execute\n          - Test suites to run\n\n       2. Execution Order\n          - Unit → Integration → E2E (typical)\n          - Or risk-based prioritization\n\n       3. Coverage Targets\n          - Line coverage: ≥80%\n          - Branch coverage: ≥75%\n          - Critical path coverage: 100%\n\n       4. Pass\u002FFail Criteria\n          - All tests pass\n          - Coverage thresholds met\n          - No P0\u002FP1 defects\n          - Performance within SLAs\n\n       5. Resource Requirements\n          - Test environments needed\n          - Test data requirements\n          - Tool requirements\n\n       Save to: .aiwg\u002Fworking\u002Ftest-execution\u002Ftest-execution-plan.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n✓ Initialized test execution planning\n⏳ Creating test execution strategy...\n✓ Test execution plan complete\n```\n\n### Step 2: Execute Unit Test Suite\n\n**Purpose**: Run unit tests with coverage analysis\n\n**Your Actions**:\n\n1. **Launch Unit Test Execution** (parallel agents if multiple components):\n   ```\n   Task(\n       subagent_type=\"test-engineer\",\n       description=\"Execute unit test suite\",\n       prompt=\"\"\"\n       Component: {target-component}\n       Coverage target: ≥80% line, ≥75% branch\n\n       Execute unit tests:\n       1. Identify test framework (Jest, Pytest, JUnit, etc.)\n       2. Run tests with coverage enabled\n       3. Collect results:\n          - Total tests\n          - Passed\u002FFailed\u002FSkipped\n          - Execution time\n          - Coverage metrics\n\n       4. Identify coverage gaps:\n          - Uncovered lines\n          - Uncovered branches\n          - Critical paths without tests\n\n       5. Document failures:\n          - Test name\n          - Failure reason\n          - Stack trace\n          - Component affected\n\n       Generate Unit Test Report:\n       - Test results summary\n       - Coverage analysis\n       - Failure details\n       - Recommendations\n\n       Save to: .aiwg\u002Fworking\u002Ftest-execution\u002Funit-test-results.md\n       \"\"\"\n   )\n   ```\n\n2. **Launch Coverage Analysis**:\n   ```\n   Task(\n       subagent_type=\"test-engineer\",\n       description=\"Analyze code coverage\",\n       prompt=\"\"\"\n       Read unit test results\n       Coverage data from test execution\n\n       Analyze coverage:\n       1. Overall Metrics\n          - Line coverage %\n          - Branch coverage %\n          - Function coverage %\n          - Statement coverage %\n\n       2. Coverage by Component\n          - Identify well-tested areas\n          - Identify gaps\n          - Critical path coverage\n\n       3. Coverage Trends\n          - Compare to baseline\n          - Improvement\u002Fdegradation\n\n       4. Recommendations\n          - Priority areas for new tests\n          - Acceptable uncovered code\n          - Technical debt items\n\n       Save to: .aiwg\u002Fworking\u002Ftest-execution\u002Fcoverage-analysis.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Executing unit tests...\n  ✓ Unit tests complete: 245 passed, 3 failed, 2 skipped\n  ✓ Coverage: 82% line, 76% branch (targets met)\n✓ Unit test execution complete\n```\n\n### Step 3: Execute Integration Test Suite\n\n**Purpose**: Test service interactions and data flows\n\n**Your Actions**:\n\n```\nTask(\n    subagent_type=\"test-engineer\",\n    description=\"Execute integration tests\",\n    prompt=\"\"\"\n    Scope: Service interactions, API contracts, database operations\n\n    Execute integration tests:\n    1. Test Categories\n       - API endpoint tests\n       - Database integration\n       - External service mocks\n       - Message queue interactions\n\n    2. Validate\n       - Data contracts (request\u002Fresponse schemas)\n       - Error handling (4xx, 5xx responses)\n       - Transaction boundaries\n       - Service dependencies\n\n    3. Collect Metrics\n       - API coverage %\n       - Response times\n       - Error rates\n       - Data consistency\n\n    4. Document Issues\n       - Contract violations\n       - Performance bottlenecks\n       - Integration failures\n       - Configuration issues\n\n    Generate Integration Test Report:\n    - Results by service\u002FAPI\n    - Contract validation\n    - Performance metrics\n    - Integration health\n\n    Save to: .aiwg\u002Fworking\u002Ftest-execution\u002Fintegration-test-results.md\n    \"\"\"\n)\n```\n\n**Communicate Progress**:\n```\n⏳ Executing integration tests...\n  ✓ API tests: 45\u002F48 passed\n  ✓ Database tests: 22\u002F22 passed\n  ✓ External service tests: 15\u002F16 passed\n✓ Integration test execution complete\n```\n\n### Step 4: Execute E2E and Acceptance Tests\n\n**Purpose**: Validate complete user journeys and business logic\n\n**Your Actions**:\n\n1. **Launch E2E Test Execution**:\n   ```\n   Task(\n       subagent_type=\"qa-engineer\",\n       description=\"Execute end-to-end tests\",\n       prompt=\"\"\"\n       Execute E2E test suites:\n\n       1. Critical User Journeys\n          - User registration\u002Flogin\n          - Core business workflows\n          - Payment\u002Fcheckout (if applicable)\n          - Data export\u002Fimport\n\n       2. Cross-browser Testing\n          - Chrome, Firefox, Safari\n          - Mobile responsive\n\n       3. Test Execution\n          - Setup test data\n          - Execute test scenarios\n          - Capture screenshots on failure\n          - Record execution videos\n\n       4. Results Collection\n          - Journey completion rates\n          - Step-level pass\u002Ffail\n          - Performance metrics\n          - UI\u002FUX issues\n\n       Document:\n       - Critical path coverage\n       - Failed journeys\n       - Performance bottlenecks\n       - Accessibility issues\n\n       Save to: .aiwg\u002Fworking\u002Ftest-execution\u002Fe2e-test-results.md\n       \"\"\"\n   )\n   ```\n\n2. **Launch UAT Validation** (if acceptance level):\n   ```\n   Task(\n       subagent_type=\"product-owner\",\n       description=\"Validate acceptance criteria\",\n       prompt=\"\"\"\n       Read use case specifications\n       Read e2e test results\n\n       Validate:\n       1. Use case coverage\n          - All use cases tested\n          - Acceptance criteria met\n          - Business rules validated\n\n       2. User Experience\n          - Workflow efficiency\n          - Error messaging\n          - Help\u002Fdocumentation\n\n       3. Business Logic\n          - Calculations correct\n          - Rules properly enforced\n          - Edge cases handled\n\n       Acceptance Decision:\n       - ACCEPTED: Ready for production\n       - CONDITIONAL: Minor issues, can proceed\n       - REJECTED: Major issues, must fix\n\n       Save to: .aiwg\u002Fworking\u002Ftest-execution\u002Fuat-validation.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Executing E2E tests...\n  ✓ Critical journeys: 8\u002F10 passed\n  ✓ Cross-browser: All passed\n  ✓ UAT validation: CONDITIONAL (2 minor issues)\n✓ E2E test execution complete\n```\n\n### Step 5: Defect Triage and Root Cause Analysis\n\n**Purpose**: Analyze failures and assign severity\n\n**Your Actions**:\n\n1. **Collect All Test Failures**:\n   ```\n   Read all test results:\n   - Unit test failures\n   - Integration test failures\n   - E2E test failures\n   ```\n\n2. **Launch Defect Triage** (parallel agents for different severities):\n   ```\n   # QA Lead for overall triage\n   Task(\n       subagent_type=\"qa-lead\",\n       description=\"Triage all test failures\",\n       prompt=\"\"\"\n       Read all test failure reports\n\n       For each failure:\n       1. Assign Severity\n          - P0 (Critical): System down, data loss, security breach\n          - P1 (High): Major feature broken, significant impact\n          - P2 (Medium): Minor feature issue, workaround exists\n          - P3 (Low): Cosmetic, minimal impact\n\n       2. Categorize\n          - Functional bug\n          - Performance issue\n          - Security vulnerability\n          - Usability problem\n          - Test issue (false positive)\n\n       3. Assign Owner\n          - Component team\n          - Specific developer (if known)\n          - Priority queue\n\n       4. Set Resolution Target\n          - P0: 4 hours\n          - P1: 24 hours\n          - P2: 3 days\n          - P3: Next iteration\n\n       Create defect cards for each issue:\n       - Defect ID\n       - Title and description\n       - Severity and category\n       - Steps to reproduce\n       - Expected vs actual\n       - Owner and due date\n\n       Save to: .aiwg\u002Fworking\u002Ftest-execution\u002Fdefects\u002F\n       \"\"\"\n   )\n\n   # Component Owner for root cause\n   Task(\n       subagent_type=\"component-owner\",\n       description=\"Root cause analysis for P0\u002FP1 defects\",\n       prompt=\"\"\"\n       Analyze high-severity defects:\n\n       For each P0\u002FP1 defect:\n       1. Root Cause Analysis\n          - Code defect\n          - Configuration issue\n          - Environment problem\n          - Test data issue\n          - External dependency\n\n       2. Impact Analysis\n          - Affected components\n          - User impact\n          - Data integrity risk\n          - Performance impact\n\n       3. Fix Strategy\n          - Quick fix available?\n          - Full fix timeline\n          - Workaround options\n          - Rollback needed?\n\n       Document root cause analysis\n       Save to: .aiwg\u002Fworking\u002Ftest-execution\u002Froot-cause-analysis.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Triaging test failures...\n  ✓ Total defects: 11\n  ✓ P0 (Critical): 0\n  ✓ P1 (High): 2 (assigned, 24hr fix)\n  ✓ P2 (Medium): 6\n  ✓ P3 (Low): 3\n✓ Defect triage complete\n```\n\n### Step 6: Regression Analysis and Reporting\n\n**Purpose**: Compare to baseline and generate final report\n\n**Your Actions**:\n\n1. **Launch Regression Analysis**:\n   ```\n   Task(\n       subagent_type=\"test-architect\",\n       description=\"Analyze regression vs baseline\",\n       prompt=\"\"\"\n       Read current test results\n       Read baseline results (previous release\u002Fiteration)\n\n       Regression Analysis:\n       1. New Failures\n          - Tests that passed before, fail now\n          - Root cause (code change, environment)\n          - Severity of regression\n\n       2. Fixed Tests\n          - Previously failing, now passing\n          - Verify fix is intentional\n\n       3. Test Health Metrics\n          - Flaky test rate (intermittent failures)\n          - Test execution time trends\n          - Coverage trends\n\n       4. Quality Trends\n          - Defect discovery rate\n          - Defect escape rate\n          - Test effectiveness\n\n       Generate Regression Report:\n       - New regressions (must fix)\n       - Improvements (fixes verified)\n       - Test health status\n       - Quality metrics\n\n       Save to: .aiwg\u002Fworking\u002Ftest-execution\u002Fregression-analysis.md\n       \"\"\"\n   )\n   ```\n\n2. **Generate Comprehensive Test Report**:\n   ```\n   Task(\n       subagent_type=\"test-manager\",\n       description=\"Generate test execution report\",\n       prompt=\"\"\"\n       Synthesize all test results:\n       - Unit test results\n       - Integration test results\n       - E2E test results\n       - UAT validation\n       - Defect list\n       - Regression analysis\n\n       Create Test Execution Report:\n\n       # Test Execution Report - {test-level}\n\n       ## Executive Summary\n       - Overall Status: PASS | FAIL | CONDITIONAL\n       - Go\u002FNo-Go: {recommendation}\n       - Critical Issues: {list}\n\n       ## Test Results by Level\n\n       ### Unit Tests\n       - Tests Run: {count}\n       - Pass Rate: {percentage}%\n       - Coverage: {line}% line, {branch}% branch\n       - Execution Time: {duration}\n\n       ### Integration Tests\n       - Tests Run: {count}\n       - Pass Rate: {percentage}%\n       - API Coverage: {percentage}%\n       - Performance: p95 {latency}ms\n\n       ### E2E Tests\n       - Journeys Tested: {count}\n       - Pass Rate: {percentage}%\n       - Critical Paths: {status}\n       - Browser Coverage: {list}\n\n       ## Coverage Analysis\n       - Line Coverage: {current}% (target: {target}%)\n       - Branch Coverage: {current}% (target: {target}%)\n       - Uncovered Critical Paths: {list or none}\n\n       ## Defect Summary\n       - P0 (Critical): {count}\n       - P1 (High): {count}\n       - P2 (Medium): {count}\n       - P3 (Low): {count}\n\n       Top Issues:\n       {list with severity and owner}\n\n       ## Regression Status\n       - New Regressions: {count}\n       - Fixed Since Baseline: {count}\n       - Flaky Test Rate: {percentage}%\n\n       ## Quality Gates\n       - Unit Test Gate: {PASS | FAIL}\n       - Integration Gate: {PASS | FAIL}\n       - E2E Gate: {PASS | FAIL}\n       - Coverage Gate: {PASS | FAIL}\n       - Defect Gate: {PASS | FAIL}\n\n       ## Recommendations\n       {specific actions based on results}\n\n       ## Next Steps\n       1. {action 1}\n       2. {action 2}\n       3. {action 3}\n\n       Save to: .aiwg\u002Ftesting\u002Ftest-execution-report.md\n       \"\"\"\n   )\n   ```\n\n3. **Generate Quality Gate Report**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Validate quality gates\",\n       prompt=\"\"\"\n       Read test execution report\n       Read quality gate criteria\n\n       Validate Gates:\n       1. Test Pass Rate\n          - Criteria: ≥95% pass rate\n          - Result: {actual}%\n          - Status: PASS | FAIL\n\n       2. Coverage Thresholds\n          - Criteria: ≥80% line, ≥75% branch\n          - Result: {line}% line, {branch}% branch\n          - Status: PASS | FAIL\n\n       3. Critical Defects\n          - Criteria: 0 P0, ≤2 P1\n          - Result: {P0} P0, {P1} P1\n          - Status: PASS | FAIL\n\n       4. Performance SLAs\n          - Criteria: p95 \u003C 500ms\n          - Result: p95 = {actual}ms\n          - Status: PASS | FAIL\n\n       Overall Gate Decision:\n       - PASS: All criteria met\n       - CONDITIONAL: Minor gaps, can proceed with plan\n       - FAIL: Major gaps, must fix before proceeding\n\n       Save to: .aiwg\u002Fgates\u002Ftest-quality-gate.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Generating test reports...\n  ✓ Regression analysis complete\n  ✓ Test execution report generated\n  ✓ Quality gate validation complete\n✓ Test reporting complete\n```\n\n### Step 7: Present Results and Recommendations\n\n**Purpose**: Summarize results for user decision\n\n**Your Actions**:\n\n```\nRead final reports and present summary:\n\n─────────────────────────────────────────────\nTest Execution Summary\n─────────────────────────────────────────────\n\n**Test Level**: {test-level}\n**Component**: {target-component}\n**Status**: {PASS | FAIL | CONDITIONAL}\n\n**Test Results**:\n✓ Unit Tests: 245\u002F248 passed (98.8%)\n  Coverage: 82% line, 76% branch\n⚠ Integration Tests: 82\u002F86 passed (95.3%)\n  3 API contract issues, 1 timeout\n✓ E2E Tests: 8\u002F10 critical paths passed (80%)\n  2 non-critical UI issues\n\n**Defect Summary**:\n- P0 (Critical): 0\n- P1 (High): 2 (fix in progress)\n- P2 (Medium): 6 (scheduled)\n- P3 (Low): 3 (backlog)\n\n**Quality Gates**:\n✓ Test Pass Rate: PASS (96% > 95%)\n✓ Coverage: PASS (82% > 80%)\n⚠ Critical Defects: CONDITIONAL (2 P1s)\n✓ Performance: PASS (p95 = 287ms)\n\n**Overall Decision**: CONDITIONAL PASS\n- Can proceed with P1 fixes in parallel\n- Must resolve before production deployment\n\n**Recommendations**:\n1. Fix 2 P1 defects within 24 hours\n2. Add tests for uncovered critical path in auth module\n3. Investigate flaky integration test (payment service)\n4. Schedule P2 fixes for next iteration\n\n**Artifacts Generated**:\n- Test Execution Report: .aiwg\u002Ftesting\u002Ftest-execution-report.md\n- Coverage Report: .aiwg\u002Ftesting\u002Fcoverage-report.md\n- Defect List: .aiwg\u002Ftesting\u002Fdefects\u002F (11 files)\n- Regression Report: .aiwg\u002Ftesting\u002Fregression-report.md\n- Quality Gate Report: .aiwg\u002Fgates\u002Ftest-quality-gate.md\n\n─────────────────────────────────────────────\n```\n\n## Quality Gates\n\nBefore marking workflow complete, verify:\n- [ ] Test execution plan created and approved\n- [ ] All requested test suites executed\n- [ ] Coverage analysis completed\n- [ ] Defects triaged by severity\n- [ ] Regression analysis completed\n- [ ] Test reports generated\n- [ ] Quality gates validated\n\n## User Communication\n\n**At start**: Confirm understanding and test scope\n\n```\nUnderstood. I'll orchestrate test execution for {test-level} testing.\n\nTarget: {target-component}\nScope: {test types to run}\n\nThis will:\n- Execute relevant test suites\n- Analyze code coverage\n- Triage any failures\n- Compare to baseline\n- Generate comprehensive reports\n\nExpected duration: 30-60 minutes.\n\nStarting test orchestration...\n```\n\n**During**: Progress indicators\n\n```\n✓ = Complete\n⏳ = In progress\n❌ = Failed\n⚠️ = Warning\u002Fissues found\n```\n\n**At end**: Summary with recommendations (see Step 7)\n\n## Error Handling\n\n**Test Environment Unavailable**:\n```\n❌ Test environment not accessible\n\nIssue: {environment} is down\u002Funreachable\nImpact: Cannot execute {test-type} tests\n\nActions:\n1. Check environment status\n2. Restart services if needed\n3. Use alternate environment\n4. Or defer testing with risk acknowledgment\n\nEscalating to DevOps team...\n```\n\n**Coverage Below Threshold**:\n```\n⚠️ Coverage below target\n\nCurrent: {actual}% line coverage\nTarget: {threshold}%\nGap: {delta}%\n\nUncovered areas:\n- {component}: {coverage}%\n- {component}: {coverage}%\n\nRecommendation: Add tests before proceeding\nOr: Accept technical debt with plan\n```\n\n**Critical Defects Found**:\n```\n❌ Critical defects blocking release\n\nP0 Defects: {count}\n- {defect-1}: {description}\n- {defect-2}: {description}\n\nP1 Defects: {count}\n- {list}\n\nDecision: NO-GO for release\nAction: Fix P0\u002FP1 defects before proceeding\n```\n\n## Success Criteria\n\nThis orchestration succeeds when:\n- [ ] Test execution completed for requested level\n- [ ] Coverage thresholds met or gap acknowledged\n- [ ] All failures documented and triaged\n- [ ] Regression analysis completed\n- [ ] Quality gates evaluated\n- [ ] Clear go\u002Fno-go recommendation provided\n- [ ] All artifacts saved to .aiwg\u002Ftesting\u002F\n\n## References\n\n**Templates** (via $AIWG_ROOT):\n- Master Test Plan: `templates\u002Ftest\u002Fmaster-test-plan-template.md`\n- Test Case: `templates\u002Ftest\u002Ftest-case-card.md`\n- Use Case Test: `templates\u002Ftest\u002Fuse-case-test-card.md`\n- Defect Card: `templates\u002Ftest\u002Fdefect-card.md`\n- Test Evaluation: `templates\u002Ftest\u002Ftest-evaluation-summary-template.md`\n\n**Related Commands**:\n- `flow-gate-check` - Quality gate validation\n- `flow-risk-management-cycle` - Risk assessment\n- `check-traceability` - Requirements coverage\n\n**Test Strategies**:\n- Test Pyramid (unit > integration > e2e)\n- Risk-Based Testing (prioritize by impact)\n- Shift-Left Testing (early detection)\n- Continuous Testing (automated pipeline)",{"name":5,"namespace":58,"platforms":59,"commandHint":61,"description":7},"aiwg",[60],"all",{"model":34,"category":62,"modelRole":44,"modelTier":63,"allowedTools":64,"argumentHint":65,"orchestration":66},"sdlc-orchestration","standard","Task, Read, Write, Glob, TodoWrite","\u003Ctest-level> [target-component] [project-directory] [--guidance \"text\"] [--interactive]",true,"main","6754967c344ccb087a8de06972f55a41067b291b","agentic\u002Fcode\u002Fplugins\u002Fcodex-sdlc\u002Fskills\u002Fflow-test-strategy-execution",36,"https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg","https:\u002F\u002Faiwg.io","https:\u002F\u002Fgithub.com\u002Fjmagly","https:\u002F\u002Fintegrolabs.io","ml\u002Fai, industrial automation, safety\u002Fsecurity, ssi\r\n\r\nmagly.net\r\nintegrolabs.io\r\naiwg.io\r\nfortemi.com\r\npagenary.com\r\nbytecask.com","2026-11-11 08:11:25",{"source":8,"skillName":5,"commands":78,"prompt":88,"zipAvailable":66},[79,82,85],{"tool":80,"command":81},"npx","npx skills add jmagly\u002Faiwg --skill flow-test-strategy-execution",{"tool":83,"command":84},"bunx","bunx skills add jmagly\u002Faiwg --skill flow-test-strategy-execution",{"tool":86,"command":87},"pnpm","pnpm dlx skills add jmagly\u002Faiwg --skill flow-test-strategy-execution","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fcodex-sdlc\u002Fskills\u002Fflow-test-strategy-execution\u002FSKILL.md",[],[91,118,140,146,153,167],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":98,"publishedAt":53},"01M70QA0BSYJ49EES9V4RE8QH1","host-hardening","Read-only system hardening baseline and plan-first host hardening recommendations for SSH, Docker bind addresses, firewall persistence, datastores, exporters and audit retention.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[97],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[99,100,101,33,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117],"host","host hardening","hardening","re","recommendations","remediation","plan","port","verification","Bash","access","only","retention","audit","never","firewall","bind","secrets","request",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":128,"publishedAt":53},"01M70PNT2Z4HMZPRBTAF6073NN","exposure-analysis","Read-only firewall analysis and effective host exposure reconstruction for Docker published ports, UFW bypass, stale rules, CDN scope, IPv6 asymmetry and external probe allowlists.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fforensics\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[124,127],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[129,47,130,33,131,106,132,133,108,134,99,135,110,136,137,113,114,138,139,42],"exposure analysis","unknown","credentials","collection","ufw","ports","internet","local","scope","reconstruction","operator",{"skillNo":141,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":145,"publishedAt":53},"01M70P8QATMPKA78E4FT5D2TNA","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[144],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[101,99,100,109,33,117,104,103,112,105,106,107,108,116,110,111,102,113,114,115],{"skillNo":147,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":152,"publishedAt":53},"01M70NMPVJ5H0JH131P60FW4R8","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[150,151],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[47,129,113,131,106,132,108,130,99,135,110,136,137,33,114,134,133,138,139,42],{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":160,"publishedAt":53},"01M6CB4DDR0B4NNCFK7ZK7449H","fixture-skill","Exercise rule delivery.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Frule-delivery\u002Fskills\u002Ffixture-skill\u002FSKILL.md",[159],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[161,162,163,164,165,166],"fixture skill","fixture","rule","delivery","true","exercise",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":174,"publishedAt":53},"01M6CB4AVK1W76MFMPP0JP32CJ","pi-local","Pi-local duplicate-precedence fixture.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fproviders\u002Fpi\u002Fproject\u002F.pi\u002Fskills\u002Fpi-local\u002FSKILL.md",[173],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[175,176,136,177,162],"pi","pi local","duplicate"]