Zephyr Coverage Analysis
Priority: P1 (HIGH)
Workflow
CRITICAL — Read and follow workflow file exactly. NOT implement from memory or from this description. Implementing inline bypasses
jira-analystandzephyr-scannersub-agents.
Read and execute .agents/workflows/zephyr-coverage-analysis.md.
Anti-Patterns
- No TC creation: Analysis read-only — call quality-engineering-zephyr-test-generation to create TCs.
- No pagination-first: Always use
Get Issue Link Test Cases(direct lookup) before falling back to pagination. - No ticket-level platform: Read Platform from each AC table row HTML, not ticket header section.
- No merged WEB+MOBILE slots: Treat each platform as independent coverage slot — Mobile covered ≠ Web covered.
- No skipping QE debt: Scan beyond AC rows — always include data correctness, negative flows, role differentiation, and regression risk in Section 4.
References
- Report Template — load when building coverage_analysis_report.md (Step 5 of workflow)
- Impact Analysis Protocol — TC discovery protocol
- Zephyr Test Generation — invoke after analysis to create missing TCs
Source: HoangNguyen0403/agent-skills-standard — distributed by TomeVault.