Your coding agents are the engineers. Halfcycle is the rest of the team. Runs inside your own Claude Code npx halfcycle Newsletter: https://xitter.cf/t.co/lBPjEkhxE5
Joined August 2026
- Tweets246
- Following108
- Followers15
- Likes177
Pinned Tweet
Your coding agent is the engineer. Halfcycle is the rest of the team: product owner, business analyst, architect and reviewer.
In Claude Code it asks the decisions nobody made, before code. Another agent reviews the plan. One project's lessons reach your next.
npx halfcycle
The bug wasn't in any file.
One feature split between server and screen, with nothing agreeing what passes between them. Each half fine alone, broken the day they're connected. Unless the plan is checked first.
halfcycle.ai/f/07
The session that wrote your spec is the worst available reviewer of it. Not dishonest. It cannot see what it did not think of, and if you ask, it says yes.
5/ Then the build ran as a team. ADA on the store, OTTO on the Stripe receiver, NOVA on the inbox. Every task reviewed by a different agent before merge.
One review failed. It was fixed and re-checked by someone else. All of it live on the project console.
6/ The things only a person can do (create an account, capture a real event) went into the plan as tasks of their own, with steps. Everything that did not need us got built.
7/ The honest part: the specs took sixteen review rounds before the build was allowed to start. Every finding was real. Sixteen is still too many, and it is going back into the method.
The whole build, with screenshots:
halfcycle.ai/writing/introdu…
4/ Before any code, the team found six problems. None was a coding mistake.
Example: replaying a Stripe delivery would fail the handler's own signature check, because Stripe signatures expire after five minutes. Fix: Hookbox signs its forwards with its own secret.
A test that mocks one layer too high asserts nothing about the layer underneath it. The suite is green, the path never ran, and the green is doing active harm, because now there is evidence.
Halfcycle retweeted
Halfcycle is now listed in the HOL plugin registry, under Development & Workflow. Thanks @Kantorcodes for the nudge.
It runs inside Claude Code: asks the open decisions before any code, records them for every agent, and sends the plan to a reviewer that has never seen it.
npx halfcycle
hol.org/registry/plugins/hal…
Halfcycle is now listed in the HOL plugin registry, under Development & Workflow. Thanks @Kantorcodes for the nudge.
It runs inside Claude Code: asks the open decisions before any code, records them for every agent, and sends the plan to a reviewer that has never seen it.
npx halfcycle
hol.org/registry/plugins/hal…
A clear roadmap, then a backlog of half-built features.
They start as lines nobody finished deciding. Halfcycle asks the open questions first, reviews the plan before the build and the code after, and keeps your roadmap on track.
halfcycle.ai/method
Your coding agent is the engineer. Halfcycle is the rest of the team: product owner, business analyst, architect and reviewer.
In Claude Code it asks the decisions nobody made, before code. Another agent reviews the plan. One project's lessons reach your next.
npx halfcycle
Waiting months to get an MVP in front of users?
Halfcycle pins down what you're building, cuts it into pieces that can ship, and has a team of agents build them. A working prototype in days, and feedback while it can still change the plan.
halfcycle.ai
