kumihimo-iteration

Kumihimo iteration — one pass

One invocation is exactly one iteration: one queue item, one verdict, one commit, one journal entry. A loop re-invokes this skill for the next item. Every iteration must leave the repository committed and clean enough for the next one to start cold.

Working directory is C:\Kumihimo. Nothing outside it is written except Claude's own memory directory.

Before anything: the safety check

1. Never git push. Commits are local. Pushing publishes to the public repo and triggers CI; it happens at milestone close with Thomas's say-so, or when he asks. If a milestone completes mid-loop, propose the push in the report and keep looping.
2. Never publish to PyPI, create GitHub releases, or post anywhere.
3. Never weaken an invariant in CLAUDE.md to make an item pass. If an item and an invariant collide, the item is needs-thomas.

Step 1 — Read the state

• build/state/queue.md — the work, in order.
• build/state/journal.md — what the last few iterations did.
• build/state/loop.json — iteration counter and collision guard.

Collision guard. If loop.json has an active_session under 30 minutes old that is not this session, another loop is running — stop and say so. Otherwise claim it (session id + timestamp) and clear it when the iteration ends.

Step 2 — Pick exactly one item

Take the first item with status todo whose dependencies are all done. Do not batch. Do not skip ahead because something looks easier.

If an item is larger than one review round can hold, mark it split, write the smaller items beneath it, and take the first.

Stop conditions — end the loop, do not spin:

• No todo items remain → say the queue is drained and stop.
• Three consecutive iterations ended blocked → stop and report the pattern.
• The same item has failed verification twice across two iterations → mark it needs-thomas, write why, and stop.
• The clean tree fails uv run pytest -q before you changed anything → stop; the tree is broken and another iteration will not help.