verify-product-outcomes
Installation
SKILL.md
Verify Product Outcomes
Contract
Verification is evidence, not a claim. Distinguish code complete, tests passed, deployed, observed, customer validated, and outcome achieved. Verify the user journey and failure paths, not only the happy-path implementation.
Workflow
- Resolve the authoritative requirements, decision records, designs, acceptance scenarios, release artifact, environment, and exact version or SHA.
- Convert intended outcomes and constraints into a traceability matrix with observable evidence.
- Inspect the implemented surface and supporting behavior. Test primary journeys, permissions, empty and error states, accessibility, recovery, analytics, and operational controls.
- Compare artifact intent, implementation, automated checks, environment state, and observed behavior. Record evidence links, screenshots, logs, or IDs.
- Classify gaps as missing requirement, implementation divergence, regression, ambiguous spec, instrumentation gap, or accepted tradeoff.
- Assess severity from customer outcome and risk, not code size.
- Produce a verdict per requirement and an overall verified, conditional, or failed state. Name what remains unverified.
BuildBetter Acceleration
If BuildBetter MCP is available, search organization skills first. Use projects, linked tickets, evidence, documents, signals, surveys, and agent-session or release context when deployed. Keep BuildBetter evidence distinct from browser, test, CI, staging, and production proof.