architect-service

To generate service-level architecture documentation, you provide project-level service boundary details like the PDR and contracts. The skill inherits these constraints to produce structured specs, architecture layers, and module documents.

Decomposing a service into architecture layers and modules involves defining clear responsibilities, external dependencies, and cross-cutting concerns. This skill guides that decomposition by distilling boundaries into separate specs and module documents.

You need to provide project-level service boundary details, specifically the PDR and contracts, to start documenting service architecture. These inputs define the scope and constraints for the generated architecture files.

Service architecture layering works with existing project contracts by inheriting their boundaries to define the service scope. The skill ensures the generated architecture layers and specs align with these project-level constraints.

Yes, you can output individual module documentation separately. The skill generates optional .docs/architecture/modules/<name>.md files alongside the main architecture document to support granular module reviews.