
iterative-loop
Runs continuous AI iteration loops that repeat build-test-fix cycles until success criteria are met. Use when building features requiring test-driven refinement, implementing tasks with clear pass/fail criteria, or automating iterative improvement workflows.
- Installs
- 114
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill iterative-loop- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads iterative-loop automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Iterative Loop
Overview
The Iterative Loop skill implements continuous AI-driven development loops that persist until completion criteria are met. Inspired by the Ralph Wiggum technique, this approach enables autonomous, self-correcting development cycles where the AI sees its previous work in files and git history, iteratively improving until success.
Core Philosophy
- Iteration > Perfection - Don't aim for perfect on first try; let the loop refine the work
- Failures Are Data - Each failure provides information to improve the next attempt
- Clear Criteria - Success must be objectively measurable (tests, metrics, validations)
- Persistence Wins - Keep trying until success; the loop handles retry logic automatically
Prerequisites
- Claude Code with session management
- Clear completion criteria (tests, linting, metrics)
- Version control (git) for tracking iterations
Quick Start
Basic Iterative Development Pattern
# Define task with clear completion criteria
TASK="Implement user authentication with JWT.
Success criteria:
- All unit tests pass
- Integration tests pass
- No TypeScript errors
- Security audit passes
Output <promise>COMPLETE</promise> when all criteria met."
# Execute iterative loop (conceptual)
while ! task_complete; do
claude_execute "$TASK"
check_completion_criteria
done
AQE v3 Integration Example
# Using claude-flow hooks for iterative task
npx --no-install ruflo hooks pre-task --description "Implement auth with iteration" --taskId "auth-impl"
# Store iteration state in memory
npx --no-install ruflo memory store \
--key "iteration-auth" \
--value '{"iteration": 1, "maxIterations": 20, "criteria": "all tests pass"}' \
--namespace iterations
Step-by-Step Guide
Step 1: Define Clear Success Criteria
Essential: Every iterative task MUST have objectively measurable completion criteria.
Good Criteria Examples:
✅ All unit tests pass (npm test returns exit code 0)
✅ Coverage > 80% (coverage report shows 80%+)
✅ No TypeScript errors (tsc --noEmit returns 0)
✅ Linting passes (eslint returns 0)
✅ Performance < 100ms (benchmark shows < 100ms)
Bad Criteria Examples:
❌ "Code looks good" (subjective)
❌ "Works properly" (undefined)
❌ "Well-structured" (no measurable check)
Step 2: Structure the Task with Phases
Break complex tasks into incremental phases:
## Task: Implement User Authentication
### Phase 1: Data Layer
- Create User model with Prisma schema
- Write migration
- Run tests: `npm test -- --grep "User model"`
- Criteria: Model tests pass
### Phase 2: Service Layer
- Implement AuthService with JWT
- Add token generation/validation
- Run tests: `npm test -- --grep "AuthService"`
- Criteria: Service tests pass
### Phase 3: API Layer
- Create /auth/login endpoint
- Create /auth/register endpoint
- Run tests: `npm test -- --grep "auth API"`
- Criteria: API tests pass
### Phase 4: Integration
- End-to-end authentication flow
- Run tests: `npm test`
- Criteria: ALL tests pass
Output <promise>AUTH_COMPLETE</promise> when Phase 4 passes.
Step 3: Implement Safety Mechanisms
Always include escape conditions:
## Safety Rules
1. **Max Iterations**: Stop after 20 attempts
2. **Stuck Detection**: After 5 iterations without progress:
- Document what's blocking
- List attempted approaches
- Suggest alternative strategies
3. **Critical Errors**: Stop immediately if:
- Database corruption detected
- Security vulnerability introduced
- Breaking changes to existing features
Step 4: Execute with Verification
Each iteration should:
- Make targeted changes
- Run verification (tests, lint, build)
- Analyze results
- Plan next iteration based on feedback
# Iteration pattern
1. Read previous state (files, git log)
2. Identify remaining work
3. Implement specific change
4. Run verification suite
5. If all pass -> output completion promise
6. If failures -> analyze and continue iteration
Iterative Patterns
Pattern 1: Test-Driven Iteration
## TDD Iteration Task
1. Write failing test for [feature]
2. Implement minimal code to pass test
3. Run `npm test`
4. If test fails -> debug and fix implementation
5. If test passes -> check if more tests needed
6. Repeat until all acceptance tests pass
7. Refactor if needed
8. Output <promise>TDD_COMPLETE</promise>
Pattern 2: Bug Fix Iteration
## Bug Fix Task
1. Write failing test that reproduces bug
2. Implement fix
3. Run test suite
4. If reproduction test fails -> analyze why fix didn't work
5. If other tests fail -> fix regressions
6. If all tests pass -> output <promise>BUG_FIXED</promise>
Max iterations: 10
After 5 iterations without fix:
- Document root cause analysis
- Suggest alternative approaches
Pattern 3: Coverage Improvement Iteration
## Coverage Improvement Task
Target: 80% line coverage
1. Run coverage analysis
2. Identify uncovered code paths
3. Write test for highest-impact uncovered path
4. Run tests with coverage
5. If coverage >= 80% -> output <promise>COVERAGE_ACHIEVED</promise>
6. If coverage < 80% -> continue iteration
Max iterations: 30
Progress check: If coverage doesn't improve for 3 iterations -> analyze blockers
Pattern 4: Performance Optimization Iteration
## Performance Optimization Task
Target: Response time < 100ms
1. Run performance benchmark
2. Identify slowest operation
3. Implement optimization
4. Run benchmark again
5. If target met -> output <promise>PERF_TARGET_MET</promise>
6. If not improved -> try different approach
Max iterations: 15
Record metrics each iteration for trend analysis
Integration with Claude Flow
Memory-Enhanced Iteration
# Store iteration state
npx --no-install ruflo memory store \
--key "current-iteration" \
--value '{"task": "auth", "iteration": 5, "lastResult": "2 tests failing"}' \
--namespace iterations
# Search for similar past iterations
npx --no-install ruflo memory search \
--query "auth implementation" \
--namespace iterations
# Learn from successful completions
npx --no-install ruflo hooks post-task \
--taskId "auth-impl" \
--success true \
--quality 0.9
Swarm-Coordinated Iteration
For complex tasks, use multiple agents iterating in parallel:
# Initialize swarm for parallel iteration
npx --no-install ruflo swarm init --topology mesh --max-agents 5
# Spawn specialized iterators
Task("Iterate on unit tests", "Fix failing unit tests until all pass", "tester")
Task("Iterate on integration", "Fix integration tests until all pass", "tester")
Task("Iterate on performance", "Optimize until benchmarks pass", "performance-engineer")
Best Practices
Prompt Engineering for Iteration
Include:
- Explicit completion criteria with verification commands
- Phase-based breakdown for complex tasks
- Safety limits (max iterations)
- Progress tracking instructions
- Stuck detection and recovery procedures
Example Well-Structured Prompt:
## Task: Implement Feature X
### Success Criteria (ALL must pass):
1. `npm test` exits with code 0
2. `npm run lint` exits with code 0
3. `npm run typecheck` exits with code 0
4. No console.log statements in production code
### Phases:
1. Write failing tests
2. Implement feature
3. Fix any failures
4. Clean up and refactor
### Safety:
- Max iterations: 20
- After 10 iterations: summarize blockers
- Stop if security issues detected
### Completion:
When ALL success criteria pass, output:
<promise>FEATURE_X_COMPLETE</promise>
When to Use Iterative Loops
Ideal for:
- Well-defined tasks with measurable success
- Test-driven development
- Bug fixing with reproducible tests
- Coverage improvement
- Performance optimization
- Linting/formatting fixes
Not ideal for:
- Tasks requiring human judgment
- Design decisions
- Vague or subjective goals
- One-time operations
- Production debugging without tests
Troubleshooting
Issue: Infinite Loop / No Progress
Symptoms: Same errors repeat without improvement
Solutions:
- Increase specificity in completion criteria
- Add "stuck detection" with alternative approaches
- Lower max iterations
- Break task into smaller phases
Issue: False Completion
Symptoms: Loop ends but task not actually complete
Solutions:
- Add more verification commands
- Make completion criteria more explicit
- Add integration tests alongside unit tests
Issue: Regression in Later Iterations
Symptoms: Previously passing tests fail after new changes
Solutions:
- Add regression check step
- Use git to compare iterations
- Implement smaller, targeted changes
Related Skills
- tdd-london-chicago - TDD approaches for iterative development
- qe-iterative-loop - AQE v3 fleet-specific iteration patterns
- hooks-automation - Claude Flow hooks for automation
Resources
- Ralph Wiggum Technique - Original methodology
- Ralph Orchestrator - Orchestration tools
- Claude Code Plugins - Official plugins
Origin: Based on Ralph Wiggum plugin from claude-code repository (anthropics/claude-code) Adapted for: Agentic QE v3 with Claude Flow integration
FAQ
What does the iterative-loop skill do?
Runs continuous AI iteration loops that repeat build-test-fix cycles until success criteria are met. Use when building features requiring test-driven refinement, implementing tasks with clear pass/fail criteria, or automating iterative improvement workflows.
How do I install iterative-loop?
Run npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill iterative-loop in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/iterative-loop/ (personal) or .claude/skills/iterative-loop/ (project).
Which AI agents can use iterative-loop?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is iterative-loop safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains iterative-loop?
It is published by proffesor-for-testing in proffesor-for-testing/agentic-qe. It has 114 recorded installs.
More from proffesor-for-testing/agentic-qe
code-review-quality
proffesor-for-testing/agentic-qe
Conduct context-driven code reviews focusing on quality, testability, and maintainability. Use when reviewing code, providing feedback, or establishing review practices.
compatibility-testing
proffesor-for-testing/agentic-qe
Cross-browser, cross-platform, and cross-device compatibility testing ensuring consistent experience across environments. Use when validating browser support, testing responsive design, or ensuring platform compatibility.
api-testing-patterns
proffesor-for-testing/agentic-qe
Comprehensive API testing patterns including contract testing, REST/GraphQL testing, and integration testing. Use when testing APIs or designing API test strategies.
regression-testing
proffesor-for-testing/agentic-qe
Open the skill to read its SKILL.md instructions.
test-automation-strategy
proffesor-for-testing/agentic-qe
Open the skill to read its SKILL.md instructions.
github-code-review
proffesor-for-testing/agentic-qe
Comprehensive GitHub code review with AI-powered swarm coordination
Popular testing & qa skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
grilling
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
migrate-to-shoehorn
mattpocock/skills
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
run-train
lllllllama/rigorpilot-skills
Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.
test-driven-development
obra/superpowers
Use when implementing any feature or bugfix, before writing implementation code
finishing-a-development-branch
obra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work