architect-refine-critique

To generate an Architecture Decision Record, you can run a three-phase design review workflow that produces a complete ADR. It orchestrates design, refinement, and critique steps to capture domain boundaries, trade-offs, and final decisions in a traceable document.

A collaborative design review is best run by chaining architect, refiner, and critique subagents. This enforces structured feedback and governance, resulting in a shared architectural understanding and a set of stored artifacts like design.md and critique.md.

Yes, you can apply tactical DDD and separation-of-concerns principles to document architectural trade-offs. The workflow specifically uses these principles to surface domain decisions, risks, and trade-offs within a governance framework.

To structure ADR artifacts, the workflow outputs files under a docs/design-reviews/[name]/ directory. This includes design.md, refinements.md, refined.md, critique.md, and the final adr.md to ensure traceable architecture decisions.

No specific dependencies are required to run the design review workflow and generate ADRs. The skill operates independently to orchestrate the architect, refiner, and critique phases without external tool dependencies.

You need a three-phase architecture critique workflow when your team requires enforced governance and traceable ADRs. It is suited for evaluating new modules where surfacing deep trade-offs, risks, and domain boundaries is critical before finalizing decisions.