subarc-create

To design a sub-architecture, define self-contained boundaries, APIs, and data models for the new service. This ensures explicit parent-child linkage and scopes tradeoffs, producing a delivery-ready architecture document that aligns with your root system.

Subsystem design is planning self-contained architectures for new application components. You need to document it when adding new services to an existing root architecture, ensuring dependencies, NFRs, and cross-system contract assumptions are explicitly mapped.

Plan technology choices and build-vs-buy decisions by scoping tradeoffs within a sub-architecture document. This process evaluates non-functional requirements and dependency mappings to produce a ready-to-review technical plan for your new application component.

Yes, mapping sibling dependencies and cross-system contract assumptions is supported. The sub-architecture planning process explicitly documents these parent-child linkages to ensure new components seamlessly integrate with existing architectural standards.

Sub-architecture documentation should follow a markdown format, specifically generating a file like <subdir>/<appname>-architecture.md. This delivery-ready artifact explicitly links to the root architecture.md and details boundaries, APIs, and data models.

You should not use a sub-architecture planning skill for standalone applications lacking a root architecture, or when a quick prototype is needed without explicit parent-child linkage, non-functional requirement scoping, or cross-system contract documentation.