harness-implementation

Start from an approved design review document, write a failing test first (Red), add the minimal implementation to pass it (Green), then refactor to clarify responsibilities. Update design and test documents together with the code.

Isolate vendor SDK integration in the C++ Infrastructure layer and lift word parsing, message composition, and status interpretation into the domain model. The C# layer orchestrates use cases and UI without calling device SDKs directly.

No. The workflow requires an existing design review with defined scope, exclusions, and C++/C# responsibility boundaries before any implementation begins. Starting without it violates the enforced design-review-then-implement order.

All public types and methods must carry Korean XML documentation comments, including summary, parameter, and return tags. Complex private logic should also receive explanatory comments where needed.

It assumes a completed design review and does not cover requirements gathering or design itself. It also focuses on implementation discipline rather than vendor-specific SDK configuration or hardware setup.