Work Agent Tools — Productivity skill for Claude Code

work-agent-tools

Claude Code plugins for a software project run by a team through a tracker: setting up the agent harness with the project's own workflow commands, Jira work to one standard, and estimates from a spec and a design. One author's toolkit, grown on commercial projects and open to anyone — the rules are opinionated, and each project tunes them through its own profile.

One repository: it is both the marketplace (`mluk-work-agent-tools`) and the home of the plugins.

Why it exists: the method must not live as copies in every repository. Estimation rules, the shape of a Jira issue and the order of project bootstrap are the same everywhere; only keys, rates and the domain differ, and those stay in the project.

Does it fit your project

Each plugin is enabled on its own, so a project takes only what fits.

• work-bootstrap — any repository, any stack: frontend, backend, monorepo, library, CLI. It writes the harness into the project, including workflow commands shaped to its branch chain, its forge (GitHub, or GitLab including self-hosted) and its tracker, and keeps it current with the method.
• work-jira — work tracked in Jira Cloud: issues created to one standard, statuses, comments, worklog.
• work-estimation — a project estimated before it starts, from a spec and a design handoff.

A solo project on GitHub without a tracker fits [agent-tools](https://github.com/maximlukyanovich/agent-tools) better: there the workflow commands ship in a plugin instead of being written into the project.

Requirements

• Claude Code; 2.1.292 or later for the one-line start from scratch.
• git, and gh or glab signed in for the steps that open a pull or merge request.
• Python 3 — the plugins' scripts and the work-bootstrap session-start hook.
• For work-jira: a Jira Cloud site and a working .mcp.json with its credentials; without one the commands stop and say what is missing.
• For /work-estimation:export: the .xlsx workbook templ