agf-writing-qa-report

# Writing a QA Report (E2E / UAT) Use this skill when: - E2E execution is complete and a report needs publishing - UAT business sign-off needs to be captured - A bug-fix E2E re-verification needs recording (always **appended** as `## Re-run [N] — [date]` to the existing `[feature]-e2e-[YYYY-MM-DD].md`; never a new file — see "File path & naming" below) **Pair with**: - `agf-running-sit-tests` skill — SIT 由 dev 自跑，本 skill 不覆盖 SIT 报告（SIT 证据已在 `progress/<role>.md` 的 `**SIT 证据**` 段，归档随 `docs/qa/<feature>-process-log.md` 走） - **UAT 用例文档** `docs/qa/[feature]-uat-cases-[date].md`（模板 `docs/qa/uat-cases-_TEMPLATE.md`，gate SSOT 见 `testing.md`「UAT 用例文档」节）— UAT 执行前生成 + 用户审核 `status: Approved`；执行证据回填用例文档（证据 SSOT），**UAT 报告引用用例 ID，不重复粘贴证据** - This skill — covers the **E2E / UAT artifact** (report file) format ## File path & naming `docs/qa/[feature-kebab-case]-[stage]-[YYYY-MM-DD].md` — Stage ∈ `{e2e, uat}`. Examples: - `docs/qa/oauth-login-e2e-2026-05-13.md` - `docs/qa/oauth-login-uat-2026-05-15.md` **One report per stage per feature.** Re-runs after defect fix → append a new `## Re-run [N] — [date]` section to the same file, do not create a new file. ## Required sections (in order) ```markdown --- # frontmatter 是 verdict 数据��唯一 SSOT（agf-verdict.py 解析；validate-verdict hook 校客观底线、agf-matrix.sh fan-in 都读这里） feature: [feature-slug] date: YYYY-MM-DD tester: qa-engineer stage: E2E # E2E | UAT report_verdict: Promote # Promote | Conditional promote | Block crit...