AI skills - imdone docs

Bundled AI Skills

imdone-cli ships with backlog-local skills for Claude Code and Codex. They help teams turn issue context into execution-ready work without inventing a separate planning system or burying delivery context in side docs.

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.
`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.

These skills are bundled in your backlog under .claude/skills/ and .codex/skills/.