$git clone https://github.com/anombyte93/atlas-session-lifecycleSession lifecycle management for Claude Code — persistent memory, soul purpose, reconcile, harvest, archive
| 1 | # Atlas Session Lifecycle |
| 2 | |
| 3 | [](https://github.com/anombyte93/atlas-session-lifecycle/releases) [](https://opensource.org/licenses/MIT) [](https://github.com/anombyte93/atlas-session-lifecycle/stargazers) [](https://github.com/anombyte93/atlas-session-lifecycle/commits/main) [](https://github.com/anombyte93/atlas-session-lifecycle/issues) |
| 4 | |
| 5 | Persistent project memory and session lifecycle management for Claude Code. |
| 6 | |
| 7 | > **Featured in**: [I just delivered on a $30,000 contract thanks to Claude Code](https://www.reddit.com/r/ClaudeAI/comments/1r0n1qz/i_just_delivered_on_a_30000_contract_thanks_to/) (r/ClaudeAI) |
| 8 | |
| 9 | --- |
| 10 | |
| 11 | ## Install |
| 12 | |
| 13 | ```bash |
| 14 | curl -fsSL https://raw.githubusercontent.com/anombyte93/atlas-session-lifecycle/main/install.sh | bash |
| 15 | ``` |
| 16 | |
| 17 | Then run `/start` in any Claude Code project. |
| 18 | |
| 19 | --- |
| 20 | |
| 21 | ## What It Does |
| 22 | |
| 23 | Claude Code has no persistent memory between sessions. Every new conversation starts from zero. This creates three compounding problems: |
| 24 | |
| 25 | - **No persistent memory** -- Context, decisions, and progress are lost between sessions. You re-explain the same things every time. |
| 26 | - **Project sprawl** -- Files accumulate at the project root with no organization. Scripts, docs, configs, and logs pile up across sessions. |
| 27 | - **No lifecycle management** -- Projects have goals, but no mechanism to track progress, verify completion, or transition to new objectives. |
| 28 | |
| 29 | `/start` solves all three with a structured five-file memory bank, automatic file organization, and a soul purpose lifecycle that tracks your project from inception through completion. |
| 30 | |
| 31 | --- |
| 32 | |
| 33 | ## How It Works |
| 34 | |
| 35 | `/start` auto-detects which mode to run based on directory state: |
| 36 | |
| 37 | ``` |
| 38 | /start |
| 39 | | |
| 40 | +-- session-context/ exists? --> Reconcile Mode |
| 41 | | +-- Validate & repair session files |
| 42 | | +-- Refresh CLAUDE.md via /init |
| 43 | | +-- Self-assess soul purpose status |
| 44 | | +-- Offer: Continue / Close / Redefine |
| 45 | | +-- Harvest learnings on closure |
| 46 | | |
| 47 | +-- No session-context/ -------> Init Mode |
| 48 | +-- Capture soul purpose |
| 49 | +-- Bootstrap 5-file memory bank |
| 50 | +-- Organize root files |
| 51 | +-- Generate CLAUDE.md |
| 52 | +-- Onboard Ralph Loop |
| 53 | ``` |
| 54 | |
| 55 | ### Init Mode (first run) |
| 56 | |
| 57 | Triggered when `session-context/` does not exist. |
| 58 | |
| 59 | - Captures your project's **soul purpose** -- the single objective this project exists to achieve |
| 60 | - Detects environment (git status, existing files, tech stack) |
| 61 | - Bootstraps `session-context/` with 5 memory bank files from immutable templates |
| 62 | - Scans root-level files and proposes an organization map (scripts, docs, config, logs) |
| 63 | - Generates or updates `CLAUDE.md` with project structure and governance sections |
| 64 | - Onboards Ralph Loop (automatic, manual, or skip) |
| 65 | |
| 66 | ### Reconcile Mode (returning) |
| 67 | |
| 68 | Triggered when `session-context/` already exists. |
| 69 | |
| 70 | - Validates and repairs session files from templates if corrupted |
| 71 | - Runs Claude's `/init` to refresh `CLAUDE.md` from current codebase state |
| 72 | - Reads soul purpose and active context to understand where you left off |
| 73 | - Self-assesses soul purpose completion (clearly incomplete, probably complete, uncertain) |
| 74 | - Presents lifecycle decision: **Continue**, **Close**, or **Redefine** soul purpose |
| 75 | - Harvests durable knowledge on closure -- promotes decisions, patterns, and troubleshooting entries |
| 76 | |
| 77 | ### Capability Inventory |
| 78 | |
| 79 | When `/start` runs in Reconcile mode (or when you run `/sync --full`), it generates a comprehensive capability inventory: |
| 80 | |
| 81 | - **MCP Tools**: All available tools with test coverage status |
| 82 | - **Security Claims**: Security-related features needing verification |
| 83 | - **Feature Claims**: What the project claims vs what's tested |
| 84 | - **Test Gaps**: Untested code identified by priority |
| 85 | |
| 86 | The inventory lives in `session-context/CLAUDE-capability-inventory.md` and is used by `/research-before-coding` to identify what needs validation testing. Results are cached based on git HEAD, so regeneration only happens when your code changes. |
| 87 | |
| 88 | ### Stepback (bundled skill) |
| 89 | |
| 90 | Also included: `/stepback` -- a strategic reassessment protocol for when debugging goes sideways. If you've hit the same error after 2+ fix attempts, `/stepback` forces you to zoom out: |
| 91 | |
| 92 | 1. Inventory all fix attempts and their assumptions |
| 93 | 2. Find the common thread across failures |
| 94 | 3. Research the architecture (mandatory Perplexity queries) |
| 95 | 4. Test the broadest hypot |