architect-init

To document inferred architecture from a brownfield codebase, run the analysis to generate ADR drafts organized by sub-systems. The process identifies architectural patterns and cites concrete code evidence to assign a confidence level for each inference.

Generating ADRs for an existing codebase involves detecting architectural patterns like monolith or microservices and drafting records per sub-system. It links to clarifications for validation and cites concrete files, directories, and patterns as evidence.

Identifying architectural patterns in a legacy codebase requires analyzing the directory structure and code relationships. The skill detects patterns such as monolith, microservices, or modular monolith and documents them as inferred architectural decisions.

Yes, you can use code analysis to prepare architectural clarification questions. The process identifies information gaps in the inferred architecture and generates targeted questions for stakeholders to validate the assigned confidence levels of each decision.

Yes, this approach works for both monolith and microservices architecture documentation. It detects various architectural patterns from the existing codebase and generates ADR drafts organized by sub-systems regardless of the initial structure.

Inferring architectural decisions from undocumented code relies on analyzing structural patterns, which means inferences may have information gaps. It assigns confidence levels to each inference and generates clarifying questions to resolve ambiguity with stakeholders.