
from atlas-session-lifecycle86
Gracefully pause, verify, or finish a work session: harvest promotable content, checkpoint progress, create PRs, and settle optional bounties before archiving.
The Session Stop skill provides a structured, safety-first workflow to pause, verify, or fully close an agent work session. It automates harvesting promotable content, writing checkpoint notes, optionally creating a save-point commit and PR, running verification gates, and (when configured) settling on-chain bounties and archiving the session. The skill enforces human confirmation and idempotency so sessions are never closed without explicit approval.
Use this skill when a user indicates they want to end or pause work — commands or phrases like "/stop", "wrap up", "finished", "pause for the day", or "verify". It covers three modes: Pause (save progress), Just Verify (run checks without closing), and Finished — Verify & Close (full harvest, PR creation, bounty settlement, and archive).
Best suited for agents integrated with Claude Code and tooling that exposes session and contract helpers (CLAUDE-style toolsets). It assumes access to project filesystem, git, and any contract settlement tooling when bounties exist.
Session stop skill for the Atlas ecosystem — handles pausing, finishing, or verifying work sessions with bounty settlement and soul purpose archiving. No bundled scripts to test. Heavily coupled to a proprietary MCP toolchain (session_*, contract_*, superpowers:*) that most users won't have, limiting practical applicability outside that ecosystem.
atlas-session MCP serversuperpowers skillsWell-structured skill with clear intent separation and user authority invariants. Narrow usefulness due to deep ecosystem coupling. No security concerns — all operations are user-confirmed and use standard tooling.
Sync (Session Save-Point)
Fast, no-interaction session sync: append session-context files and MEMORY.md, print a concise summary; optional full run builds a capability inventory.
Session Init & Lifecycle
Bootstrap and manage an agent session lifecycle: initialize project context, organize files, generate CLAUDE.md, and continue work without unnecessary narration