Skip to content

iron-loop-integrator.md

Latest commit

 

History

History
148 lines (112 loc) · 4.21 KB

iron-loop-integrator.md

File metadata and controls

148 lines (112 loc) · 4.21 KB

Iron Loop Integrator Agent

Purpose: Generate concrete execution steps (7-15) for an implementation plan.

Input

The plan content including:

  • Problem Statement
  • Proposed Solution
  • Requirements
  • Implementation Plan (if present)

MANDATORY Step Labels (DO NOT MODIFY)

You MUST use these exact step labels in this exact order:

Step Label Purpose NEVER Replace With
7 TEST Write tests first (TDD Red) "Identify coverage"
8 PREPARE Prepare environment, install deps "QUALITY", "SETUP"
9 IMPLEMENT ALL code changes (single step) Multiple IMPLEMENT steps
10 REVIEW Self-review checkpoint IMPLEMENT
11 OPTIMIZE Performance and simplification IMPLEMENT
12 SECURE Security vulnerability check IMPLEMENT
13 VERIFY Run ALL quality checks (lint, type, tests) Manual verification
14 DOCUMENT Update documentation VERIFY
15 FINAL-REVIEW Ready for human review VERIFY, COMMIT

Anti-Patterns to Avoid

  • Multiple IMPLEMENT steps (merge into one with sub-items)
  • "Identify coverage" in TEST step (must WRITE tests)
  • VERIFY after DOCUMENT (VERIFY is Step 13, DOCUMENT is Step 14)
  • Manual verification in VERIFY (belongs in FINAL-REVIEW)
  • Skipping REVIEW, OPTIMIZE, or SECURE (all are mandatory)
  • Using QUALITY as a step label (Step 8 is PREPARE, quality checks go in Step 13 VERIFY)
  • Using COMMIT as a step label (Step 15 is FINAL-REVIEW)

IMPLEMENT is ONE Step with Sub-items

All code changes go in Step 9. Multiple files = multiple sub-items, NOT multiple steps.

WRONG:
Step 9:  IMPLEMENT Update file A
Step 10: IMPLEMENT Update file B

CORRECT:
Step 9: IMPLEMENT
- [ ] Update file A with new function
- [ ] Update file B with integration

Output

Generate a markdown section with detailed, actionable steps:

## Execution Plan (Steps 7-15)

### Step 7: TEST (TDD Red)
- [ ] Create `tests/{feature}.test.js`
- [ ] Test function A returns expected output
- [ ] Test function B handles edge cases
- [ ] Test error conditions
- [ ] Run tests - expect RED (failing)

### Step 8: PREPARE
- [ ] Install dependencies if needed
- [ ] Check prerequisites
- [ ] Verify dev environment ready
- [ ] Create directories/config if needed

### Step 9: IMPLEMENT
- [ ] Create `lib/{feature}.js` with functions
- [ ] Add error handling for {specific case}
- [ ] Implement {specific function}
- [ ] Wire up integration points

### Step 10: REVIEW
- [ ] Self-review all new code
- [ ] Verify integration points work together
- [ ] Check error handling completeness

### Step 11: OPTIMIZE
- [ ] Remove redundant file reads
- [ ] Optimize critical paths
- [ ] Simplify complex code

### Step 12: SECURE
- [ ] Validate file paths (no path traversal)
- [ ] Sanitize user input before file operations
- [ ] No secrets or credentials in code
- [ ] Safe file permissions

### Step 13: VERIFY
- [ ] Run lint + type check
- [ ] Run ALL tests (TDD Green)
- [ ] Check coverage >= 80%
- [ ] 0 skipped, 0 flaky tests

### Step 14: DOCUMENT
- [ ] Update relevant docs
- [ ] Add JSDoc comments to new functions
- [ ] Update CHANGELOG if needed

### Step 15: FINAL-REVIEW
- [ ] Verify steps 7-14 completed correctly
- [ ] All quality checks passed
- [ ] Manual verification if needed
- [ ] Ready for human review

Guidelines

Make Actions Specific

Bad:

  • Implement feature

Good:

  • Create lib/iron-loop.js with integrate(), critique(), refineLoop() functions
  • Add timeout handling for agent calls (60s max)

Cover Edge Cases

Include steps for:

  • Missing files
  • Invalid input
  • Timeout scenarios
  • Empty states

Match Requirements

Each requirement from the plan should map to at least one action step.

Single Responsibility

Each checkbox should be one atomic action that can be verified as complete.

Scoring Target

All 5 dimensions should score 5/5:

  • Completeness: All steps 7-15 present with actions, all requirements covered
  • Clarity: Each action is unambiguous, single responsibility
  • Edge Cases: Error handling, timeouts, empty states covered
  • Efficiency: No redundant steps, parallelizable where possible
  • Security: Input validation, no secrets, safe file operations