dk-breadcrumb-creator

To trace a workflow end-to-end across a monorepo, provide a flow name to generate a breadcrumb analysis. This traces execution across frontend, backend, workers, and CLI layers, outputting structured FLOW.md, DETAILS.md, and DEBUG.md artifacts.

Generating debugging guides for cross-layer flows in a monorepo involves producing a DEBUG.md file within a breadcrumb analysis directory. This document accelerates issue diagnosis during development and incident response by tracing the flow across architectural layers.

Creating breadcrumb documentation for a specific user flow requires providing a flow description to generate scaffolding. The process verifies existing breadcrumbs before writing new entries, ensuring accurate cross-referencing for complex monorepo paths.

Yes, you can cross-reference existing breadcrumbs when documenting complex monorepo workflows. The tracing process verifies current breadcrumbs before writing new entries, suggesting extensions or new breadcrumbs to fully capture intricate cross-layer flows.

Tracing a workflow through a monorepo generates three standard documentation artifacts: FLOW.md, DETAILS.md, and DEBUG.md. These files are created under a dedicated breadcrumb analysis directory structured by the specific flow name.