Issues written
for whoever picks them up.
Issues, projects and cycles where an agent takes work the way a teammate does. Each issue carries what done means and the thread it came from, so Atlas starts from the decision, and status moves because the work did.
Projects
What it does
Issues anyone can pick up
Each issue says what done means and links its spec and the message it came from, so whoever takes it, person or agent, knows the job and why it matters.
Handed to an agent, still yours
Assign an issue to Atlas and you stay its owner. Its session shows what it read and did, and a question it asks marks the issue as needing you.
Triage, with the source kept
Work that arrives from a conversation, a form or an agent waits in triage, quoted from where it came, until someone accepts, declines or merges it.
Projects and cycles
A project is an outcome with a lead, a target date and its heading in one line. Cycles set the rhythm, and what does not finish rolls over with a note on why.
Review before done
Work arrives in review with its evidence. Done takes a check by someone other than whoever did it, and the issue keeps who checked and what they saw.
Status from the work
Issues move when the team decides in a thread or a pull request merges, and each move carries who decided and why.
What changes
What it changes
for your team and its agents
Agents on the board
An agent's work sits beside everyone else's, with an owner, a date and a review, so the team plans with it like any other capacity.
Standups about problems
Issues move as the team talks, so the standup is spent on what is stuck, with no round of updates first.
Forecasts from real throughput
Every project's date is checked against how fast this team and its agents actually close work, so a slip shows while there is still time to act.
Related
It works
with the rest of Together
