chsh-sk-ncs-2-dev-spec

Generates engineering specification documents from a PRD for Nordic NCS firmware projects.

1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/chshzh/claude --skill chsh-sk-ncs-2-dev-spec-chshzh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chsh-sk-ncs-2-dev-spec
Source: https://github.com/chshzh/claude/tree/main/skills/chsh-sk-ncs-2-dev-spec
Command: npx skills add https://github.com/chshzh/claude --skill chsh-sk-ncs-2-dev-spec-chshzh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Firmware teams need a consistent bridge between product requirements and implementation. This Skill translates a PRD into a complete set of engineering specs — overview, architecture, flash partition layout, memory optimization, and per-module specs — so developers can write code without re-reading the PRD. ## Core Features & Use Cases - Three operating modes: New Design (generate specs from a PRD), Update Specs (sync specs to a newer PRD revision or code drift), and Reverse Design (document an existing codebase). - Template-driven output: Produces 0-overview.md, 1-architecture.md, 2-dts-partition.md, 3-memopt.md, and per-module specs covering Zbus channels, SMF state machines, Kconfig flags, and memory budgets. - Architecture safety rules: Enforces bounded SYS_INIT timeouts, correct zbus observer type selection, and thread justification for nRF Connect SDK projects. - Use Case: After finishing a PRD for an nRF7002DK Wi-Fi product, run this Skill to generate the full docs/dev-specs/ set, then hand off directly to the coding skill. ## Quick Start Ask Claude to use the chsh-sk-ncs-2-dev-spec skill to generate engineering specs from the PRD at docs/pm-prd/PRD.md.

Frequently Asked Questions about chsh-sk-ncs-2-dev-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate engineering specs from a PRD for an nRF Connect SDK project?

Place your PRD at docs/pm-prd/PRD.md and invoke the skill. It detects that no specs exist, enters New Design mode, and generates 0-overview, 1-architecture, 2-dts-partition, 3-memopt, and per-module spec files under docs/dev-specs/.

How do I update specs when the PRD changes?

The skill compares the PRD Changelog timestamps against each spec's PRD Version field and builds a gap table of affected specs. You can choose to apply fixes, which updates the impacted sections and appends changelog entries, or report only.

Can it document an existing Zephyr codebase that has no specs?

Yes. Reverse Design mode scans src/modules/, reads each module's C sources, headers, and Kconfig files, and generates overview, architecture, and per-module specs using the code as the source of truth, flagging undocumented behavior as open issues.

Does it support both SMF+Zbus and multi-threaded architectures?

Yes. The architecture pattern is captured in the PRD or confirmed with the user, and module specs are generated accordingly. SMF modules get Mermaid state diagrams with transitions and error paths; library wrapper modules document external library APIs and callbacks instead.

What are the limitations of the generated specs?

Specs cover how to implement, not what to build — product requirements stay in the PRD. Memory values in 3-memopt.md are initial estimates at design time; measured watermark values are written later by the separate memopt skill after a build.