spec-blind-validate

To validate tests against a public API surface only, the skill authors black-box tests from the acceptance criteria plan and runs them as a Final Gate teammate. Three PreToolUse guards enforce surface isolation during test execution.

Black-box testing for public API surface validation is a method that authors tests strictly against public artifacts without accessing implementation source code. This prevents data leaks from internal code and ensures tests validate only external behavior.

You run public API tests in parallel with other harness checks by invoking the validator as a Final Gate teammate. It executes alongside other gates to accelerate verification while preserving isolation from implementation details automatically.

Yes, black-box testing works with Final Gate workflows by applying pre-checks that guard read, write, and bash operations. This maintains surface isolation and emits SPEC_BLIND verdicts with targeted failure context to guide fixes without exposing internal code.

To prevent test data leaks from internal implementation code, enforce test authoring strictly against public-surface artifacts using PreToolUse guards. This blocks access to implementation details and ensures tests rely only on the public API surface.

A limitation of spec-blind validation is that tests cannot access implementation details, which may restrict debugging depth. It also requires precise failure context reporting to guide fixes effectively when SPEC_BLIND_FAILED or SPEC_BLIND_BLOCKED verdicts are emitted.