Architecture Refiner

Step 0: Style Selection

Before anything else, ask the user which architecture style their team uses:

"What architecture style does your team use?

1. Clean Architecture (default) — layers (Domain, Application, Interface, Infrastructure), dependency inversion, command/query separation
2. Hexagonal / Ports & Adapters — core domain surrounded by ports, adapters on the outside
3. Modular Monolith — vertical slices, each module owns its own layers
4. Custom / Define from scratch — you describe the layers and rules"

Branching:

• Option 1 → proceed to the clean architecture flow below (existing interview). Template: ./assets/template-clean-arch.md. Output: .lattice/standards/architecture.md. Config key: paths.architecture. No architecture_mode key needed (defaults to clean).
• Options 2–4 → proceed to the generic architecture flow. Template: ./assets/template-generic.md. Output: .lattice/standards/architecture.md. Config key: paths.architecture. Additionally, set architecture_mode: custom in .lattice/config.yaml.

The rest of this document describes the clean architecture flow (Option 1). For the generic flow (Options 2–4), read ./assets/template-generic.md and follow its <!-- INTERVIEW GUIDANCE: --> comments. The facilitation approach, conversation style, output assembly, and document quality checks below apply to both flows — substitute the appropriate template, output path, and config key.