What problem does it solve? Building an Intent Architect module involves judgment calls that mechanical how-to guides do not cover: how to decompose modules, when to choose a template versus a factory extension, whether to use settings or stereotypes, and how to verify generated output. This Skill provides the strategic decision framework for those design decision points. ## Core Features & Use Cases - Module Decomposition Strategy: Apply the dependency-boundary rule to decide between root modules, bridging modules, and common modules, and avoid shared-project DLL version skew. - Template & Configuration Judgment: Choose between template and factory extension, pick file cardinality and managed modes (Fully, Merge, Ignore), and decide between module settings, stereotypes, and convention-based defaults. - Two-Phase Verification: Reproduce output on a reference app, then run a mandatory from-scratch generation test with a spanning set of scenarios and comprehensive domain models. - Use Case: When extending an eventing module, use this Skill to decide whether the integration belongs in a bridging module, whether the topic name should be a convention or an explicit stereotype, and how to test both single-app and cross-app topologies. ## Quick Start Ask the AI to help you decide whether a new integration should be a bridging module or part of an existing root module while building an Intent Architect module.
