Mindlap
Atlas
Top

Atlas is a living playbook for AI coding agents.

It keeps a team's decisions, patterns, and practices current as the code and product change, so each agent run can use what the team has learned.

See Atlas in action.

A playbook that
keeps up with your product.

Every correction is a chance to improve the next run. Atlas turns those signals into practices your team can trust.

01 / OBSERVE

Start with what actually happens.

Atlas connects the repository with product decisions, agent sessions, pull requests, reviews, tests, and documentation.

One example: an orders export.
The code, the review, and the decision.
02 / IDENTIFY DRIFT

Find the lesson
that keeps getting lost.

Repeated mistakes, skipped checks, stale instructions. Atlas spots where the team's guidance and the code have moved apart.

“The export still needs a permission check.”
A repeated review correction.
03 / PROPOSE AN UPDATE

A small change.
A better next run.

Atlas proposes the smallest useful update: a skill, rule, policy, prompt, document, check, or hook. Grounded in the evidence that prompted it.

+ Update skills/orders-export.md
Read permissions. Reuse the helper. Run checks.
04 / APPROVE & GOVERN

Your team's judgment.
Always in the loop.

People decide what changes, who owns it, where it applies, and how it's enforced. Exceptions have owners and expiry dates.

Owner: Orders platform
Scope: exports · Enforcement: required check
05 / VERIFY

Better guidance
needs real proof.

Relevant tests, checks, reviews, and future agent runs show whether the practice works. An instruction is only useful when it changes the outcome.

Required proof: export + permission tests
Connect the practice to its evidence.
06 / MAINTAIN

The product changes.
The playbook changes with it.

When code moves or decisions evolve, Atlas detects drift, suggests updates, and helps retire guidance that no longer belongs.

Helper refactored → revisit the export skill
Keep the lesson. Update the instructions.

Knowledge your agents
can actually use.

A focused change, right where your team works. Explore an example of what Atlas could propose for an orders export.

orders-service / atlas changes
Skills, rules, and proof.
Connected to the same decision.

skills/orders-export.md

PROPOSED
# Add an export safely

+ Read rules/permissions.md
+ Reuse the Orders table export helper
+ Run: pnpm test export
+ Run: pnpm test permissions
+ Ask Orders platform if scope changes

Proof required before calling this done:
+ Export test passes
+ Permission test passes
Linked to the export review and permission policy.

Atlas, clearly explained

Common questions about Atlas

What is Atlas?

Atlas is a living team playbook for AI coding agents. It keeps a team’s decisions, patterns, and practices connected to the code and current as the product changes.

Who is Atlas for?

Atlas is for engineering teams using AI coding agents that want shared guidance grounded in their repository, reviews, tests, and product decisions.

How does Atlas work?

Atlas connects repository, product decisions, agent sessions, pull requests, reviews, tests, and documentation. It looks for repeated corrections or stale guidance, proposes focused updates, and leaves approval, ownership, and scope to people. Tests and future runs help verify the updates.

What does Atlas add to an AI coding-agent workflow?

Atlas turns recurring feedback and drift into proposed updates to skills, rules, policies, prompts, documents, checks, or hooks, with team approval and a link to the evidence or proof.

Is Atlas a code reviewer?

Atlas is described as a system for maintaining the team playbook, not as a code reviewer. It uses pull requests and reviews as evidence to find recurring lessons and improve team guidance.

What information does Atlas use?

The page describes Atlas connecting the repository, product decisions, agent sessions, pull requests, reviews, tests, and documentation. It does not specify the exact data fields or access scope.

What does Atlas install or integrate with?

The page shows examples of proposed skills, rules, checks, and hooks, and describes possible updates to policies, prompts, and documents. It does not specify an installer or name vendor integrations.

How is Atlas different from ordinary documentation?

Atlas connects team guidance to the repository, decisions, agent sessions, reviews, and tests. When practices drift, it proposes updates for people to approve, then uses tests and future runs to help verify them.

Better context. Every time.

AI writes the code.
Atlas keeps your team's
way of building up to date.

A living team playbook.
Connected to the code.
Built on what you've learned.