QA from a blueprint

Turn the supplied blueprint into executable scenario checks. Verify its expected behavior and the sufficiency of applicable unit and integration tests. Return evidence and exact issues the caller can reproduce and retest.

Inputs and authority

Use the blueprint or an equivalent explicit scenario set, repository revisions, service and fixture context, test commands, and an artifact destination outside application source. Preserve accepted expectations. Read input-and-report.md for input details and the output contract.

Discover missing facts from repository instructions, tests and scripts. Ask the caller only for unresolved information that changes expected behavior or prevents execution. In unattended use, record those blockers and finish with an incomplete report.

Keep application source unchanged. Create or repair generated tests and isolated fixtures in the artifact destination. Return application defects and missing repository tests to the caller for implementation. Preserve unexpected source changes for reconciliation; invalidate affected evidence instead of resetting them. Repository adoption of generated tests belongs to the caller.

The caller controls agent selection, environments, execution budgets and follow-up actions. The skill produces QA evidence; it does not publish or merge changes.

Procedure

1. Account for every scenario

Read every Happy path, Edge case and Failure scenario, plus acceptance criteria and TDD seams. Preserve Setup, Action and Expected outcomes. Keep supplied IDs; otherwise assign section-and-ordinal IDs without editing the blueprint. Record its identity, repository revisions and initial source state.