Adopt a workflow that already exists — GitHub Spec Kit, Kiro, a bespoke prompt/script/cron harness, Claude Code or Codex skill libraries, a Jira/Linear tracker, or an n8n/Temporal automation — and map it into a definition of workflow without rewriting what works. Use when an organisation already has agentic or process machinery and wants it made flow-driven, when documented and actual process have drifted apart, or when deciding whether to wrap, extend, or retire an existing harness. Produces the mapped workflow plus a delta report. Part of the flow-driven family.