prd
An open-source Claude Code plugin that turns a one-line goal into a product requirements document through a PM-style interview, then breaks it into a dependency-ordered task graph and executes each task with verification.
Session lifecycle tools for Claude Code: start bootstraps context and CLAUDE.md, sync saves progress to memory files, stop wraps up and archives a session, and stepback reassesses architecture after repeated failed fixes. Includes a test spec generator.
Claude Code
$ npx -y skills add anombyte93/atlas-session-lifecycle --agent claude-code
Codex
$ npx skills add anombyte93/atlas-session-lifecycle -a codex
Cursor
$ npx skills add anombyte93/atlas-session-lifecycle -a cursor
Gemini CLI
$ npx skills add anombyte93/atlas-session-lifecycle -a gemini-cli
GitHub Copilot
$ npx skills add anombyte93/atlas-session-lifecycle -a github-copilot
OpenCode
$ npx skills add anombyte93/atlas-session-lifecycle -a opencode
Windsurf
$ npx skills add anombyte93/atlas-session-lifecycle -a windsurf
Persistent project memory and session lifecycle management for Claude Code.
Featured in: I just delivered on a $30,000 contract thanks to Claude Code (r/ClaudeAI)
curl -fsSL https://raw.githubusercontent.com/anombyte93/atlas-session-lifecycle/main/install.sh | bash
Then run /start in any Claude Code project.
Claude Code has no persistent memory between sessions. Every new conversation starts from zero. This creates three compounding problems:
/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.
/start auto-detects which mode to run based on directory state:
/start
|
+-- session-context/ exists? --> Reconcile Mode
| +-- Validate & repair session files
| +-- Refresh CLAUDE.md via /init
| +-- Self-assess soul purpose status
| +-- Offer: Continue / Close / Redefine
| +-- Harvest learnings on closure
|
+-- No session-context/ -------> Init Mode
+-- Capture soul purpose
+-- Bootstrap 5-file memory bank
+-- Organize root files
+-- Generate CLAUDE.md
+-- Onboard Ralph Loop
Triggered when session-context/ does not exist.
session-context/ with 5 memory bank files from immutable templatesCLAUDE.md with project structure and governance sectionsTriggered when session-context/ already exists.
/init to refresh CLAUDE.md from current codebase stateWhen /start runs in Reconcile mode (or when you run /sync --full), it generates a comprehensive capability inventory:
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.
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:
Invoked separately via /stepback or /atlas-session-lifecycle:stepback.
Five files in session-context/ give Claude persistent memory across sessions:
| File | Purpose |
|---|---|
CLAUDE-activeContext.md | Current session state, goals, and progress |
CLAUDE-decisions.md | Architecture decisions and rationale |
CLAUDE-patterns.md | Established code patterns and conventions |
CLAUDE-troubleshooting.md | Common issues and proven solutions |
CLAUDE-soul-purpose.md | Soul purpose definition and completion criteria |
All files use a structured entry format with timestamps, 5W1H context, git references, and potential issues.
Every project has a soul purpose -- the single objective it exists to achieve.
Define --> Work --> Reconcile --> Assess --> Close or Continue
| | |
| | +--> Harvest learnings
| | +--> Archive purpose
| | +--> Redefine (optional)
| |
| +--> Self-assess completion
| +--> Optional doubt agent verification
| +--> User decides (never AI)
|
+--> Captured during Init Mode
Key invariant: The AI never closes a soul purpose. It assesses and suggests; the user decides.
curl -fsSL https://raw.githubusercontent.com/anombyte93/atlas-session-lifecycle/main/install.sh | bash
Installs to ~/.claude/skills/start/. The SKILL.md orchestrator and session-init.py script are placed together.
curl -fsSL https://raw.githubusercontent.com/anombyte93/atlas-session-lifecycle/main/install.sh | bash -s -- --plugin
Installs to ~/.claude/plugins/atlas-session-lifecycle/ with full plugin structure including plugin.json.
git clone https://github.com/anombyte93/atlas-session-lifecycle.git
cd atlas-session-lifecycle
./install.sh
Or copy files directly:
mkdir -p ~/.claude/skills/start
cp skills/start/SKILL.md ~/.claude/skills/start/SKILL.md
cp scripts/session-init.py ~/.claude/skills/start/session-init.py
chmod +x ~/.claude/skills/start/session-init.py
mkdir -p ~/claude-session-init-templates
cp templates/* ~/claude-session-init-templates/
# Install v1 (monolithic SKILL.md, no script)
./install.sh --version v1
# Revert from v2 back to v1 (backs up v2 files first)
./install.sh --revert
# Pull latest version and reinstall
./install.sh --update
The installer records a last-checked timestamp. On each run, if more than 24 hours have passed since the last check, it queries GitHub for newer releases and prompts you to update.
Edit custom.md in the plugin root (or ~/.claude/skills/start/custom.md for skill installs) to modify /start behavior. Write plain English instructions — no code needed. The AI reads these at each lifecycle phase and follows them.
Three headings control when your instructions apply:
## During Init
- After brainstorming, always suggest a git branching strategy
- Skip file organization for monorepo projects
- Always ask about deployment target (local, cloud, edge)
## During Reconcile
- Check for uncommitted changes before assessing soul purpose
- If soul purpose mentions "API", verify endpoints are documented
- Always show a progress percentage estimate
## Always
- Keep tone direct and concise. No fluff.
- When creating session context entries, include the git branch name
- Never suggest closing a soul purpose unless all tests pass
How it works: The skill reads custom.md at specific points — during init (after session-context is bootstrapped), during reconcile (after reading context, before assessment), and always (both modes). Your instructions augment the default behavior; they don't replace the skill logic.
Examples of what you can customize:
During Init, the skill asks how Ralph Loop should operate:
The preference is stored in CLAUDE.md and respected on subsequent Reconcile runs.
v2 is a backward-compatible evolution. Your existing session-context/ files, templates, and project structure are unchanged.
The main difference: v1 was a single 867-line SKILL.md where Claude interpreted all operations from prose. v2 extracts deterministic operations into session-init.py (9 JSON-outputting subcommands), reducing SKILL.md to a slim orchestrator. The user experience is identical.
To revert at any time:
./install.sh --revert
atlas-session-lifecycle/
.claude-plugin/
plugin.json # Plugin metadata (name, version, keywords)
skills/
start/
SKILL.md # Session lifecycle orchestrator
stepback/
SKILL.md # Strategic reassessment for stuck debugging
scripts/
session-init.py # Deterministic ops (9 JSON-outputting subcommands)
custom.md # User customization hook (plain English)
templates/
CLAUDE-activeContext.md
CLAUDE-decisions.md
CLAUDE-mdReference.md
CLAUDE-patterns.md
CLAUDE-soul-purpose.md
CLAUDE-troubleshooting.md
v1/
SKILL.md # v1 monolithic skill (867 lines)
install.sh # Installer with version toggle and auto-update
README.md
LICENSE
CONTRIBUTING.md
CODE_OF_CONDUCT.md
SECURITY.md
git mv for tracked files during organization)See CONTRIBUTING.md for guidelines.
An open-source Claude Code plugin that turns a one-line goal into a product requirements document through a PM-style interview, then breaks it into a dependency-ordered task graph and executes each task with verification.
Helps you take a change from a rough idea or bug report through to a tested, reviewed result, with each step handled by a focused skill. Its skills cover pinning down domain terms, designing module interfaces, diagnosing hard bugs, and reviewing changes against your repo's coding standards.
A development methodology for coding agents that makes the agent brainstorm before building, follow plans, run parallel work and finish branches in a disciplined way. You get fewer skipped steps and more consistent results from your coding assistant.
Gives your coding agent a planning, testing and review routine to follow on every task. It plans before building, checks changes with tests, has a fresh reviewer look for regressions, and saves repeated wins as reusable skills.
Developer tools for working on the React codebase itself. Provides skills for extracting error messages, managing and debugging feature flags across release channels, running Flow type checks, and fixing lint and formatting issues before committing.
Session lifecycle tools for Claude Code: start bootstraps context and CLAUDE.md, sync saves progress to memory files, stop wraps up and archives a session, and stepback reassesses architecture after repeated failed fixes. Includes a test spec generator. Install it with the command on its page. It includes test-spec-gen, start, stepback. Its skills do not fire on their own yet. Free and open source.
Is this plugin yours?
Claim it with GitHubSubmit a pluginPromote it