User Input
$ARGUMENTS
Outline
- Read
docs/skills/catalog.md#add-replacement-contract-implementation. - Read the framework replacement-contract gate.
- Identify the owning domain, contract, current implementations, and expected selection/conflict behavior.
- Confirm the workflow is not a contribution flow and must not use contribution-style
IEnumerable<T>semantics. - Plan registration, conflict detection or prevention, extension-point catalog updates, and tests.
- Return a plan with exact files and open questions before implementation.
Do not implement until the user approves the plan. After approval, required tests, extension-point catalog updates, generated-map refreshes, and small docs follow-through are part of completing the approved work.