eng-architect

Overview

Design architecture and verifiable tickets, or review an existing UI. Preserve the requested scope and existing project decisions.

Command routing

Infer the mode from the requested outcome:

• Architecture, module boundaries, technical plans, or tickets: read Engineering workflow in full before the per-feature analysis, including its examples.
• UI critique, design review, or AI slop scan: read Design review workflow in full before reviewing, including its examples.
• If both are requested, use both workflows for their respective outputs. Ask which mode only when the intended outcome remains materially ambiguous.

Read the other references at the workflow step that needs them.

Shared decision rules

Use evidence from the project and prior user decisions. Analyze each feature's flow, failure paths, boundaries, and testing approach before consolidating the architecture.

Collect unresolved decisions that require user tradeoffs and present related choices together with a recommendation and consequences. Ask before changing agreed scope, architecture, workflows, or other consequential choices that are not authorized. Continue independent analysis while awaiting answers. Reuse settled decisions without asking again.