imdone-cli docs

Turn Jira or GitHub issues into shared working memory for AI and humans, then sync updates back to your provider.

imdone-cli pulls issue content and attachments into local Markdown and files, then syncs your updates back to Jira or GitHub so developers and AI agents can work locally in the editor while product, design, and stakeholders stay in Jira or GitHub.

Many teams keep their stories and requirements in Jira or GitHub, but let the AI execution context drift into the working branch or into a branch independent of the work. That leads to broken handoffs, rework, and missing context. imdone keeps the working context with the issue, where the work already lives, and turns it into durable, reviewable local files.

imdone pull and imdone push keep that context in sync. Bundled skills help teams turn raw tickets into buildable work, create and repair issue structure, reduce handoff risk, and inspect delivery flow from local issue history. The result is a shared working memory of hypotheses, decisions, evidence, and next steps tied to the issue instead of scattered across browser tabs, branches, and chat.

What you get:

• Keep AI and human working context in Jira or GitHub issues instead of hiding it in a branch independent of the work.
• Work from local Markdown in your editor without giving up provider-native collaboration.
• Track feature work and feedback loops visually on the imdone kanban board.
• See issue lifecycle history locally in changelog.yml, so cycle-time inputs stay visible in the issue folder.
• Use bundled skills to create and structure issues, refine stories, define success metrics, tighten plans, assess handoff quality, render PDFs, and generate archived cycle-time reports.
• Reduce handoff risk by keeping decisions, evidence, and delivery notes tied to the issue.