esp32-feature-contract
Creates a mission file and an implementation contract (scope, affected files, risks, tests, rollback) that must be accepted before any ESP32 firmware code is changed. Use when the user asks to "add a feature", "implement", "fix a bug", "refactor", "write a contract", "start a mission", "plan this change", "/contract", or "resume the mission" in an ESP-IDF, ESP32, ESP32-S3, ESP32-C3 or ESP32-C6 project, and before editing any firmware source.
- Version
- 0.2.0
- License
- MIT
Pinned to revision f4b67c33f6fb, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/esp32-feature-contract/SKILL.md
- skills/esp32-feature-contract/agents/openai.yaml
- skills/esp32-feature-contract/assets/implementation_contract.md
- skills/esp32-feature-contract/assets/mission_template.md
Every link opens the file at its source, pinned to the revision this page describes.