Twitter/X

@code_rams used Claude Code's dynamic 'workflow' feature to orchestrate a 14-page…

2026-05-28 · 19:13 UTC ·@code_rams ·1 min read

Brief

@code_rams used Claude Code's dynamic 'workflow' feature to orchestrate a 14-page Linkedmash product-research handover plus an Obsidian Canvas mapping of an 8-stage user journey with 4 automation agents. A single 'workflow' prompt produced the plan; PDF and Canvas agents ran in parallel with no manual setup and completed while the author was away. The author cautions input quality still matters, but says the feature collapses ~3-hour manual tasks into automated runs.

Source evidence

Used this for the first time today on a real task.

The job: a 14-page Linkedmash product research handover + an Obsidian Canvas mapping the full user journey across 8 stages and 4 automation agents.

What happened:

  1. One prompt with the word "workflow"
  2. Claude built the orchestration plan itself
  3. PDF agent and Canvas agent ran in parallel, no manual setup
  4. Both delivered while I was doing something else

The catch: the brief still matters. Garbage in, garbage out. But the plan execution is now not your problem.

For multi-output tasks that used to take 3 hours manually - this changes the ceiling.

cat (@_catwu)

Excited to share our most powerful new Claude Code feature: dynamic workflows!

Mention "workflow" in a prompt and Claude will dynamically create an orchestration plan that it strictly follows, allowing you to confidently trust that every stage happens in the right order even across 100s of agents.

— https://nitter.net/_catwu/status/2060054180379689074#m