agent-workflow-architect

Workflow failure mode mapping identifies all potential execution paths and boundary conditions upfront. By designing state machines and documenting cleanup inventories before implementation, teams reduce rework and miscommunication across product and engineering groups.

To design a pre-implementation state machine, draft a baseline process, map its states and transitions, and outline handoff contracts. This captures all execution paths and failure handling requirements, ensuring clear interfaces before development begins.

Handoff contracts formalize clear interfaces between engineering and product teams. Defining these contracts before coding ensures all execution paths and failure recovery options are documented, preventing miscommunication during pre-implementation handovers.

Yes, you can document all execution paths by creating an end-to-end workflow specification. This specification captures success paths, error paths, and boundary conditions, translating them into canonical state machines and cleanup inventories.

Design-first workflow mapping requires a defined baseline process to begin. It focuses on pre-implementation planning and state-machine construction, meaning it must be completed before coding starts to effectively reduce downstream rework.