architecture

To create a system architecture blueprint, this Skill applies structured elicitation to define project boundaries, dependencies, and technical decisions. It outputs a structured architecture document and a project registry to align product structure with implementation.

A project registry in system design is a machine-readable metadata store of capability mappings and dependency relationships. It captures technical decisions and documentation units to maintain alignment between architecture boundaries and downstream planning workflow.

Documenting system topology and cross-cutting technical decisions is achieved by updating the architecture blueprint. This process captures shared infrastructure choices, service stacks, and dependency relationships to ensure consistency across all application projects.

Yes, you can use this Skill to plan dependencies for a multi-project application before implementation. It validates registry consistency and synchronizes architecture documentation with implementation planning artifacts to define clear project boundaries.

The best way to maintain alignment is through continuous synchronization between architecture documentation and implementation planning artifacts. This Skill validates registry consistency to ensure technical decisions and dependency relationships remain accurate during development.

You should avoid a centralized architecture blueprint if your project lacks complex cross-cutting decisions or multiple interdependent services. The structured registry and topology planning are intended for multi-project applications requiring strict boundary and dependency management.