auditor-responsabilidades

Run the readiness gate: recover the contract (INTENT, scope, Definition of Done), map responsibilities with RACI, reconcile authorized versus touched scope, verify every PENDING obligation is closed with evidence, and confirm each cited artifact exists. The audit ends in an explicit verdict with named owners.

QA testing proves the product works by executing test batteries; a process audit verifies the delivery followed the rules — authorization, scope, evidence, traceability. This Skill audits the process and consumes QA and test reports as evidence, but never executes the product tests itself.

No. External or irreversible actions such as publishing, deploying, or sending data require a prior verifiable AUTH record citing the exact request, target, environment, and limits. Retroactive regularization is prohibited, and missing authorization is a blocking non-conformity.

Self-assessment answers can be produced without doing any work, so they prove nothing. The audit demands forced facts instead: command outputs, git diffs, file contents, and test counts that only exist if the verification actually ran.

Out-of-scope changes are recorded as surprises with impact, owner, and routing to the decision-maker — never silently corrected or retroactively approved. Unauthorized scope expansion is a blocking non-conformity regardless of intent.

Do not use it to build solutions, execute product test batteries, or compare and rank alternative versions. Those belong to the implementation lenses, the real-tester skill, and the judges panel respectively; this Skill only audits process compliance and issues verdicts.