Live data from Hacker News

EvanFlow – A TDD driven feedback loop for Claude Code

github.com

11–20 of 75 posts

Re: EvanFlow – A TDD driven feedback loop for Claude Code

#11
post #8

Two questions 1) Do you not feel self-conscious or weird about calling this "EvanFlow"? Seems like a lot of people these days are naming their AI tools/skills/whatever after themselves which seems self-absorbed. Either that or they hope that if their thing takes off like OpenClaw did then they'll grab the fame that comes along with it. 2) Why does your TDD flow miss the refactor step of TDD?

Ref 1, he should have called it Daughter.

No Code, surely?

Re: EvanFlow – A TDD driven feedback loop for Claude Code

#17
I’ve thought of going down the TDD model for LLMs as a way of providing constraints on their behavior. I would think that “vertical slice” TDD would encourage the LLM to start tailoring the tests to the implementation rather than establishing the invariants up front, though. I was considering “horizontal” TDD to force the agent to implement constraints before coding to them.

Re: EvanFlow – A TDD driven feedback loop for Claude Code

#18

Built this as an opinionated Claude Code development flow based on evidence based practices and what has been working for me while developing professional code. EvanFlow is a single TDD-driven loop. Say "let's evanflow this" and it walks brainstorm → plan → execute → tdd → iterate → STOP. Real checkpoints at design and plan approval. Never auto-commits, never auto-stages, never proposes integration - every git op is…

Please don’t post AI generated comments :(

Just write it yourself. I promise it’s worth it

Post reply on HN