atlas

Execute tasks with fresh context and persistent state files.

1|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/jesserathbun/atlas-plugins --skill atlas-jesserathbun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atlas
Source: https://github.com/jesserathbun/atlas-plugins/tree/main/core/skills/atlas
Command: npx skills add https://github.com/jesserathbun/atlas-plugins --skill atlas-jesserathbun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Atlas provides a robust task execution loop that preserves context between steps by using per-task sub-agents and persistent state storage.

Core Features & Use Cases

  • Fresh-context task execution with sub-agents for complex work
  • Inline execution for small edits
  • Persistent state across sessions via STATE.md, progress.txt, CLAUDE.md, AGENTS.md
  • Pause/resume across sessions

Quick Start

To start, run Atlas tasks using /atlas and let Atlas manage the TodoWrite-backed workflow.

Frequently Asked Questions about atlas

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

FAQPage Schema
How do I preserve context when automating task execution across multiple sessions?

You can preserve context by using per-task sub-agents alongside persistent state files like STATE.md and progress.txt. This approach maintains task tracking and enables pause/resume workflows across sessions.

What is fresh-context task execution with sub-agents?

Fresh-context task execution delegates complex work to sub-agents that start with a clean slate for each task. This prevents context window bloat while relying on in-repo state files to coordinate the overall workflow.

How do I set up persistent state for task tracking and workflow automation?

Persistent state is managed through in-repo files such as STATE.md, progress.txt, CLAUDE.md, and AGENTS.md. These files track execution progress and allow workflows to pause and resume reliably.

Can I use inline edits for small tasks instead of spawning sub-agents?

Yes, the workflow supports inline execution for small edits directly, while reserving sub-agent powered implementations for more complex work that requires a fresh context window.

Does TodoWrite-backed workflow automation support pause and resume?

TodoWrite-backed workflow automation supports pause and resume by storing execution state in repository files. This allows task tracking to persist across sessions and maintain progress continuity.

When should I avoid using sub-agents for task execution?

You should avoid sub-agents for small inline edits where fresh context is unnecessary. Sub-agent powered implementations add overhead, making them best suited for complex, multi-step tasks.