← ClaudeAtlas

iteratinglisted

Multi-conversation methodology for iterative stateful work with context accumulation. Use when users request work that spans multiple sessions (research, debugging, refactoring, feature development), need to build on past progress, explicitly mention iterative work, work logs, project knowledge, or cross-conversation learning.
oaustegard/claude-skills · ★ 124 · Code & Development · score 84
Install: claude install-skill oaustegard/claude-skills
# Iterating Maintain context across multiple sessions by persisting state in Work Logs. ## Environment Detection Detect environment and load appropriate reference: ```bash if [ "$CLAUDE_CODE_REMOTE" = "true" ]; then # Claude Code on the Web (CCotw) - writes to GitHub # Read: references/ccotw-environment.md elif [ -n "$CLAUDE_CODE_REMOTE" ]; then # Claude Code CLI - writes to local filesystem # Read: references/codecli-environment.md elif [ -x "$(command -v osascript)" ] && [ -d "/Applications/Claude.app" ]; then # Claude Desktop - may write to disk OR output for download # Read: references/desktop-environment.md else # Claude.ai (web/chat/native app) - outputs for download # Read: references/chat-environment.md fi ``` See environment-specific reference for persistence and retrieval details. ## Critical: Checkpoint Pattern **The iterating skill enforces a checkpoint-and-save pattern to prevent work loss:** 1. **Create/Update WorkLog** → Output for user → **STOP** 2. User saves WorkLog to project knowledge (survives conversation limits) 3. User says "continue" (same or new conversation) 4. **Make incremental progress** on ONE item → Update WorkLog → **STOP** 5. Repeat **Why this matters:** - Prevents token exhaustion mid-task - Survives 5-hour conversation limits - Allows user to review progress before continuing - Creates natural save points - Enables work across multiple conversations **NEVER skip the STOP step** - going "full waterfall" defeats the