map-workflow

Domain workflow mapping codifies operational pipelines into structured stages with entry and exit criteria. You need it during domain discovery to convert raw operational data into auditable documents governing daily rhythms and automation candidates.

Provide domain discovery results to generate a populated domain-workflow.md file. The output enforces structure by requiring entry and exit criteria, conversion rates, and time budgets for each pipeline stage to finalize the codified roadmap.

Yes, the domain workflow document captures conversion rates and time budgets for bottlenecks. It identifies automation candidates across multiple domains and outputs a final distribution to domain-input/domain-workflow.md for loading into the kernel.

You can generate automation candidates across multiple domains by mapping daily and weekly rhythms. It builds on domain discovery results to finalize a complete, load-ready domain workflow document with auditable metrics.

The best way to structure a load-ready domain workflow document is to populate domain-input/domain-workflow.md with pipeline stages, conversion rates, and time budgets. This enforces governance and enables quick domain understanding for loading.

You need prior domain discovery results to map a complete workflow accurately. The mapping skill builds directly on domain discovery outputs to finalize the domain-workflow document with required metrics and automation candidates.