Keep context close to code

Get Started

Why teams adopt imdone-cli

Your Jira or GitHub issue has the official conversation, but the real working context lives somewhere else

AI notes and human notes end up buried in branches, side docs, or chats independent of the work

Developers avoid updating issues because switching back to provider UI breaks flow

Handoffs break because decisions, evidence, and next steps are not tied to the issue

Turn issues into a shared context repo

Pull issues into local Markdown

imdone-cli brings issue content, comments, and attachments into durable files in your repo so developers and AI agents can work where the code lives.

"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

Sync updates back to Jira or GitHub

Keep provider-native collaboration without forcing developers out of their editor. Edit locally, then push changes back when you are ready.

"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

Keep handoffs and decisions with the work

Working context stays reviewable, searchable, and tied to the issue instead of disappearing into side docs, chat threads, or private AI sessions.

"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

What you get

Shared context for AI and humans

Keep AI and human working context with the Jira or GitHub issue instead of hiding it in a branch independent of the work.

Local editing in your own tools

Work from Markdown in VS Code, Vim, Cursor, Codex, Claude Code, or any editor without giving up provider-native workflows.

Better delivery discipline

Use repo-local issue context and bundled skills to tighten stories, define success metrics, and reduce handoff risk.

Bundled AI skills

Repo-local skills help teams refine stories, tighten plans, and turn issue context into buildable work without inventing a separate planning system.

Choose your workflow

The same local issue workspace supports terminal-first and visual workflows. Pick the interface that fits your team.

Command Line

Pull, edit, and push issue context from your editor and terminal

Pull Jira or GitHub issues into local Markdown and attachments
Edit issue content in Vim, VS Code, Cursor, or any editor
Grep your backlog and comments like code
Give AI agents direct access to the same local issue context
Push updates back to Jira or GitHub when ready

See CLI Workflow

Visual Board

View the same Markdown-backed work as a kanban board

Drag and drop Markdown TODOs on a visual board
Real-time sync with the same local files used by imdone-cli
Keep existing Markdown workflows and folder structure
Desktop app for Mac, Windows, and Linux

See Desktop Workflow

Used by developers at:

Developers who love imdone