All 4,799 reports

YesClaude · 6 Sep 2026

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)

gojkoa on Hacker News

token spend for workflows before) and time (from average 5-6 hours per workflow to about 20-30 minutes

In the thread “Ask HN: Any Software Engineers here who enjoy their AI-native dev workflow?”

Helped: Deterministic orchestration and custom linting rules reduced token spend and time.

… the latest addition is an orchestrator script that takes our plan file format and turns into Claude Dynamic Workflow descriptions deterministically, and parses the progress of the workflows so suggest what's slow and what can be moved out of LLM processing to deterministic tools. 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). It also removed the 10-15 minute wait that we had while claude was LLM constructing workflows from our plans. …