arizuko › products › PM agent (Sloth)
PM agent (Sloth)
Keeps the task board, writes the weekly status, and logs decisions with their context. Moves slowly, forgets nothing, and never invents scope.
What it does
The board is facts/tasks.md — a file, in the
group, that you can read and diff. Sloth updates it on explicit
instruction (“mark X done”, “add Y, owner Z,
Friday”), confirms owner and deadline before writing, and
flags what is blocked or overdue before anyone asks.
Decisions land in facts/decisions/, one file per
decision, with the context that produced it. That is the half most
task trackers lose: six weeks later the board says what was decided
and this says why.
A sample exchange
user mark the migration task done
agent facts/tasks.md — "0034 outbound retry migration", owner mira,
due 2026-08-12. Mark it done as of today?
user yes
agent Done. Two tasks still blocked: "route token rotation" (waiting on
mira since the 9th) and "eval budget" (no owner). Want me to ping?What it ships
| File | What it is |
|---|---|
PRODUCT.md | the manifest — name, brand, tagline, env hints |
SOUL.md | who the agent is: precise, confirms before writing |
facts/team.md | who is on the team, their roles and contacts |
facts/tasks.md | the board itself — ships with the row format and no rows |
Who it is for
A small team that wants the board in the same channel as the work, and is willing to keep it in Markdown. It does not execute anything — no code, no infrastructure — by design: it tracks the work, other agents do it.