Turn your issue tracker into shared working memory.

Prove it in 5 minutes

Start in the repo where issue context should live. imdone will create local backlog files and sync them with Jira or GitHub.

Open the generated Markdown, make one small edit, then push it back.

Before you run it

• Node.js 22 or newer.
• git and a project directory. Run imdone init from your repo.
• Jira or GitHub access with permission to read and update issues.

The package is imdone-cli. It installs the imdone command.

What appears in your repo

imdone stores issue content, comments, attachments, and sync metadata as local files you can inspect with your editor, grep, diffs, and AI coding agents.

>tree backlog
backlog
├── .imdone
│   └── config.yml
└── current-sprint
    └── SCRUM-123-Example_issue
        ├── attachments
        │   └── .metadata.yml
        ├── comments-SCRUM-123.md
        ├── issue-SCRUM-123.md
        └── changelog.yml

System metadata lives in HTML comments at the end of issue files. Leave it intact so imdone can map local files back to provider issues.

Sync commands

Read provider context

• imdone pull fetches issues, comments, and attachments.
• imdone show KEY inspects one issue.
• imdone list lists local issues.

Write local changes

• imdone push syncs local Markdown updates back.
• imdone add creates a new issue.
• imdone move KEY "In Progress" changes status.
• imdone merge resolves sync conflicts locally.

Where to go next

Use the full CLI docs for provider setup, command reference, Git behavior, attachments, AI skills, and troubleshooting.