add-cross-domainlisted

# Cross-Domain Dependency Wiring Request: $ARGUMENTS (format: "from:{consumer} to:{provider}", e.g.: "from:order to:user") ## Default Flow Position - Step: `implement` (`approach options` upstream is **always mandatory** — cross-domain dependency is an architecture commitment) - Routes after: verify (`/test-domain {consumer} run`, `/test-domain {producer} run`) → self-review (`/review-architecture {consumer}`) → completion gate (`/sync-guidelines`) - Recursion guard: do not invoke `/plan-feature` from inside this skill ## Procedure Overview 1. Analysis — identify consumer/provider, determine needed functionality 2. Implementation — verify provider Protocol → modify consumer Service → wire DI Container → verify app container 3. Verification — grep for prohibited imports, run tests for both domains Read `docs/ai/shared/skills/add-cross-domain.md` for detailed steps and code templates. Also refer to `docs/ai/shared/project-dna.md` §5 for DI patterns and §2 for base class paths.