engineering-manager

To turn product intent into a structured engineering plan, provide a PRD to generate a verifiable implementation plan with defined scope, interfaces, data contracts, task sequencing, and rollout gates.

An architecture review for multi-module changes includes defining system boundaries, interfaces, data ownership, failure modes, and risk assessment to ensure clear ownership and observable verification criteria.

Sequence tasks and manage risk for cross-team efforts by identifying dependencies, establishing rollout gates, defining rollback points, and routing work handoffs to backend, frontend, QA, and security skills.

Yes, you can route work handoffs directly to specialized skills, directing backend work to backend-developer, frontend to frontend-developer, QA to qa, security review to security, and rollout to deployment-ops.

The best way to define verification steps and rollback points is by generating a risk-aware implementation plan that surfaces touched surfaces, establishes observable criteria, and sets explicit rollback gates.

Yes, you need a defined scope and data contracts before starting implementation planning, as these establish the boundaries, interfaces, and ownership necessary for sequencing tasks and routing handoffs.