Done means proven.
An agent saying “finished” is not the same as finished. Damper makes every task carry its own proof — checklist evidence, before-and-after screenshots, request and response examples — and gives reviewers one place to approve it or send it back.
No evidence, no ship.
Each project defines a completion checklist, and Damper scopes it to what a change actually touches — the server, the dashboard, a public page, a migration. Completing a task needs a resolution for every active item: done with proof, or skipped with a reason.
- Scoped automatically — items activate from the paths and change kinds in play.
- Structured proof — commands run, files affected and a short evidence note per item.
- Completion receipt — what shipped, what was verified and what risk remains, stored on the task.
See the change, not just the diff.
Agents attach screenshots of every changed page — per state, theme, locale and viewport — and request and response examples for every changed endpoint. Before and after, side by side, right on the roadmap item.
- Before and after — compare side by side, or flip between them with the arrow keys.
- API examples — credentials redacted, long bodies trimmed, copy as curl.
- Evidence policy per project — off, suggested or required for the change kinds you declare.
Reviewers decide. Agents listen.
Approve an artifact or request changes on it. The verdict is stored on the task, so the next agent session reads it back and fixes exactly what you flagged — no copy-pasting feedback out of chat.
- Per-artifact verdicts — approve or request changes on each screenshot and example.
- Public “what to verify” — review instructions can appear on the public roadmap item while it is in review.
Review the work where the work is.
Checklists, screenshots and API examples arrive with every task, so review takes minutes, not a meeting.
Where this fits in the loop.
Collect
Catch feedback where it happens — in your app, in Slack, on a call — and land it in one clean inbox.
Prioritize
Rank requests by who is asking. Votes are weighted by plan, so paying customers move the roadmap.
Build
Hand the top task to your AI coding agent with the rules that govern it — and get proof when it is done.
Ship
Shipped work becomes a changelog entry, and everyone who asked for it hears first.
Around the loop
Docs, uptime, errors and team access — the product ops that sit next to the loop.