CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/qa-okr-author

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

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

okr-shape-catalog.mdreferences/

QA-OKR shape catalog

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.

Shape 1 - Strengthen the test pyramid

Anchored on test-pyramid-balancer. Used when the suite is E2E-heavy and shifting weight downward improves cycle time + maintainability.

KR axisExample KRBaseline source
Layer ratiounit:integration:E2E reaches 70:20:10current ratio per test-pyramid-balancer
Cycle timeregression suite duration < 45 min per shardcurrent per test-run-summary-author
E2E suite budgetE2E test count ≤ 200, growth rate ≤ 5/quartere2e-suite-budget

Shape 2 - Reduce escape-defect rate

Anchored on the defect-trend baseline. Used when production defects are above the team's tolerance.

KR axisExample KRBaseline source
VolumeP1 escapes < 2/quarter; P2 escapes < 10/quartercurrent per the defect-trend quarterly report
Time-to-detectMTTD on P1 < 4 hoursper mttr-mtbf-tracker
Category-specificregression-class escapes -50% WoWper defect clustering + the defect-trend report

Shape 3 - Cut regression cycle time

Anchored on test-run-summary-author. Used when CI is the bottleneck.

KR axisExample KRBaseline source
Wall-clockregression suite < 60 min per shard, 4× paralleltest-run-summary-author
Parallelisationsharding factor ≥ 8 with no shard >90 minCI config + test-run-summary-author
CI costper-PR CI cost -30% via TIAregression-suite-selector

Shape 4 - Reduce flake-budget consumption

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 axisExample KRBaseline source
Quarantine ceilingquarantine list ≤ 5 at any pointcurrent per flaky-test-quarantine
Flake rateflake rate < 3% of CI runs (vs 8% current baseline)per the flake-detection weekly history
Repair velocitymean time-to-repair on quarantined test < 5 daysper flaky-test-quarantine

Shape 5 - Close compliance evidence gaps

Anchored on compliance-readiness review. Used in regulated industries (healthcare, finance, automotive).

KR axisExample KRBaseline source
Per-control coverageSOC 2 Trust Service Criteria coverage ≥ 95%the compliance-readiness review
Evidence freshnessevery control's evidence ≤ 90 days oldsoc2-evidence-collector
Audit pass-rateexternal audit findings ≤ 3, no high-severityprior audit history

SKILL.md

tile.json