---
name: openqa-acceptance-report
description: Write an inspectable software-change acceptance report in Markdown. Local only. No SaaS.
license: Apache-2.0
---

# OpenQA Acceptance Report

Write a change-acceptance record that another engineer can audit without talking to you.

## Goal

Turn a verification run into a durable Markdown asset. The report is the product.

## File

If the user does not specify a path, write:

`docs/qa/acceptance/<date>-<short-change-id>.md`

Never overwrite an existing report. Create a new file.

## Template

```markdown
# Acceptance Record

- Change: <PR, commit or branch>
- Date: <ISO date>
- Verifier: <agent or person>
- Decision: merge | review | block

## Intent

## Change

## Verification

## Evidence

## Risk

## Decision
```

## Rules

- Every claim in Evidence must point to a command, log, screenshot or test name.
- If a check was skipped, list it under Risk, not Evidence.
- Decision must be one of: merge, review, block.
- Keep the report short enough to read in five minutes.
- Do not invent metrics, pass rates or coverage percentages.
- Do not call OpenQA SaaS. This skill only writes local Markdown.