Thread Truncated (Cap Enforced)
Only the first 20 tweets are unrolled into slides to ensure reliable PDF exporting and high server performance.
Canvas & Ratio
Choose your destination platform format
Layout Template
Choose a content structure for your slides
Preset Themes
Typography & Sizing
Brand Kit Customization
AGENCYConfigure brand assets for headers & footers
Outro Slide CTA
Customize your closing call-to-action slide
Background Pattern
Build Your Carousel
Drag and drop any post card below onto a slide, or use the quick buttons to insert content/images instantly!
Loop engineering is often explained in abstract terms.
Here is my concrete, current, and pragmatic implementation in a nutshell.
# <b>What is loop engineering?</b>
Definitions of loop engineering differ in some details, but the common building blocks seem to be these:
1. <b>Sub-agents</b>: Multiple specialized agents working together. One agent does the work, another verifies it independently, and a third one keeps the big picture and focuses on the goal.
1. <b>Worktrees</b>: Isolated workspaces, typically Git worktrees, that let multiple agents work in parallel on the same repository without file conflicts or overwriting each other's changes.
1. <b>State</b>: Persistent storage outside any single conversation, for example `STATE.md` or issue boards. It tracks what is done and what is next. This is essential for long-running or multi-cycle loops.
1. <b>Skills</b>: Persistent, codified instructions, usually in files like `SKILL.md`. They capture conventions, standards, and reusable workflows, preventing agents from re-deriving context every session.
1. <b>Plugins and connectors</b> (often via MCP): Integrations that connect the agent to real external tools like issue trackers, PR systems, or databases. This allows the agent to act rather than just suggest changes.
1. <b>Automations**</b> (scheduling/triggers): Scheduled or event-driven processes that discover tasks, triage work, and initiate execution. Examples are cron jobs, `/loop`, or GitHub Actions.
# <b>My pragmatic setup</b>
## <b>Sub-agents</b>
I use SwarmForge by @unclebobmartin, which brings the idea of different roles, realized as separate agents.
I have an Architect, which prepares the plan, an Implementer, which only changes the production code, and a Verifier, which checks the result and writes the tests. This splits the responsibilities of planning, coding, and verification.
Furthermore, I have instructions that tell agents to use sub-agents for detailed analysis or research. For example, my Architect instructions include this:
> <b>## Research </b>If you require details from the code, do not read it directly. Use sub-agents instead.
GitHub Copilot then seems to spawn temporary sub-agents automatically for different tasks, such as analysis and verification of details. When I watch my team working, I see those temporary sub-agents being used quite a bit.
## <b>Worktrees</b>
SwarmForge provides dedicated workspaces for each role or agent.