agency-workflow-architect

To document undocumented API workflows, you scan repository routes, workers, and infrastructure to discover entry points and implicit lifecycles, generating build-ready specs with failure modes, handoff contracts, and test cases.

A workflow tree specification is an exhaustive, step-level breakdown of system paths including timeouts, observable states, and cleanup inventories. You need one for background jobs to prevent production surprises caused by implicit workflows and race conditions.

Generate test cases and cleanup inventories by mapping user journeys into structured workflow trees that specify step-level actions, handoff payload schemas, and observable states suitable for QA validation.

Yes, you can compare workflow specifications against actual code using reality checker integration to record discrepancies, track assumptions, and define remediation actions for undocumented branches.

The best way to specify handoff payload schemas for scheduled tasks is to map them into structured workflow trees that explicitly define every handoff, failure mode, and observable state.

A limitation is that discovering implicit workflows in infrastructure modules requires scanning existing config and migrations to find entry points, meaning fully untracked or dynamically generated infrastructure paths may remain undiscovered without explicit repository access.