STOP - Read before ANY tool call
Read _shared/skill-boilerplate.md first. It holds the guardrails read, the session gate rule, the user sim rule, the one-step rule, the gate check, and the user chat language rule. The steps below are skill-specific only.
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
Negative signal: applies as defined in _shared/skill-boilerplate.md; the skill-specific signals are listed below.
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):
- Detected messaging stack and reference consumer(s)
- Confirmed requirements (payload, errors, idempotency, retry, DLQ)
- Proposed file layout aligned with the repo
- Scaffold code and tests only after user confirmation - following existing project patterns, not copied templates from this repo
Lazy-load
| When | Path |
|---|---|
| Reference index (routing only) | skills/scaffold-message-handler/reference.md or {{TOOLKIT_ROOT}}/skills/scaffold-message-handler/reference.md after sync |
| Process step detail (lazy) | skills/scaffold-message-handler/references/<section>.md |
| Generating or reviewing .NET code | {{TOOLKIT_ROOT}}/skills/_shared/dotnet-guidelines/clean-architecture.md |
| C# conventions | {{TOOLKIT_ROOT}}/skills/_shared/dotnet-guidelines/csharp-patterns.md |
| .NET test patterns | {{TOOLKIT_ROOT}}/skills/_shared/dotnet-guidelines/dotnet-test-patterns.md |
| Structure / quality (when coding) | {{TOOLKIT_ROOT}}/skills/_shared/code-guidelines/principles/structure-and-quality.md |
| Small follow-up without SDD | /dotnet-developer |
Never by default: do not preload all references/*.md, full messaging docs, or unrelated guideline packs. Load one references/<section>.md per Process step (SKILL-REFERENCE-RETRIEVAL.md).
Process
Read references/<section>.md for detection/checklists — not full reference.md.
0. Workspace
Confirm target .NET repository (.sln or worker/API with messaging). If the workspace is the toolkit only, stop and ask which repo to open.
1. Detect messaging stack
Grep/Glob per references/stack-detection.md. Report:
| Signal | Likely stack |
|---|---|
MassTransit, IConsumer<T> |
MassTransit (transport varies) |
RabbitMQ.Client, ConnectionFactory |
RabbitMQ direct |
Azure.Messaging.ServiceBus (or similar ASB packages) |
Azure Service Bus SDK |
| Other | Describe generically; read one existing consumer |
Default when none detected: MassTransit with RabbitMQ transport (implicit). Still collect requirements before scaffolding. Use Azure Service Bus only when ASB packages or existing ASB wiring are already in the repo.
Do not require corporate docs/consumidores/ paths.
2. Find conventions
Glob existing consumers/handlers in the repo. Note: namespace layout, registration (AddMassTransit, hosted service, etc.), message contract location, test project pattern.
If no consumer exists, say so and propose a layout consistent with Clean Architecture after reading clean-architecture.md (references/layering.md).
3. Collect requirements (blocker before code)
Ask using references/requirements-checklist.md. Free-text intake: each answer is open text, and the question stays open until answered. Minimum:
- Queue or topic name (and subscription if applicable)
- Message contract (type name, key fields, schema source)
- Processing responsibility (what changes in the system)
- Error handling: retry count/backoff, DLQ or error queue
- Idempotency strategy (natural key, outbox, dedup store)
- Test expectations (unit vs integration)
Wait for answers. Do not invent queue names or payloads.
4. Propose scaffold plan
Present (references/scaffold-checklist.md):
- Files to add or extend (paths from repo conventions)
- Registration point (DI / MassTransit config)
- Test files and how to run them
Ask explicit confirmation before writing code. Single select; ids confirm (write the scaffold), adjust (change the plan first), cancel (stop). Render labels in the user chat language; answer mapping: {{TOOLKIT_ROOT}}/skills/_shared/agents/QUESTIONS.md.
5. Implement (target repo only)
After confirmation:
- Load
clean-architecture.mdandcsharp-patterns.md; when adding tests, loaddotnet-test-patterns.md(references/layering.md,references/test-guidance.md) - Mirror naming and folder structure from step 2
- Add consumer/handler, contract if missing, registration, and tests
- Run
dotnet buildand targeteddotnet testfor affected projects
6. Summarize handoff
Report: stack detected, paths touched, how to run locally, open risks (idempotency, poison messages). See references/related-skills.md, references/exclusions.md, references/context-management.md.
| Situation | Next |
|---|---|
| Commit | /commit |
| Part of SDD PLAN step | Mark PLAN step; continue in new session if another step remains |
| Build failure | /repair-dotnet-build |
Must not
- Ship or copy hardcoded consumer templates from external prompt collections or internal org repos into the toolkit
- Assume a specific organization or proprietary observability tools
- Generate code before requirements are collected and the user confirms the plan
- Preload entire
dotnet-guidelines/tree beyond clean-architecture and csharp-patterns when coding
Handoff examples
/repair-dotnet-build
/sdd-develop - <full-plan-path> - Step N
SDD PLAN paths: resolve per {{TOOLKIT_ROOT}}/skills/_shared/sdd-artifacts/STORAGE.md (features/**/PLAN/PLAN_*.md or global {{SDD_ROOT}}/<repo-id>/features/**/PLAN/ only). Not root/flat PLAN/ and not docs/documentation-plan/plan.md.