What problem does it solve? Product Managers working on Nordic NCS/Zephyr IoT firmware projects need a structured, code-free way to author and maintain a Product Requirements Document that stays in sync with actual code changes, without writing Kconfig or architecture details themselves. ## Core Features & Use Cases - Four operating modes: create a new PRD from scratch (or from an existing codebase), add a feature, change a feature, or sync a stale PRD after code commits land ahead of documentation. - Structured PRD template: generates docs/pm-prd/PRD.md with executive summary, device capabilities, prioritized functional requirements (P0/P1/P2), non-functional requirements, release criteria, and a timestamped changelog. - Customer-facing README generation: produces a fixed-pattern README with evaluator quick start, buttons/LEDs tables, developer guide, and documentation index. - Use Case: A PM notices developers merged Wi-Fi P2P support but the PRD is outdated; the skill detects undeclared commits since the last PRD version pin, summarizes user-visible effects, and updates the PRD with a new changelog entry. ## Quick Start Ask the assistant to use the chsh-sk-ncs-1-pm-prd skill to create a new PRD for your NCS Wi-Fi project or update the existing PRD after recent code changes.
