TUNGKOL SA EPISODE NA ITO
Loop engineering is having a moment. Boris Cherny and Peter Steinberger have both said the same thing in public: stop prompting your coding agent turn by turn, and start designing systems that prompt it for you. This episode is the implementation guide.
I walk through the five building blocks a real loop needs: automations and hooks, git worktrees for isolating parallel agents, skills for persistent project knowledge, MCP connectors that let a loop touch your actual tools, and sub-agents that separate the agent doing the work from the agent checking it. Then I walk through a complete example, an unattended loop. I also cover what most posts on this topic skip: how many turns to let a loop run before you step in, what a loop actually costs, and the handful of decisions that should never run unattended.
Show Notes
Substack article: https://swapniltalekar.substack.com/p/loop-engineering?r=1v4ea
Tools and references:
Addy Osmani's original piece on loop engineering— https://addyosmani.com/blog/loop-engineering
Peter Steinberger's post — https://x.com/steipete/status/2063697162748260627
/goal and /loop — Claude Code's two core commands for building loops
--max-turns — flag to cap how many turns a /goal runs
Hooks: PreToolUse, PostToolUse, configured in .claude/settings.json
isolation: "worktree" — flag for spawning a sub-agent in an isolated git worktree
SKILL.md — project knowledge file; see the Skills series below for the full breakdown
MCP connectors — GitHub, Linear, Slack, database integrations
Sub-agents — defined as markdown files in .claude/agents/
Related episodes:
