architecture-preflight

To check architecture boundary violations before feature planning, you run a preflight analysis against your repository scope and architectural standards to detect boundary risks and generate an Architecture Preflight Report with actionable ADR recommendations.

An architecture preflight report is a structured output that identifies boundary compliance risks, validates repository scope, and provides ADR recommendations to ensure architecture decisions are explicitly constrained and governance requirements are met before planning begins.

To align feature scope with architecture boundaries and ADRs, analyze the feature requirements against defined architectural contracts to detect boundary risks, verify repository scope, and output required interface definitions and ADR alignment steps for the feature team.

Yes, you can use architecture preflight to enforce governance and gatekeeping by running a boundary compliance analysis against your architectural standards prior to planning, ensuring no feature proceeds without explicit ADR alignment and boundary validation.

You need to run architecture boundary analysis and ADR verification when preparing for feature planning, specifically to detect boundary risks, validate required interfaces, and ensure your architectural decisions are aligned with governance standards before development starts.