imdone-cli docs
AI skills and plugins
Use bundled AI skills and plugins with local issue context.
Bundled AI Skills
imdone-cli ships with imdone skills for Claude Code and Codex. The canonical skill files live in the backlog, and imdone init, imdone clone, and imdone update link detected agents into the software project root so teams can use the same issue context whether the agent starts in the project root or inside backlog/.
| Skill | Problem it solves |
|---|---|
imdone-ls |
You need to find the right local Jira or GitHub issues quickly without jumping back to the provider UI or hand-scanning the backlog. |
imdone-template |
A story exists but is missing the right template-backed structure, so you need a fast way to apply or repair the expected sections and attachment links on an existing issue. |
imdone-add |
You want to create a new Jira or GitHub issue with the project’s usual defaults without switching back to the provider UI or manually rebuilding the same issue shape each time. |
backlog-refinement |
TODO stories are too vague to build, so developers and product owners need a fast way to identify weak stories and tighten them into thin, executable slices. |
hypothesis-driven-development |
Teams start building before they agree on the value, success criteria, demo path, or execution plan, which leads to output without proof of outcome. |
ai-experiment-capture |
Teams try new AI coding practices but lose the problem, prompt, outcome, and evidence unless a developer explicitly captures the experiment as shared working memory, with no background monitoring. |
shared-context-report |
It is hard to tell which in-progress stories are safe to hand off or how to brief others on the work without interrupting the team because planning context is missing or uneven across the work set. |
markdown-pdf-docker |
Teams have markdown reports and Mermaid diagrams, but no reliable way to turn them into polished PDFs without depending on host-specific tooling. |
cycle-time-report |
Teams want to inspect delivery speed from archived issue history and share the result as a markdown report, trend chart, and PDF without rebuilding the numbers by hand. |
Skills are installed under backlog/.claude/skills/ and backlog/.codex/skills/. When a supported agent is detected, imdone creates symlinks for every installed skill directory under the software project root’s .claude/skills/ or .codex/skills/ paths, pointing each link back to the backlog copy.
Bundled AI Plugins
imdone-cli also bundles agent plugin manifests under backlog/.claude/plugins/ and backlog/.codex/plugins/. When a supported agent is detected, imdone creates symlinks for every installed plugin directory under the software project root’s .claude/plugins/ or .codex/plugins/ paths, pointing each link back to the backlog copy.
| Plugin | Problem it solves |
|---|---|
imdone |
Developers start direct Codex or Claude sessions, disagree with AI output, add context, hit blockers, make decisions, complete meaningful work, or identify next steps during normal coding work, but that progress disappears unless the agent records a local progress note. The plugin ships the imdone-ai skill for loading configured active-story context on demand, captures progress moments, and asks for an issue or file target when no active story is configured. |