exodus

Name: exodus
Availability: InStock
Author: GadaaLabs

Execute planned tasks in a fresh isolated session with strict checkpointing.

67|10|Updated Apr 12, 2026

Search Tags:#workflow #planning #isolation #blueprint #vault #seal #exodus

Ready to run

npx skills add https://github.com/GadaaLabs/claude-code-on-steroids --skill exodus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: exodus
Source: https://github.com/GadaaLabs/claude-code-on-steroids/tree/main/skills/exodus
Command: npx skills add https://github.com/GadaaLabs/claude-code-on-steroids --skill exodus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

EXODUS — An exodus is a deliberate departure into clean, uncharted territory — leaving all baggage behind. When invoked: loads a written plan into a completely fresh session with zero context inherited from the current conversation, executes each task exactly as specified, stops on any blocker, and hands off to SEAL when done.

Core Features & Use Cases

Fresh session per plan to avoid context pollution and ensure clean execution.
Deterministic task execution with strict checkpointing, blocker reporting, and per-task verification.
Handoff to SEAL on completion to finalize the branch and prevent manual merging.
Vault-based isolation and an optional phantom workflow for in-session planning when needed.

Quick Start

Load a plan file, run VAULT to set up an isolated workspace, review the plan, then execute tasks one by one until completion.

Frequently Asked Questions about exodus

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

FAQPage Schema

How do I execute a multi-step plan in an isolated session to prevent context leakage?▼

Executing a multi-step plan in an isolated session requires loading a blueprint-generated plan file into a pristine workspace. This prevents context pollution by ensuring zero context inheritance from previous conversations, enforcing deterministic task execution with strict checkpointing and per-task verification.

What is the best way to handle blockers during stepwise task execution?▼

Handling blockers during stepwise task execution involves stopping immediately upon encountering any issue within the isolated session. The workflow pauses deterministic execution, reports the blocker for review, and waits for resolution before proceeding with the remaining planned tasks.

Does strict checkpointing work for high-stakes plans with zero context inheritance?▼

Strict checkpointing works effectively for high-stakes plans by verifying each task exactly as specified within a fresh session. Zero context inheritance ensures the execution environment remains pristine, guaranteeing deterministic outcomes and preventing pollution from prior conversational baggage.

How do I set up a vault-based workspace for pristine task execution?▼

Setting up a vault-based workspace for pristine task execution involves running a vault setup process to create an isolated environment. This workspace loads your written plan, ensures strict isolation from current conversation context, and facilitates stepwise reviews during execution.