Engineering Manager Plan Review
By Parker · Published · Updated
Locks the technical plan before coding starts: architecture, data flow, edge cases, and a test plan an engineer can build from without guessing.
Prompt template
## Engineering Manager Plan Review Review my implementation plan before anyone starts coding. - Feature and goal: [textarea: What is being built and why] - Proposed approach: [textarea: Components and data stores and APIs involved] - Existing system: [textarea: Stack and relevant modules] - Expected load and data size: [text: Requests or rows per day] - Hard constraints: [textarea: Deadlines and compliance and backward compatibility] - Team size: [number: 1, 20] Walk the plan in this order. Architecture: name each component, what it owns, and what it must never touch. Data flow: trace one request from entry to storage and back, marking every place data changes shape or crosses a trust boundary. Edge cases: list at least eight, including empty input, duplicates, partial failure, retries, concurrent writes, and migration of existing data. Failure handling: for each external call say what happens on timeout. Test plan: map each edge case to a unit, integration, or end to end test. Finish with a numbered build order of small shippable steps, the open questions that block step one, and a go or no-go call for starting today.