Claude Code workflows went from 5-6 hours to 20-30 minutes
Turning plan files into Claude Code workflows took 5-6 hours each. A script that converts them deterministically, and flags what can move out of the LLM, cut that to 20-30 minutes at about 20% of the tokens.
Done withClaude CodeSpotted· by HN user gojkoa· Oct 20, 2026
Result Also removed a 10-15 minute workflow construction wait
“This significantly reduced the token spend (now running at about ~20% of the token spend for workflows before) and time (from average 5-6 hours per workflow to about 20-30 minutes).”
Spotted: found in the wild. Details are as reported by the source above and have not been independently verified.
What they did
They built an orchestrator script that takes their plan-file format, which a 5-command pipeline builds up as a shared plan sitting in git, and turns it into Claude Dynamic Workflow descriptions deterministically. The same script parses the progress of the workflows to suggest what is slow and what can move out of LLM processing into deterministic tools.
How it went
This significantly reduced both the token spend, now running at about 20% of what workflows used before, and the time, from an average of 5-6 hours per workflow down to about 20-30 minutes. It also removed a 10-15 minute wait that used to happen while Claude was constructing workflows from the plans.
Try it yourself with Claude Code
Build an orchestrator script that converts your project's plan-file format into structured workflow steps for [Claude Code], then has it track progress against those steps so it can flag which parts are slow enough to move out of LLM processing and into deterministic tools (linting, scripts, tests), to cut both run time and token spend.
A starting prompt written by Agents in the Wild. Fill in the [brackets], and check what the agent does before it sends, pays for or deletes anything.
Markdown files should just open, so they asked Claude Code for a viewer. It opens instantly: faster, they say, than any other macOS app, and faster than Bitwarden's Chrome extension shows its fill menu.
Migrating a password reset flow, Claude Code and Opus produced code on par with a mid level developer. It needed close supervision throughout, and cost roughly 2 months of Pro subscription for about half a day's work.
A URL shortener side project ran on AWS. Claude Code wrote the GitHub Actions workflows for the move and fixed each failure as it came up. The writer reports zero downtime.
A 7-app monorepo needed an 8 GB memory setting and 25 seconds to typecheck. Claude Code made the changes for the move to oxlint, oxfmt and tsgo, and the team validated each step.
An inherited app on Azure, an error, and a hunt that could easily take 1-2 days by hand. With CLI access to Azure and the repo, Claude Code ran the config and network checks and found the root cause in about 45 minutes.
Running Claude Code in YOLO mode risked projects leaking tokens, so a container setup isolated each project's permissions. Typing a hotkey and a feature name, like text-to-speech streaming, got it done in five minutes.