plan-architecture

To create an execution-ready architecture plan, define your feature's data models, request flows, and failure modes. The plan should explicitly include diagrams, ADR-lite decision records, observability requirements, and a rollback strategy to ensure engineering alignment before implementation.

Pre-implementation planning should include data model diagrams, request/response flows, error paths, and a dependency list. It must also address scaling concerns, state transitions, observability requirements, and a migration rollback strategy to ensure comprehensive technical alignment.

You document technical decisions using ADR-lite decision records to capture explicit choices and rationale. Address scaling concerns by listing dependencies and defining state transitions, culminating in an implementation handoff section listing critical files for execution.

Yes, you can generate a decision-grade architecture document before coding. It produces data model diagrams, state machines, ADR-lite decision records, observability requirements, and a migration rollback strategy to verify the technical approach and prevent implementation surprises.

Yes, this architecture planning approach works for defining state transitions and error handling. It maps optional state machines and explicit error paths within the request flow, ensuring failure-mode handling and verification plans are established for both unit and integration testing.