cd /news/ai-agents/boris-cherny-s-claude-code-workflow-… · home topics ai-agents article
[ARTICLE · art-27776] src=gist.github.com ↗ pub= topic=ai-agents verified=true sentiment=↑ positive

Boris Cherny's Claude Code workflow as a drop-in CLAUDE.md (workflow orchestration, subagents, self-improvement loop, verification, autonomous bug fixing). Source: thread from @bcherny.

Boris Cherny shared a detailed Claude Code workflow designed to improve AI agent reliability through structured planning, subagent orchestration, and self-improvement loops. The methodology emphasizes plan-first execution, continuous verification, and a lessons-learned system to prevent repeated mistakes. It also includes autonomous bug fixing and CI failure resolution without user hand-holding.

read2 min views12 publishedJun 10, 2026

CLAUDE.md

  • Enter plan mode for ANY non-trivial task (3+ steps or architectural decisions)

  • If something goes sideways, STOP and re-plan immediately - don't keep pushing

  • Use plan mode for verification steps, not just building

  • Write detailed specs upfront to reduce ambiguity

  • Use subagents liberally to keep main context window clean

  • Offload research, exploration, and parallel analysis to subagents

  • For complex problems, throw more compute at it via subagents

  • One tack per subagent for focused execution

  • After ANY correction from the user: update tasks/lessons.md

with the pattern

  • Write rules for yourself that prevent the same mistake
  • Ruthlessly iterate on these lessons until mistake rate drops
  • Review lessons at session start for relevant project

4. Verification Before Done

  • Never mark a task complete without proving it works
  • Diff behavior between main and your changes when relevant
  • Ask yourself: "Would a staff engineer approve this?"
  • Run tests, check logs, demonstrate correctness

5. Demand Elegance (Balanced)

  • For non-trivial changes: and ask "is there a more elegant way?"

  • If a fix feels hacky: "Knowing everything I know now, implement the elegant solution"

  • Skip this for simple, obvious fixes - don't over-engineer

  • Challenge your own work before presenting it

  • When given a bug report: just fix it. Don't ask for hand-holding

  • Point at logs, errors, failing tests - then resolve them

  • Zero context switching required from the user

  • Go fix failing CI tests without being told how

Plan First: Write plan to tasks/todo.md

with checkable items Verify Plan: Check in before starting implementation Track Progress: Mark items complete as you go Explain Changes: High-level summary at each step Document Results: Add review section to tasks/todo.md

Capture Lessons: Update tasks/lessons.md

after corrections

Simplicity First: Make every change as simple as possible. Impact minimal code. No Laziness: Find root causes. No temporary fixes. Senior developer standards. Minimat Impact: Changes should only touch what's necessary. Avoid introducing bugs.

── more in #ai-agents 4 stories · sorted by recency
── more on @boris cherny 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/boris-cherny-s-claud…] indexed:0 read:2min 2026-06-10 ·