Build-an-X workflow that drafts a QA team's quarterly OKR set - one to three Objectives, each with 3 - 5 measurable Key Results - from the team's current state (risk matrix, defect-trend narrative, test-run history, test-pyramid balance, compliance coverage). Every numeric target cites its source artifact (e.g., a defect-trend baseline's 2026-Q1 escape rate). QA-specific by design - generic OKR generators (Tability, Asana, ClickUp) don't know test metrics; the differentiation is the domain. Produces the OKR set itself - not the test-strategy document it sits inside, and not the risk-score calibration behind the baselines. Use at the start of each quarter to draft the OKR set the manager edits and the team commits to.
75
94%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Deep reference for the qa-okr-author SKILL.md, Step 2. Five canonical QA Objective shapes (catalog, not prescription). Each maps to a measurable KR family with its baseline source. The manager picks 1 - 3; the skill drafts the KRs. Other Objective shapes are valid; these are the most-cited in QA-manager-facing literature.
Anchored on test-pyramid-balancer. Used when the suite is E2E-heavy and shifting weight downward improves cycle time + maintainability.
| KR axis | Example KR | Baseline source |
|---|---|---|
| Layer ratio | unit:integration:E2E reaches 70:20:10 | current ratio per test-pyramid-balancer |
| Cycle time | regression suite duration < 45 min per shard | current per test-run-summary-author |
| E2E suite budget | E2E test count ≤ 200, growth rate ≤ 5/quarter | e2e-suite-budget |
Anchored on the defect-trend baseline. Used when production defects are above the team's tolerance.
| KR axis | Example KR | Baseline source |
|---|---|---|
| Volume | P1 escapes < 2/quarter; P2 escapes < 10/quarter | current per the defect-trend quarterly report |
| Time-to-detect | MTTD on P1 < 4 hours | per mttr-mtbf-tracker |
| Category-specific | regression-class escapes -50% WoW | per defect clustering + the defect-trend report |
Anchored on test-run-summary-author. Used when CI is the bottleneck.
| KR axis | Example KR | Baseline source |
|---|---|---|
| Wall-clock | regression suite < 60 min per shard, 4× parallel | test-run-summary-author |
| Parallelisation | sharding factor ≥ 8 with no shard >90 min | CI config + test-run-summary-author |
| CI cost | per-PR CI cost -30% via TIA | regression-suite-selector |
Anchored on flake-detection + flaky-test-quarantine. Used when flake rate is above the team's tolerance (below 5% flake rate is aspirational, under 10% a reasonable committed bar; Google Testing Blog).
| KR axis | Example KR | Baseline source |
|---|---|---|
| Quarantine ceiling | quarantine list ≤ 5 at any point | current per flaky-test-quarantine |
| Flake rate | flake rate < 3% of CI runs (vs 8% current baseline) | per the flake-detection weekly history |
| Repair velocity | mean time-to-repair on quarantined test < 5 days | per flaky-test-quarantine |
Anchored on compliance-readiness review. Used in regulated industries (healthcare, finance, automotive).
| KR axis | Example KR | Baseline source |
|---|---|---|
| Per-control coverage | SOC 2 Trust Service Criteria coverage ≥ 95% | the compliance-readiness review |
| Evidence freshness | every control's evidence ≤ 90 days old | soc2-evidence-collector |
| Audit pass-rate | external audit findings ≤ 3, no high-severity | prior audit history |