Implementing Firmware

Firmware Implementation

Target: $ARGUMENTS

Implement firmware code with mandatory requirement traceability tags, following ESP-IDF or PlatformIO patterns.

References (MUST READ)

Read these before proceeding:

• references/esp-idf-patterns.md — Component structure, FreeRTOS, sdkconfig, idf.py
• references/platformio-patterns.md — platformio.ini, pio commands, library management
• references/c-safety-rules.md — MISRA-C cppcheck flags, clang-tidy, tagging rules

Workflow

1. Detect framework:

• CMakeLists.txt + sdkconfig* → ESP-IDF
• platformio.ini → PlatformIO
• Neither → ask user which framework to use

1. Read existing requirements — Check for docs/requirements.md to understand which SW-REQs need implementing
2. Implement code with mandatory docstrings on every new function:

```c /**

• @brief

*

• @requirement SW-REQ-NNN
• @parent PRD-REQ-NNN
• @test TEST-NNN

*

• @param ...
• @return ...

*/ ```

1. Create test stubs in test/ with matching @test TEST-NNN references
2. Lint with cppcheck:

``bash cppcheck --addon=misra.py --std=c11 --enable=all --xml src/ 2> misra-report.xml ``

1. Build:

• ESP-IDF: idf.py build
• PlatformIO: pio run

1. Report — Count tagged functions, list any warnings

Rules

• Every new function must have @requirement, @parent, and @test tags
• Follow existing code style (indentation, naming conventions) in the project
• Use ESP-IDF error handling patterns (ESP_ERROR_CHECK, esp_err_t returns)
• Do not suppress MISRA warnings without documenting the deviation
• Create header declarations alongside implementations
• Test stubs must compile even if test logic is not yet implemented

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: qte77
• Source: qte77/claude-code-plugins
• License: Apache-2.0
• Homepage: https://qte77.github.io/claude-code-plugins/

Install and usage instructions live in the source repository linked above.