architecture-discovery

Architecture discovery for a greenfield project starts by answering targeted universal questions to map domain contexts, identify constraints, and establish clear project context before design. The structured workflow then outlines concrete architectural options to guide implementation.

An Architecture Decision Record (ADR) documents architectural decisions, patterns, and artifacts to support team alignment. Generating ADRs during discovery ensures concrete rationale and context are captured for future reference and integration planning.

Yes, the structured discovery workflow explicitly targets cloud migration and complex integration projects across multiple teams and cloud environments. It surfaces targeted questions and defines domain boundaries to handle these specific architectural contexts.

The best way to document domain boundaries is through a structured multi-phase workflow that generates an architecture-package.md, domain patterns, and ADRs. This consolidates artifacts into an integrated package for team alignment and handoff.

After defining software architecture through structured discovery, you receive a CLAUDE.md, an architecture-package.md, and implementation plans. These artifacts support implementation work by consolidating decisions, patterns, and domain contexts.

Structured architecture discovery is not necessary for simple, single-team projects with straightforward requirements. It is designed for complex scenarios like greenfield, migration, and multi-team integration where defining domain boundaries and generating ADRs add significant value.