Skip to content

baksho/ATLAS

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

5 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

ATLAS β€” Adaptive Thinking Layer for Agentic Systems

Multi-agent orchestration for Claude Code. Think before you build.

License: MIT Node.js Platform Claude Code


What Is ATLAS?

Most AI coding tools optimize for doing things faster. ATLAS optimizes for doing the right things.

ATLAS is an orchestration layer for Claude Code built around three ideas that other tools ignore:

Layer What it does Problem it solves
Socratic Layer Challenges every plan before execution with a Critic and Devil's Advocate You stop building the wrong thing
Living Document Maintains a persistent knowledge graph of your codebase across sessions Claude remembers like a teammate, not a goldfish
Confidence Layer Gates execution by certainty β€” fast when sure, careful when not Claude moves fast where it knows, slows down where it doesn't

ATLAS is not a fork of Claude Code. It hooks into Claude Code's native extension points, so you always stay on upstream.


How It Works

Every task flows through the ATLAS pipeline:

User Prompt
    β”‚
    β–Ό
[1. CONSULT]      Read .atlas/memory.json for codebase context
    β”‚
    β–Ό
[2. SOCRATIC]     Critic + Devil's Advocate challenge the plan
    β”‚
    β–Ό
[3. CONFIDENCE]   Rate plan: CERTAIN / UNCERTAIN / RISKY
    β”‚
    β”œβ”€β”€ CERTAIN   β†’ Execute immediately
    β”œβ”€β”€ UNCERTAIN β†’ Confirm assumptions first
    └── RISKY     β†’ Full Socratic summary + explicit approval
    β”‚
    β–Ό
[4. EXECUTE]      Carry out the approved plan
    β”‚
    β–Ό
[5. UPDATE]       Write what was learned to .atlas/memory.json

The Three Layers Explained

πŸ”΄ Socratic Layer

Before Claude writes a line of code, it argues with itself.

  • Critic: finds flaws, missing edge cases, hidden assumptions, test gaps
  • Devil's Advocate: proposes an alternative approach and argues for it

Only when the plan survives both agents does execution begin. For risky tasks, the findings are surfaced to you visibly β€” ATLAS never skips this step silently.

🟒 Living Document

A persistent, structured memory of your codebase stored in .atlas/memory.json.

It tracks:

  • Project stack and architecture overview
  • Critical, fragile, and stable files
  • Architecture decisions and why they were made
  • Known gotchas and open questions
  • Session-by-session history

The Living Document is powered by an MCP server (atlas-mcp) so it is queryable, updateable, and survives across every session. You never re-explain your project to Claude again.

🟑 Confidence Layer

Every significant action is rated before execution:

Level Meaning Gate
CERTAIN Files read, intent clear, reversible, no fragile areas touched Execute immediately
UNCERTAIN Assumptions being made, intent ambiguous, unfamiliar territory Surface assumptions, confirm first
RISKY Destructive action, fragile areas, wide blast radius, unresolved Critic concerns Full Socratic summary + explicit approval

Speed is earned, not assumed.


Agents

ATLAS uses three internal agents:

Agent Role
Critic Finds flaws, edge cases, and risks in a plan
Devil's Advocate Proposes alternatives and challenges the chosen approach
Confidence Rater Assesses certainty and gates execution accordingly

Commands

Command What it does
/atlas_run Full ATLAS pipeline on the current task
/atlas_init Initialize ATLAS memory for this project
/atlas_memory Show what ATLAS knows about this codebase
/atlas_challenge Socratic challenge on a plan (no execution)
/atlas_confidence Rate confidence on the current plan
/atlas_plan Strategic planning with Socratic round
/atlas_review Review recent changes or a specific file
/atlas_help Show all commands and keywords

Magic Keywords

ATLAS detects natural language and activates automatically β€” no commands required:

Say this... ATLAS activates
"build", "implement", "create" Full ATLAS pipeline
"refactor", "change", "update" Confidence check first
"plan", "think about", "design" Socratic round
"remember", "what do you know" Living Document query
"review", "check", "audit" ATLAS review
"risky", "not sure", "careful" Forced RISKY pipeline

Requirements

  • Windows (macOS/Linux support planned)
  • Node.js >= 20
  • Claude Code installed and working in VS Code
  • Claude Pro subscription or Anthropic API key

Installation

Step 1 β€” Clone the repository

Open PowerShell and run:

git clone https://github.com/baksho/ATLAS.git
cd ATLAS

Step 2 β€” Run the setup script

powershell -ExecutionPolicy Bypass -File scripts/setup.ps1

This will:

  1. Check your Node.js version
  2. Build the ATLAS MCP server
  3. Install slash commands into Claude Code
  4. Register the atlas-mcp MCP server in Claude Code's config

Step 3 β€” Copy CLAUDE.md into your project

For every project you want ATLAS to manage, copy the orchestration brain into the project root:

copy templates\CLAUDE.md C:\path\to\your\project\CLAUDE.md

Replace C:\path\to\your\project with the actual path to your project.

Step 4 β€” Open Claude Code in VS Code

  1. Open your project folder in VS Code
  2. Open Claude Code: press Ctrl+Shift+P, type Claude Code, press Enter
  3. You should see Claude Code open in the sidebar or panel

