draft-test-status-brief

name	draft-test-status-brief
description	Draft an as-of QA status brief from approved execution, defect, plan, and risk snapshots. Use for daily or weekly testing updates, standups, sprint reports, stakeholder summaries, and comparisons with a prior status snapshot. Reports sourced progress, changes, blockers, risks, and next actions without logging test outcomes, filling missing metrics, closing a cycle, or making a release decision.
license	MIT
metadata	{"author":"TheTestingAcademy","category":"Test Deliverables","version":"1.0.0"}

Draft Test Status Brief

Turn existing QA records into a time-bounded communication. Keep source freshness and metric denominators visible so readers can distinguish current facts from unknowns.

Workflow

1. Record the brief ID, reporting period, audience, scope, release or build, environment, and as-of time with timezone.
2. Inventory the approved source snapshots with URI or path, version, snapshot time, and access state. Flag stale, partial, conflicting, or inaccessible sources.
3. Copy or calculate metrics only from sourced counts. Show numerator, denominator, formula, and scope; keep unreported cases unknown or not run according to the source.
4. Compare with a prior snapshot only when scope, denominator, build, and status definitions are compatible. Otherwise state that no valid trend is available.
5. Summarize verified progress, new and resolved blockers, changed risks, and next actions. Attribute owners and dates only when the source states them.
6. HUMAN REVIEW GATE: present the draft to the QA lead or status owner. Require confirmation of facts, audience, redactions, and distribution before publication.