loop-engineering
Skill30 starsChanged 4 days agoApache-2.0View on GitHub
Implements 3-Tier Adaptive SDLC state machines, capability-gated discovery, target-project AGENTS.md bootstrapping, isolated parallel worker execution (Disjoint Mode A / Git Worktree Mode B), and 3-loop self-correcting review gates.
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 25 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Silent Memory Restore: Read context/memory/MEMORY.md if present (~500 tokens), loading architecture.md, conventions.md, or …
“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Loop Engineering Skill
Overview
This skill orchestrates multi-agent execution loops, isolated parallel worker topologies, and the 3-Tier Adaptive SDLC State Machine. It coordinates capability-gated specialist dispatch, target-project AGENTS.md (<= 90 lines) bootstrapping, collision-free parallel builds (Disjoint File Mode A and Git Worktree Mode B), and deterministic max 3-iteration self-correction gates.
When to Use
Trigger Scenarios
- Triage and execution of multi-agent workflows across Tier 1 (Fast-Track), Tier 2 (Standard), and Tier 3 (Mission-Critical).
- Bootstrapping or updating a concise root
AGENTS.md(<= 90 lines) in target user repositories. - Provisioning isolated git worktrees or disjoint file partitions for concurrent worker subagents.
- Running automated PR/branch audit crons and bounded self-correcting verification loops.
When NOT to Use
- Pure commit message linting: Route to
commit-expert. - Standalone manual PR review without loop orchestration: Route to
pull-request-expert.
Process
State 0: Memory Restore, Target-Project AGENTS.md Bootstrap & 3-Tier Triage
- Silent Memory Restore: Read
context/memory/MEMORY.mdif present (~500 tokens), loadingarchitecture.md,conventions.md, orlog/YYYY-MM-DD.mdonly on demand. - Target-Project
AGENTS.mdBootstrap (<= 90 lines): When operating in a target user repository that lacks a rootAGENTS.md—or when its stack, build/test commands,DESIGN.mdcontract, or architectural conventions change—bootstrap or update a concise rootAGENTS.md(<= 90 lines) using references/project-agents-template.md (1. Project Overview & Tech Stack,2. Executable Commands,3. Architecture & Coding Conventions,4. Design & Persistent Memorywired to rootDESIGN.mdandcontext/memory/MEMORY.md). - Concise
PLAN.md(<= 50 lines) & 3-Tier SDLC Triage:
| Dimension / Phase | Tier 1: Fast-Track (Low Complexity) | Tier 2: Standard (Medium Complexity) | Tier 3: Mission-Critical (Complex) |
| Typical Scope | Single-file bugfix, doc fix, typo, chore, localized refactor without public contract change | 2–4 files, new API endpoint, single UI view/widget, DB migration, non-breaking contract update | Full end-to-end feature, payment/auth flow, cross-cutting refactor, breaking public API |
| Discovery (State 1) | SKIPPED: Zero discovery artifacts authored | SELECTIVE (capability-gated): prd.md <= 70L, DESIGN.md <= 110L (+ delta <= 35L), adr-*.md <= 55L | FULL (capability-gated): prd.md <= 70L, DESIGN.md <= 110L (+ design.md <= 35L), adr-*.md <= 55L / architecture.md <= 70L |
| Interactive Alignment Gate | SKIPPED: Auto-proceeds directly to build | MANDATORY: ask_question modal approval before build | MANDATORY: Strict ask_question modal sign-off before build |
| Build & Isolation (State 2) | 1 code-implementer under Mode A (Disjoint Files) | 1..N code-implementer in parallel under Mode A (Disjoint Files) | 1..N code-implementer under Mode A or Mode B (Git Worktree Isolation if shared files touched) |
| QA & Audit (State 3 & 4) | Scoped test file (exit 0) + compliance-verifier (skips committee) | Full suite (exit 0) + docs/<feature-name>/test-matrix.md (<= 80L) + compliance-verifier (APPROVED) | Adversarial Verification Committee (capability-gated, reports <= 50L): qa-tester, critic, challenger, e2e-blackbox-tester, compliance-verifier |
| Token & Latency Impact | 70–85% token & latency savings | Balanced overhead with rigorous traceability | Maximum empirical depth & zero regression tolerance |
Multi-Agent Topologies & Isolation Modes
- Manager-Worker: Orchestrator decomposes tasks and dispatches isolated workers (
Mode Astrictly non-overlappingOwned Files, orMode BGit Worktrees when shared routers/configs are touched). Each parallel worker runs only its scoped test file during State 2 loops. - Sequential DAG: Deterministic
Plan -> Discover -> Align -> Build -> Verify -> Shipstate machine. - Adversarial Review Committee: Capability-gated Tier 3 specialists (
criticfor>= 150 LOCdiffs,challengerfor auth/payments/concurrency/untrusted input, fail-honeste2e-blackbox-testeronly when a runnable web UI exists).
Worktree Provisioning, PR Crons & 3-Loop Self-Correction Cap
- Worktree Provisioning (Mode B):
python3 ./skills/loop-engineering/scripts/run_parallel_agents.py --tasks "task1:path1" "task2:path2" - Automated Branch Review Cron:
python3 ./skills/loop-engineering/scripts/pr_cron_reviewer.py - Self-Correction Protocol (Strict 3-Loop Cap): On test or compliance failure, remediate surgically up to a maximum of 3 iterations. If still failing after 3 attempts, halt immediately and escalate a concise diagnostic report (failing traceback, 3 hypotheses tried, user decision needed).
Usage
python3 ./skills/loop-engineering/scripts/run_parallel_agents.py
python3 ./skills/loop-engineering/scripts/pr_cron_reviewer.py- Claude Code: Provision worktrees when Mode B applies and dispatch workers via
Agent(...). - Antigravity: Dispatch workers via
invoke_subagent(...)(Workspace='inherit'for Mode A,Workspace='branch'/'share'for Mode B).
Red Flags
- ❌ Concurrent workers editing overlapping files without Mode B Git Worktree isolation, or running the full test suite inside parallel worker loops.
- ❌ Over-invoking discovery specialists or adversarial committees on Tier 1 tasks (destroying 70–85% token/latency savings).
- ❌ Leaving target projects without a concise root
AGENTS.md(<= 90 lines) wired to executable commands,DESIGN.md, andcontext/memory/MEMORY.md. - ❌ Exceeding the 3-loop self-correction cap or skipping
ask_questionalignment on Tier 2 / Tier 3 tasks.
Verification
- SDLC Tier (
Tier 1Fast-Track,Tier 2Standard, orTier 3Mission-Critical) and capability-gatedInvoke / SKIPtable recorded inPLAN.md(<= 50 lines). - Target-project root
AGENTS.md(<= 90 lines) bootstrapped or updated per references/project-agents-template.md when missing or outdated. - Parallel tracks verified collision-free (Mode A disjoint files or Mode B worktrees via
run_parallel_agents.py), with 3-loop self-correction cap enforced.
References
- Target-Project AGENTS.md Template (
<= 65 lines) - Loop Engineering & Multi-Agent Orchestration Reference
Other versions31 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 31
- bojieli/ai-agent-book-projects★ 53ksame name
- bojieli/ai-agent-book★ 53ksame name
- huytieu/COG-second-brain★ 1.3ksame name
- akitaonrails/my-skills★ 283same name
- aiconnai/agentshield★ 21same name
- yoyothesheep/claude-skills★ 16same name
- sxivansx/loop-engineering★ 10same name
- Connected-Mate/fable-mindset★ 2same name
- VioletScar-Hui/Build_Great_Loop★ 2same name
- vpeetla-ai/aegisai-enterprise-agent-platform★ 2same name
21 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use aegis-gateway, deploy-vercel-render and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
vpeetla-aiSkillaegis-gateway
Integrate AegisAI gateway before tool side effects (notify, publish, deploy). Use when adding Slack/Telegram/WhatsApp notify, content publish, or any irreversible external action in VAP, AegisLoop, or ai-content-factory.
Also in 5 projects that use this
vpeetla-aiSkilldeploy-vercel-render
Deploy vpeetla-ai demos: Vercel static/Next.js frontends, Render FastAPI backends, env vars, free tier gotchas. Use when shipping demos, fixing deploy failures, or adding render.yaml / vercel.json.
Also in 5 projects that use this
HermeticOrmusSkilllanggraph-orchestration
LangGraph stateful multi-agent graphs with categorical coordination patterns and cyclic workflows. Use when building stateful AI agent systems, implementing multi-agent orchestration with conditional routing, creating cyclic workflows with persistence, or designing graph-based AI pipelines with checkpointing and human-in-the-loop patterns.
Also in 5 projects that use this
junimnjwSkillagentic-engineering
Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing.
Also in 5 projects that use this
- +8 more from vpeetla-ai
In this repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adversarial-challengerSkill
- agent-metricsSkill
- bigquery-query-optimizationSkill
- blackbox-testerSkill
- build-and-ci-gatesSkill
- cdc-scd-patternsSkill
- code-criticSkill
- code-implementerSkill
- code-smells-expertSkill
- commit-expertSkill
- compliance-verifierSkill
- context-captureSkill
- context-restoreSkill
- database-migration-expertSkill
- design-spec-expertSkill
- documentation-expertSkill
- flutter-architecture-decisionsSkill
- flutter-performance-profilingSkill
- flutter-release-engineeringSkill
- flutter-review-checklistSkill
- flutter-senior-orchestrationSkill
- flutter-test-strategySkill
- flutter-upgrade-migrationSkill
- gcp-data-engineeringSkill
- guidelines-karpathySkill
- performance-scalabilitySkill
- product-analystSkill
- pull-request-expertSkill
- python-expertSkill
- qa-testerSkill
- refactoring-code-expertSkill
- repo-researchSkill
- security-auditSkill
- senior-architect-engineeringSkill
- senior-dev-orchestratorSkill
- sql-query-optimizationSkill
- test-driven-developmentSkill
- testing-expertSkill
- ui-ux-designerSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