Step 5 β€” Initialize ATLAS memory for your project

In the Claude Code chat, type:

/atlas_init

ATLAS will scan your project, ask you three questions, and write .atlas/memory.json.

You are ready. ATLAS now runs automatically on every task.


Usage

Starting a new task (automatic)

Just describe what you want. ATLAS activates automatically:

build a REST API for user authentication

ATLAS will: load memory β†’ challenge the plan β†’ rate confidence β†’ wait for your approval if risky β†’ execute β†’ update memory.

Explicit commands

/atlas_plan    design the database schema for a multi-tenant SaaS app
/atlas_challenge    should I use JWT or session-based auth?
/atlas_review  src/auth.ts
/atlas_memory

Check what ATLAS remembers

/atlas_memory

Run a full pipeline manually

/atlas_run    refactor the payment processing module

Project Structure

ATLAS/
β”œβ”€β”€ agents/
β”‚   β”œβ”€β”€ critic.md              # Critic agent prompt
β”‚   β”œβ”€β”€ devils-advocate.md     # Devil's Advocate agent prompt
β”‚   └── confidence-rater.md    # Confidence Rater agent prompt
β”‚
β”œβ”€β”€ commands/
β”‚   β”œβ”€β”€ atlas:run.md           # /atlas_run command
β”‚   β”œβ”€β”€ atlas:init.md          # /atlas_init command
β”‚   β”œβ”€β”€ atlas:memory.md        # /atlas_memory command
β”‚   β”œβ”€β”€ atlas:challenge.md     # /atlas_challenge command
β”‚   β”œβ”€β”€ atlas:confidence.md    # /atlas_confidence command
β”‚   β”œβ”€β”€ atlas:plan.md          # /atlas_plan command
β”‚   β”œβ”€β”€ atlas:review.md        # /atlas_review command
β”‚   └── atlas:help.md          # /atlas_help command
β”‚
β”œβ”€β”€ skills/
β”‚   β”œβ”€β”€ socratic/SKILL.md      # Socratic round workflow
β”‚   β”œβ”€β”€ confidence/SKILL.md    # Confidence gating workflow
β”‚   β”œβ”€β”€ living-doc/SKILL.md    # Living Document read/write workflow
β”‚   β”œβ”€β”€ atlas-plan/SKILL.md    # Strategic planning workflow
β”‚   └── atlas-review/SKILL.md  # Code review workflow
β”‚
β”œβ”€β”€ mcp-server/
β”‚   β”œβ”€β”€ src/index.ts           # Living Document MCP server (TypeScript)
β”‚   β”œβ”€β”€ package.json
β”‚   └── tsconfig.json
β”‚
β”œβ”€β”€ scripts/
β”‚   └── setup.ps1              # Windows setup script
β”‚
β”œβ”€β”€ templates/
β”‚   └── CLAUDE.md              # Orchestration brain (copy to your project)
β”‚
β”œβ”€β”€ package.json
β”œβ”€β”€ LICENSE
└── README.md

The Living Document: .atlas/memory.json

ATLAS stores codebase knowledge in .atlas/memory.json in your project root. This file is updated automatically after every significant action.

Example:

{
  "project": {
    "name": "my-saas-app",
    "description": "Multi-tenant SaaS platform",
    "stack": ["TypeScript", "React", "Node.js", "PostgreSQL"],
    "entrypoints": ["src/index.ts", "src/app.tsx"]
  },
  "architecture": {
    "overview": "Monorepo with separate frontend and backend packages",
    "decisions": [
      {
        "date": "2026-04-01",
        "decision": "Use JWT for auth",
        "reason": "Stateless, scales across multiple servers"
      }
    ]
  },
  "files": {
    "critical": ["src/index.ts", "src/db/schema.ts"],
    "fragile": ["src/auth/tokens.ts", "src/payments/stripe.ts"],
    "stable": ["src/utils/logger.ts"]
  },
  "knowledge": {
    "known_gotchas": ["Stripe webhooks must be verified before processing"],
    "open_questions": ["Should we cache user permissions in Redis?"]
  }
}

Add .atlas/ to your .gitignore if you do not want to commit this file, or commit it to share context with your team.


Roadmap

  • macOS and Linux support
  • Standalone CLI (tool-agnostic: works with Codex CLI, Gemini CLI, and others)
  • Living Document visualization (web UI to browse memory graph)
  • Team memory sharing (shared .atlas/memory.json via git)
  • Agent learning β€” extract reusable patterns from sessions automatically

Philosophy

ATLAS is built on one belief: the bottleneck in AI-assisted development is not speed, it is judgment.

Other orchestration tools make Claude faster. ATLAS makes Claude more thoughtful. A plan challenged and verified before execution is worth ten plans executed at full speed in the wrong direction.


Contributing

Contributions are welcome. Please open an issue before submitting a pull request so we can discuss the change first.


License

MIT Β© Baksho

About

A multi-agent orchestration plugin for Claude Code that challenges plans before execution (Socratic Layer), remembers your codebase across sessions (Living Document), and gates execution by confidence level. Build the right thing, not just the fast thing.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors