embedded-project-loop

Embedded Project Loop

Use a small durable loop for work that crosses the boundary between files and physical hardware. The agent may prepare and verify host-side artifacts, but it must not invent soldering, flashing, measurement, or field evidence.

Recommended entry point

Load this skill before arduino-workflow-router whenever the request includes physical hardware, more than one session, a pending measurement, a field test, or recovery work. It owns the durable goal, next todo, evidence boundary, rollback path, and physical gate. The router then selects board, wiring, code, toolchain, test, and deployment specialists without closing this loop on its behalf.

State

Use .arduino/ in the project, or a user-selected external evidence directory:

.arduino/goal.md
.arduino/next-todo.md
.arduino/board-profile.md
.arduino/evidence/{build,upload,hardware,system,deployment}/
.arduino/experiment-log.jsonl
.arduino/resume-token.md

Keep secrets, tokens, private network credentials, and unredacted personal data out of these artifacts. goal.md records the exact target, success criteria, non-goals, safety constraints, stop conditions, and rollback path. The next-todo file contains one action, owner, prerequisites, expected evidence, gate, and status.

Bounded iteration

1. Read the goal, next todo, board profile, and last ledger entry.
2. Select one causal firmware, wiring, power, measurement, or diagnostic change.
3. Run the narrowest safe host/build check available.
4. Stop at a physical gate if the next action requires the user.
5. Compare the supplied observation with the expected result and independent safety gate.
6. Append the action, evidence path, decision, rollback, and next todo.
7. Keep only a verified candidate; otherwise record a blocker or restore the current experiment surface.

One iteration must not combine several wiring changes, firmware images, power sources, or measurements. One change keeps failures attributable.

Physical gate