The missing “why” is what forces the restart.
Jira can show the ticket and GitHub can show the code. Imdone keeps the reasoning that lets the next session understand what happened without replaying the conversation.
Rejected approaches
Record what the team tried, why it failed, and why the decision should not be reopened without new evidence.
Decision evidence
Keep the observations, constraints, and test results that made the current direction reasonable.
The next action
Leave the next developer or agent a trusted place to resume instead of another transcript to reconstruct.
Install once. Keep the reason with the work.
Imdone works beside Jira or GitHub and the coding agents you already use. The issue becomes the durable handoff.
1. Initialize the repository
Run imdone init and connect the tracker where the team's work already lives.
2. Capture the decision
Record the observation, evidence, decision, rejected path, and next step while the reasoning is still fresh.
3. Resume without the replay
Push useful context back to the issue so the next human or agent starts with the reason, not just the result.
Used by developers inside real engineering teams
Developers who use imdone
Looking for imdone desktop?
Imdone desktop is still here. Use it to manage local Markdown tasks and keep repo-based work visible while you code.
Get imdone desktopStop explaining the same decision twice.
See how imdone keeps the reasoning behind the issue available to humans and coding agents.
See what imdone keeps with the story