planning-architecture

Architecture planning translates ADR-driven updates into an executable plan by reading the SSOT, generating common definitions, and drafting integration issues for review. It extracts design briefs and maps bounded contexts to align teams before implementation begins.

Creating audit-ready documentation for cross-team architecture upgrades involves orchestrating SSOT-to-plan translation using defined templates and references. It ensures consistent terminology across artifacts while slicing work into discrete, dependency-linked issues for approval.

Bounded-context mapping during preliminary architecture design works by extracting design briefs from the SSOT and formulating a visualization strategy. This process creates common definitions that ensure consistent terminology across all subsequent integration artifacts and issues.

You need a feature branch to start planning an architecture update. The quick start process requires activating a switching-feature-branch skill first, then running scoping-design-tasks to generate the Design Brief before orchestrating the full plan.

You can submit a cross-team architecture plan for PR-based approval. The process produces a plan with clear dependencies and mapping, ready for review by linking discrete individual and integration issues to shared definitions and templates.

You should not use an SSOT-driven approach for architecture planning when your project lacks established ADR governance or a centralized Single Source of Truth. This method relies on reading existing ADRs and SSOTs to formulate visualization strategies and common definitions.