platform-architect

Automate platform architecture documentation by generating Platform ADRs, constraint files, and Arc42 diagrams. This ensures consistency across your system by systematically documenting foundational decisions and rules for initial setup, technology adoption, or refactoring scenarios.

The Architecture Contract Pattern enforces platform constraints by generating machine-readable JSON constraint files. These files define foundational rules that guide development and prevent architectural drift, ensuring future features strictly adhere to established platform guidelines.

Document architectural refactoring decisions by applying the platform-architect skill to generate ADRs and Arc42 documentation. It systematically captures foundational technology adoption choices, ensuring all subsequent feature development adheres to these updated guidelines.

Yes, you can generate machine-readable JSON constraints to prevent architectural drift. The skill creates these constraint files alongside your Arc42 documentation to programmatically guide development and validate adherence to the platform's foundational rules.

Yes, the platform-architect skill requires adherence to ATAM Lite methodology for comprehensive architecture validation. It applies this alongside the Architecture Contract Pattern and Arc42 to ensure thorough documentation and validation of your platform's core architecture.