chsh-sk-ncs-4-test-validation

Invoke the validation skill after static verification or a feature completion. It reads your PRD acceptance criteria, builds a coverage matrix into VALIDATION_PLAN.md, executes test rounds on connected boards via shell commands, and produces VALIDATION_REPORT.md with evidence and a verdict.

Use ZView over SWD with a J-Link probe while driving load over UART. Build with CONFIG_INIT_STACKS, CONFIG_THREAD_MONITOR, and CONFIG_THREAD_STACK_INFO, then run west zview record during the high-memory round and extract peaks with west zview dump --frame last --json.

Yes, no-shell boards like the nRF7002DK with CONFIG_SHELL=n are supported. Tests are driven via button triggers and UART log parsing instead of shell commands, with explicit human instructions written into the plan for manual steps.

Empty ZView output means the firmware build is missing the required instrumentation configs. Rebuild with an overlay enabling CONFIG_INIT_STACKS, CONFIG_THREAD_MONITOR, CONFIG_THREAD_STACK_INFO, and CONFIG_SYS_HEAP_RUNTIME_STATS, then flash that instrumented build for the ZView round.

Run static verification first for code review, security, and format checks without hardware. Run this hardware validation anytime after that—post-feature or pre-release—to confirm PRD criteria hold at runtime and to capture real memory watermarks under load.