Skill

iterations

Tracked iteration cycles for reducing failures. Number iterations sequentially, record state before/after, commit atomically per fix. Use when iteratively reducing test failures, fixing bugs in cycles, or any work requiring tracked progress across multiple attempts.

npx claudepluginhub ctoth/protocols-plugin --plugin protocols

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Use when: iteratively reducing failures, fixing bugs in cycles, any work requiring tracked progress across multiple attempts.

SKILL.md

Similar Skills

cache-components

139.4k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

pdf

131.6k

Processes PDFs: extracts text/tables/images, merges/splits/rotates pages, adds watermarks, creates/fills forms, encrypts/decrypts, OCRs scans. Activates on PDF mentions or output requests.

11 files

document-skills

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 23, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Iteration Protocol

Use when: iteratively reducing failures, fixing bugs in cycles, any work requiring tracked progress across multiple attempts.

Structure

reports/ iteration-log.md # Running summary iterations/ 001/ start.json # State at iteration start end.json # State at iteration end analysis.md # What was attempted clusters/ # If working on multiple fixes cluster-a/ fix.md verification.json

Iteration Tracking

Number iterations sequentially: 001, 002, etc.

Critical rule: If failures increase from previous iteration, STOP and diagnose before proceeding.

Per-Iteration Workflow

Record starting state -> start.json

Analyze failures -> analysis.md

Select targets (2-3 unrelated issues max)

For each target:

Attempt fix
Verify (test must pass)
If regression -> revert, document, move on
If success -> commit immediately

Record ending state -> end.json

Update iteration-log.md

Repeat

State JSON Format

{ "timestamp": "ISO8601", "total": 100, "pass": 85, "fail": 15, "skip": 0 }

iteration-log.md Format

# Iteration Log ## 001 - [date] - Start: 15 failures - Targets: [list] - Result: 12 failures (-3) - Commits: [hashes] ## 002 - [date] - Start: 12 failures - Targets: [list] - Result: 14 failures (+2) WARNING REGRESSION - Action: Reverted, investigating...

Commit Protocol

One atomic commit per fix, immediately after verification passes.

fix(<component>): iteration {N} - <brief description> Fixes: <what was wrong> Tests: <what now passes>

Rules

Never batch multiple fixes into one commit

Never proceed if failure count increased

Always verify before committing

Always record state before and after

Keep iteration-log.md updated as you go

Iteration Protocol

Use when: iteratively reducing failures, fixing bugs in cycles, any work requiring tracked progress across multiple attempts.

Structure

reports/
  iteration-log.md          # Running summary
  iterations/
    001/
      start.json            # State at iteration start
      end.json              # State at iteration end
      analysis.md           # What was attempted
      clusters/             # If working on multiple fixes
        cluster-a/
          fix.md
          verification.json

Iteration Tracking

Number iterations sequentially: 001, 002, etc.

Critical rule: If failures increase from previous iteration, STOP and diagnose before proceeding.

Per-Iteration Workflow

Record starting state -> start.json
Analyze failures -> analysis.md
Select targets (2-3 unrelated issues max)
For each target:
- Attempt fix
- Verify (test must pass)
- If regression -> revert, document, move on
- If success -> commit immediately
Record ending state -> end.json
Update iteration-log.md
Repeat

State JSON Format

{
  "timestamp": "ISO8601",
  "total": 100,
  "pass": 85,
  "fail": 15,
  "skip": 0
}

iteration-log.md Format

# Iteration Log

## 001 - [date]
- Start: 15 failures
- Targets: [list]
- Result: 12 failures (-3)
- Commits: [hashes]

## 002 - [date]
- Start: 12 failures
- Targets: [list]
- Result: 14 failures (+2) WARNING REGRESSION
- Action: Reverted, investigating...

Commit Protocol

One atomic commit per fix, immediately after verification passes.

fix(<component>): iteration {N} - <brief description>

Fixes: <what was wrong>
Tests: <what now passes>

Rules

Never batch multiple fixes into one commit
Never proceed if failure count increased
Always verify before committing
Always record state before and after
Keep iteration-log.md updated as you go