scaffold-message-handlerlisted

## STOP - Read before ANY tool call 1. Read `{{GUARDRAILS_PATH}}` 2. Read `_shared/sdd-artifacts/SESSION.md`; load session-state for `$Cwd` 3. If the relevant gate is not approved: **STOP** - ask user **(pt-BR)** - do **NOT** Write/Shell 4. SDD/develop skills: after **ONE** step/task, **STOP** session - handoff only 5. This skill body is **English**; user-facing prompts may be **(pt-BR)** ### Step -1 - Gate check (report in chat before continuing) ``` Gate check: [ ] guardrails.mdc read [ ] SESSION.md read; session-state loaded [ ] PIPELINE.md read (SDD skills only) [ ] User confirmed current action (sim) -> If any unchecked: STOP ``` --- # Skill: scaffold-message-handler ## Status **Scaffold** - guides discovery, requirements, and implementation in the **target repository**. This toolkit ships **no** embedded corporate consumer templates or org-specific wiring. ## Trigger Invoke when the user asks for: `/scaffold-message-handler`, `create message consumer`, `/scaffold-message-handler`, or when a PLAN step adds a new queue/topic handler. Optional arguments: message or event name, queue/topic name, or path to an existing consumer to mirror. ## Outcome In the **target workspace** (not this toolkit repo unless it is the .NET repo under work): 1. Detected messaging stack and reference consumer(s) 2. Confirmed requirements (payload, errors, idempotency, retry, DLQ) 3. Proposed file layout aligned with the repo 4. Scaffold code and tests **only after** user confirmatio