name: ntn-validation-gate-runner description: Use when ntn-sim-core changes need validation planning or phase-completion verification, to map the current scope to the correct validation gates, scripts, blockers, and evidence requirements.
NTN Validation Gate Runner
Use this skill whenever code behavior changes, a phase/group may be complete, or a reviewer needs clear evidence for go/no-go.
Required Read Order
Read these first:
agent-governance.mdsdd/ntn-sim-core-validation-matrix.mdsdd/ntn-sim-core-acceptance-gates.mdsdd/ntn-sim-core-implementation-status.md- the active phase SDD
package.jsonscripts section
Workflow
- Identify the current phase/group and the files touched.
- Map the change to the relevant
VAL-PLAT-*gates. - Separate validations into:
- iteration set: smallest useful checks while developing
- completion set: required checks before claiming the group/phase is done
- Run or recommend the smallest correct set.
- Report which failures are blocking and which are informative only.
Default Script Families
Typical scripts to consider:
npm run lintnpm run validate:tracenpm run validate:profilesnpm run validate:runtimenpm run validate:registrynpm run validate:bundlenpm run validate:stagenpm run validate:visual-browserwhen browser-visible behavior changes
Phase Mapping Rule
Do not pick scripts by habit alone. Always map them to the active phase gates. For example:
- Phase 1 should emphasize registry-oriented gates.
- Phase 2 should emphasize bundle/interface gates.
- Phase 3 should emphasize profile migration and round-trip gates.
- Phase 4 should emphasize frozen runtime/exposure contract gates.
- Phase 5 should emphasize structural size limits, cleanup, and orchestration purity.
Output
Report:
- which
VAL-PLAT-*gates apply - which scripts should run for iteration
- which scripts are required before claiming completion
- whether current evidence is sufficient to close the group/phase
- any validation gaps that should be added to SDD or the validation matrix