imdone-cli docs

Turn your Jira and GitHub backlog into a product-engineering lab notebook for humans and AI agents.

imdone-cli pulls issue content, comments, attachments, lifecycle history, and progress notes into a local Markdown backlog, then syncs useful updates back to Jira or GitHub. Developers and AI agents can work locally in the editor while product, design, and stakeholders keep using the provider.

The goal is to keep learning attached to the work. Hypotheses, decisions, evidence, blockers, and next steps should live with the issue instead of disappearing into chat sessions, branches, terminals, and browser tabs.

What you get:

• A local Markdown backlog where Jira and GitHub issues become issue workspaces.
• Shared context for humans and AI agents without giving up provider-native collaboration.
• Progress notes that capture observations, evidence, decisions, blockers, completed work, and next steps.
• Comments, attachments, lifecycle history, and metadata stored with each issue workspace.
• Backlog-level templates, skills, and project configuration that keep story structure consistent across issues.
• imdone ai and imdone hdd workflows that launch supported coding agents with story context.
• imdone pull and imdone push sync so stakeholders can stay in Jira or GitHub.
• Track feature work and feedback loops visually on the imdone kanban board.
• 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 the product-engineering record in the backlog and linked to provider issues.

Why imdone-cli exists

AI makes it easier to produce code, but it also makes product-engineering learning easier to scatter. Decisions live in chat, evidence sits in terminal scrollback, blockers are mentioned in meetings, and the next agent session starts by reconstructing context.

imdone-cli makes the backlog a durable product-engineering lab notebook. Each issue workspace is an entry in that notebook: issue body, comments, attachments, lifecycle history, metadata, progress notes, and AI-ready context live together in local files next to the code. Backlog-level templates and skills keep structure consistent across issues. Humans and AI agents can read and update the same record, then imdone push syncs the useful parts back when the team is ready.