What problem does it solve? Writing Nordic NCS (nRF Connect SDK) firmware from engineering specs is slow and error-prone when every module is built from scratch, and code often drifts out of sync with the PRD and spec documents it was written against. ## Core Features & Use Cases - Spec-driven implementation: Reads specs from docs/dev-specs/ and creates Zephyr modules (src/modules/<name>/) with Kconfig, CMake wiring, SMF state machines, Zbus integration, and structured logging. - Reuse-first workflow: Checks zego bricks (button, led, wifi, network, BLE provisioning, NTP, memory monitor) before writing new code, and falls back to the nordic-wifi-webdash and nordic-wifi-memfault reference repos for uncovered patterns. - Testing and CI: Generates native_sim ztest suites for pure-logic modules, builds for target boards, and scaffolds a GitHub Actions workflow from a build template covering three Nordic board targets. - Doc-drift guard: Tracks PRD/spec versions in prj.conf and prompts to update docs when code changes outpace them. - Use Case: After specs are finalized for a Wi-Fi sensor device, invoke this skill to wire in the button and LED bricks, implement a custom webserver module modeled on nordic-wifi-webdash, run host tests on native_sim, and produce a CI pipeline that builds release hex files for three boards. ## Quick Start Ask Claude to implement the modules described in docs/dev-specs using the chsh-sk-ncs-3-dev-coding skill, reusing zego bricks where they apply.
