ultragoal

Multi-step workflow goals persist across sessions by splitting a brief into ordered stories and saving ledger artifacts under a local directory. This ensures progress continuity even after restarting Claude Code sessions or switching worktrees.

Ledger checkpointing for long-running Claude Code tasks is the process of recording progress events with evidence. It allows you to save your current state, resume the next story, and enforce a final quality gate before completion.

To enforce a quality gate for the final step of a multi-step workflow, use a goal orchestration tool that checks for a clean quality gate on the last story. You repeatedly complete goals and record checkpoints until the final gate passes.

Claude Code session goal orchestration works across different worktrees when using a durable ledger system. By persisting plan and ledger artifacts locally, the workflow state remains accessible and resumable regardless of the active worktree.

To create ordered goals from a brief file for Claude Code, run the goal creation command with your brief file or inline goals. The system splits the brief into sequential stories and persists them for the active agent to process.

Session-only Claude Code goals disappear on restart because they are stored in active memory rather than a durable format. Without ledger checkpointing to persist artifacts, the workflow state cannot transfer to a new session.