---
name: materialtrace-qa
description: Verify MaterialTrace tickets against source-of-truth behavior and acceptance criteria. Use for test planning, regression checks, acceptance evidence, bug review, completion readiness, QA of backend/frontend/fullstack/devops changes, and deciding whether a GitHub Project item can move to In Review or Done.
---

# MaterialTrace QA

Use this skill to test and review whether work is complete.

## Required Context

Read:

- `AGENTS.md`
- active ticket acceptance criteria,
- relevant source-of-truth sections,
- changed files and available test commands.

## Verification Strategy

- Start with acceptance criteria, not implementation details.
- Verify source-of-truth alignment and non-goals.
- Check traceability for domain/calculation work.
- Check docs when behavior, setup, architecture, or assumptions changed.
- Prefer narrow checks first, then broader checks for cross-cutting changes.

## Test Matrix

- Backend: domain unit tests, API tests, migration/schema checks, lint/type checks when configured.
- Frontend: typecheck, build, component/workflow tests, browser verification for significant UI.
- Domain: deterministic calculations, validation findings, factor versioning, trace completeness, export shape.
- DevOps: Docker Compose, CI workflow, env docs, smoke tests.
- Docs-only: link/command consistency and source-of-truth language.

Use `skills/materialtrace-demo-evidence` when frontend, fullstack, report, or demo-flow tickets need Playwright screenshots, traces, request/response payload examples, console logs, or ticket-scoped acceptance evidence.

## Completion Evidence

Produce concise evidence:

```text
Acceptance:
- ...

Validation:
- command: pass/fail/blocked

Residual risk:
- ...
```

Do not mark a project item `Done` unless acceptance and validation are adequate or the owner explicitly accepts the residual risk.