iterate

Orchestrates unattended delivery cycles of board review, agent waves, CI watching, and PR merging.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/diy-accounting-uk/submit.diyaccounting.co.uk --skill iterate-diy-accounting-uk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: iterate
Source: https://github.com/diy-accounting-uk/submit.diyaccounting.co.uk/tree/main/.claude/skills/iterate
Command: npx skills add https://github.com/diy-accounting-uk/submit.diyaccounting.co.uk --skill iterate-diy-accounting-uk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating a multi-step software delivery cycle by hand—reading the work board, dispatching sub-agent batches, watching CI, merging PRs, and repeating—is repetitive and error-prone. This Skill runs that entire loop unattended until no machine-only work remains on the board. ## Core Features & Use Cases - Autonomous delivery loop: Runs the board → wave → watch → auto-merge → board cycle under /loop until no machine-only row in state ready remains. - Wave orchestration: Dispatches isolated sub-agent batches on one branch and one PR, sized by file contention, SSO session window, and model tier (Haiku/Sonnet/Opus). - CI watch and merge gating: Arms a CI monitor, diagnoses failures from run logs, applies fixes on the same batch branch, and merges PRs one at a time after re-reading every gate. - Use Case: An operator says "iterate" before stepping away; the Skill clears every startable board row, merging each wave's PR and reporting per-cycle results, stopping only when nothing can start within the SSO window. ## Quick Start Say "iterate" or "run the cycle" to start the unattended delivery loop until the board is clear.

Frequently Asked Questions about iterate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an unattended delivery cycle with sub-agents?▼

Invoke the iterate skill by saying "iterate" or "run the cycle". It starts a loop that reads the board, dispatches one wave of isolated sub-agent batches on a single branch, watches CI, merges the PR, and repeats until no machine-only row is startable.

How are sub-agent batches sized and assigned to models?▼

Batches fill until file contention stops them, with one agent per board row and rows sharing files combined into one brief. Haiku handles one-file mechanical changes, Sonnet handles bounded changes against existing patterns, and Opus is reserved for design work a Sonnet can then build.

What happens when the AWS SSO session expires during a cycle?▼

The skill checks the SSO token with aws sts get-caller-identity before starting and treats the 8-to-12-hour window as the budget for every wave. When a render finds the token expired, it reports this on the prod line and prints the aws sso login command once.

How does the skill handle CI failures on a batch branch?▼

Failures are diagnosed from the run's own job logs, with all failures in the run gathered before any fix. The fix rides on the same batch branch as a second commit, and pushes are never made while a deploy of that branch is in flight.

When does the iterate loop stop running?▼

The loop stops when nothing is startable and the next unblock falls past the SSO window or on another day. It sends one push notification with the outcome, schedules a wakeup with stop, and halts any active Monitor.

Which operations require the human operator instead of the skill?▼

Destructive or privileged commands—git worktree remove, git branch -D, git push --delete, ruleset or Actions-settings writes, AWS writes outside workflows, and Cognito or Step Functions invocations—are printed as fenced blocks with a ! prefix for the operator to run.