What problem does it solve? Turning a sharpened feature idea into a concrete AL/Business Central architecture is error-prone: modules get invented without justification, seams lack real adapters, and BaseApp facts go unverified. This Skill settles the feature architecture and writes a verified architecture.md that downstream scoping and implementation steps can consume directly. ## Core Features & Use Cases - Architecture authoring: Defines slices, module maps, BC patterns per module, and the R → P → W (read / pure / write) boundary, then writes architecture.md into the feature's spec folder. - Design disciplines: Enforces the deletion test for modules, the two-adapter rule for seams, AL realisation per slice with new/extends markers, and AppSource sanity checks for BaseApp modification and shipped-field renames. - Parallel design-twice: For non-trivial calls, runs three delegated design passes with divergent constraints and compares them along depth, locality, and seam placement. - Use Case: After running /al-event-model on a user-facing feature, invoke this Skill to produce a verified architecture.md naming modules, patterns, and testability constraints, ready for /al-scope to decompose into tasks. ## Quick Start Ask the agent to design the AL feature architecture from the current event model and write architecture.md into the spec folder.
