| name | zephyr-coverage-analysis |
| description | Analyze Zephyr test case coverage for a Jira user story and produce a QE management report with metrics, risk scoring, and prioritized recommendations. |
| metadata | {"triggers":{"keywords":["zephyr coverage analysis","workflow"]}} |
Zephyr Coverage Analysis Skill
[!IMPORTANT]
Analyze Zephyr test case coverage for a Jira user story and produce a QE management report with metrics, risk scoring, and prioritized recommendations.
Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false, profile=business|hybrid|technical.
Instructions
When the user asks to perform this workflow, execute the following steps:
Read-only audit — produces coverage_analysis_report.md, does NOT create or modify Zephyr test cases
// turbo-all
1. Gather Input
If the Jira Issue Key is not provided, ask for it.
Optional: Scope (single ticket default, or comma-separated epic/sprint keys) | Depth (quick = coverage table only, full = default with risk scoring + QE observations).
2. Fetch Jira + Discover Zephyr TCs (Parallel Sub-Agents)
Launch two sub-agents in parallel to keep raw API data out of main context:
Sub-Agent A: Jira Analyst
Use Agent tool with subagent_type="jira-analyst".
Prompt: "Fetch JIRA ticket {ISSUE_KEY} with ?expand=renderedFields. Extract: Summary, Status, Components, Labels, Market, and the full AC table. For each AC row, read the Platform column from rendered HTML — color codes are authoritative: = Web, = Mobile, = Web+Mobile. Do NOT use ticket-level Platform — always read per-row from renderedFields. Return structured briefing."
