菜单
Use when: starting a roadmap/initiative feature, new milestone work, a transport/codec/backend that adds behavior, or any change big enough to need a design. Author or update a spec under docs/specs first; code cites the spec by section.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | spec-driven-change |
| description | Use when: starting a roadmap/initiative feature, new milestone work, a transport/codec/backend that adds behavior, or any change big enough to need a design. Author or update a spec under docs/specs first; code cites the spec by section. |
| argument-hint | The feature/initiative, the milestone or plan track, and the seams it touches |
AGENTS.md.docs/specs/<slug>.md. Fill every section — do not skip the config-field table (§5,
no magic numbers), the wire/schema posture (§6), the test plan by category (§7), or the
CHARTER §4 invariant checklist (§9).Definition.Protocol / config); cite the spec's § numbers in
docstrings (the FPV modules and meshsa.command already do this).CHANGELOG.md +
NEXTSTEPS.md and move the spec status to Implemented (Validated after the spec's
hardware/bench exit criteria pass).docs/specs/README.md, docs/specs/TEMPLATE.mddocs/specs/PHASE1_SPEC_v1_1.md (worked example; code cites §5.1 etc.)docs/IMPLEMENTATION_PLAN.md (the queued specs to author)docs/CHARTER.md §4 (the invariant checklist every spec answers)Use when: working in packages/jetson_yolo_gcs — adding a detector backend (YOLO/Hailo/ONNX/TensorRT), a tracker backend (Norfair/SORT), GStreamer camera/egress pipeline, the MAVLink LANDING_TARGET bridge, precision-landing safety, or the perception pipeline failure policy.
Use when: running pre-PR checks, performing regression testing, validating ruff linting/formatting, verifying mypy type safety, and checking test coverage before pushing.
Use when: working on the optional NVIDIA Nemotron inference bridge — meshsa.inference, NemotronClient/InferenceService/NemotronConfig, MESHSA_INFERENCE_* env vars, aiohttp session reuse, [AI Insight] feedback-loop filter, or the aioresponses test mocks.
Use when: adding or changing metrics/health export — RouterMetrics, render_prometheus, per-transport counters, the /metrics or /healthz route, HealthConfig fields, or a Grafana golden-signal dashboard.
Use when: touching the supervised two-way command path (Initiative C) — meshsa.command.*, flightctl/run_commander.py, arm/disarm/RTL/set_mode, COMMAND_INT/ACK, force-disarm, operator confirmation, command audit log, or arm preconditions.
Use when: adding a meshsa codec, changing JSON/Compact/CoT encoding, wire format, codec registry, Envelope serialization, per-transport codec bridge, or decode compatibility.