Agent skill · operations · sickn33
ai-loop
Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.
Why this skill is useful
Adds a structured workflow for development cycles that includes explicit phases and human approval gates, which the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
AI-Loop Skill Overview The ai-loop skill structures a bounded development cycle for agentic workflows. By dividing the process into distinct planning (Spec), implementation (Build), and validation (Review) phases, it helps an agent build and correct scoped code changes while keeping requirements, risk gates, and stop conditions explicit. When to Use This Skill Use when you need a feature built from scratch or heavily modified, and you want the agent to handle the lifecycle (specification, implementation, and verification) inside one clearly bounded workflow. Use when working with isolated components, modules, or features that have well-defined scopes and constraints. Use when the user asks for a complete development pass but the work still has clear success criteria, a reasonable verification path, and no unresolved safety or product decisions. How It Works This skill executes a controlled development loop composed of three phases: Spec, Build, and Review. When invoked, the agent moves through those phases until the scoped requirements pass verification, a stop condition is reached, or human approval is needed. Before starting, define: The maximum number of build-review iterations. The verification commands or manual checks that count as evidence. The actions that require explicit approval, such as destructive commands, production changes, external service writes, or broad architectural pivots. Phase 1: Spec (Planning) 1. Reuse the current request, accepted plan and existing artifacts. Ask only for essential missing scope or acceptance criteria; do not repeat answered questions. 2. Do not start building yet. 3. When you have enough information, use the existing specification or, when needed, save a scoped new one at specs/<feature-name>.md without overwriting user work. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/ai-loop--b08a9c