plan-pipeline-eng-review

To generate a Mermaid architecture diagram before coding, you convert a locked product direction into a buildable technical spec. This process explicitly maps component boundaries, data flows, and failure modes to prevent rushed or poorly integrated implementations.

Mapping failure modes and trust boundaries for asynchronous components requires defining a state machine and inventorying recovery paths. This ensures all state transitions and user impacts are explicitly documented before implementation begins.

Creating a comprehensive test matrix from a state machine design involves enumerating all states and transitions, including failure states. This matrix documents sync versus async boundary decisions and their expected latency outcomes.

You need to plan an architecture spec with diagrams and data flows for non-trivial features with asynchronous components or external dependencies. This should be done after the product direction is locked and before implementation starts.

Yes, this design review approach supports mapping external service dependencies by creating a data flow diagram. It surfaces boundaries between frontend, backend, storage, and external services to ensure proper integration.