Procedural steps for creating, linking, and validating GitHub Issues as lifecycle traceability artifacts. Use when creating any StR, REQ-F, REQ-NF, ADR, ARC-C, QA-SC, IMP, TEST, PROBE, BUG, EPIC, DOC, or HOUSEKEEPING issue, or when checking bidirectional traceability coverage.
Rules and procedural steps for adding @implements and @verifies traceability annotations to source code and test files. Use when writing new source files, adding test functions, or auditing existing code for missing traceability.
Procedural steps for Test-Driven Development using Hardware-in-the-Loop (HIL) derived fixtures. Use when implementing features that depend on hardware device behavior (MIDI, serial, network protocols, embedded systems). Covers: PROBE issue creation, HIL capture, fixture-backed CI test writing, and CI hardware…