.agents

Make AI coding work survive the next thread.

Small changes stay conversational. When continuity matters, dot-agents stores work items, plans, and verification in your repo’s plain .agents/ folder so the next thread can continue.

Install with one command

Add it to your repo.

Run this from your repository root. It creates AGENTS.md and .agents/, and preserves your work when you sync.

terminal — repo rootbash
 curl -fsSL https://raw.githubusercontent.com/colmarius/dot-agents/main/install.sh | bash

Reviewcurl -fsSL https://raw.githubusercontent.com/colmarius/dot-agents/main/install.sh | less

Pin v0.5.1curl -fsSL https://raw.githubusercontent.com/colmarius/dot-agents/v0.5.1/install.sh | bash -s -- --ref v0.5.1

Then tell your agent: Run adapt.

Choose the smallest useful path

Keep simple work simple. Make durable work resumable.

Stay in the conversation when one thread is enough. Open a work item only when its status, decisions, or next action must survive this conversation.

Explore workflow guides

Request or change

Self-contained

Stay in this conversation

Use no repository workflow artifacts when the scope is clear and one conversation is enough.

  1. 01

    Work directly

    Plan only as needed, then implement from the request in this conversation.

  2. 02

    Verify

    Run checks that match the change’s risk.

  3. 03

    Report

    Summarize the outcome and any remaining uncertainty.

Continuity has value

Create durable context

Use a work item when work must resume, coordinate, preserve decisions, or move between threads.

  1. 01

    Work item

    index.md owns status and the exact next action.

  2. 02 · optional

    Context

    Add research or requirements only when unknowns need them.

  3. 03 · optional

    Plan when useful

    Define scoped tasks when execution needs sequencing.

  4. 04

    Execute

    Implement in the current thread by default.

  5. 05

    Evidence and closeout

    Record proof, promote reusable lessons, commit the final snapshot, then remove the work item.

What lands in your repo

Plain files. One place to resume.

A new thread reads index.md, then loads only the plan, research, or progress it needs.

Why durable context?
your-project/installed
├── AGENTS.md       # project instructions
└── .agents/
    ├── work/       # durable work items
    ├── research/   # reusable findings
    ├── references/ # local checkouts (gitignored)
    ├── skills/     # repeatable workflows
    └── scripts/    # safe sync updates
.agents/work/docs/install-pin/index.md● saved
# Pin the install example

Status: planned
Category: docs
Updated: 2026-06-22

## Why
Resume this docs fix next session.

## Summary
Pin both installer and payload versions.

## Artifacts
- None needed.

## Next Action
- Update the README install example.
- Check URL tag and --ref match VERSION.

Start with these prompts

Ask for what you need.

Use these prompts as written. Add detail only when it helps.

All four skills
Run adapt

Fill AGENTS.md with the repo’s commands and conventions.

Create a new work item for ...

Start durable context under .agents/work/.

Create a plan for ...

Plan conversationally, or turn durable context into implementation-ready tasks.

Continue the work item at ...

Read its current state, implement the next action, and verify.

with-agentsCompanion field guide

Go deeper on the practice behind the workflow.

dot-agents keeps durable work in the repo. With Agents is the source-backed field guide to briefing coding agents, spotting AI slop, preserving context, demanding evidence, and coordinating useful work.

Explore with-agents.dev (opens in a new tab)