Keep context close to code

Get Started

Sound familiar?

You lose time re-orienting after every interruption

You can't remember why you made that choice six months ago

You start every Monday rebuilding context from last week

You put off updating issues because it takes you out of flow

You can't explain to the new hire why the code works this way

When context lives in your repo

Faster onboarding

New team members see what's being worked on right now, with all the context, without switching tools.

"With imdone, everything is inside my workspace. I update tasks same way I update code, fast, smooth, and without leaving my flow."
- Vaibhav, Software Engineer

Better async collaboration

Everyone has the same context, whether working together or apart. The why and how behind decisions stay visible to the whole team.

"I'm a huge markdown fan and a huge JIRA UX/UI non-fan. imdone has allowed me to stay in my happy place and leverage JIRA, but from afar and through a UX/UI that I'm much happier with."
- B. Ruth

Fewer interruptions

Teams spend less time hunting for context and more time solving problems.

"I was looking for something simple that could serve as a single point of reference, a master kanban… something I can update from the editor with minimal fuss and version control. That's practically the value proposition of imdone."
- Software Engineer

Choose your workflow

Same markdown files. Different interfaces. Pick what fits your flow.

Command Line

For developers who live in the terminal

Sync Jira/GitHub to markdown files
Edit in vim, VS Code, any editor
Grep your backlog like code
AI agents can read your issues
Work offline, sync when ready

See CLI Workflow

Visual Board

For teams who think in kanban

Drag-and-drop markdown TODOs
Visual board in your editor
Works with existing markdown
Desktop app for Mac/Windows/Linux

See Desktop Workflow

Used by developers at:

Developers who love imdone