kendo-pm 0.7.0: resync kendo-mcp and kendo-cli with kendo, epic 163 included

[jasperboerhof]

Why

The kendo-mcp and kendo-cli skills described an older Kendo.

• Epic 163 shipped on 2026-10-16 (release #2995, CLI v0.16.0). The skills had no Goal, wishes, What done looks like, tick tools or epic comments. They also said update-epic-tool sets a status.
• 14 of kendo's 46 MCP tools were missing.
• Several existing rows were wrong against kendo main:
  • get-my-issues-tool was said to send priority and type as names. It sends numbers with *_name beside them (KD-1791).
  • The time-entry recipe used time_spent with a 1-479 limit and sprint_id. The tool takes minutes_spent, with no upper limit and no sprint.
  • Link Branch was said to pick the "primary" repo. It resolves only a project's single repo.
  • dismiss-report-tool was said to work without a category. The category is required.

What

plugins/kendo-pm/skills/kendo-mcp

• Epics: all six tools. A new section, Epics in Detail, covers:
  • goal, assignee_id and colors 0-9
  • Done when (wishes) and What done looks like (checks)
  • the derived Open/Closed status
  • the list form vs the epic_id form
  • the rule that a list is saved whole, so a wish sent without its id loses its tick
  • the tick tools and what they return
• Comments: a new table with the issue or epic subject, parent_id replies and 10,000 characters.
• New tools:
  • issues: bulk-create-issues, kendo-today
  • labels: the five label tools
  • time and tokens: update-time-entry, delete-time-entry, record-token-usage
  • sprints and reports: delete-sprint, get-report, send-feedback
  • errors: get-error-groups
• New resources: kendo://projects/archived, kendo://projects/{id} and kendo://reports/{id}. kendo://issues/{key} now takes a key too.
• Fixed rows: the four above, plus the 500 caps, the list-reports window (the queue's end, 20 by default) and the get-time-entries filters.

plugins/kendo-pm/skills/kendo-cli

• Epic commands: view, tick/untick, --goal/--assignee/--wish/--check, epic comments, attachments and delete. These need CLI 0.16.0 or later.
• Tenants and users: multi-tenant auth, --tenant / KENDO_TENANT, user me and user list, and project list --include-archived.
• Issues: unlink-branch, label set, the attachment commands and the comment commands with --reply-to. The task type works on create, update and promote.
• Sprints and labels: sprint create, update, complete and delete, and the label commands.
• Reports: report view, --status, the attachment commands, and dismiss --category (now required).
• Time and other: time update and time delete, --started-at with the UTC-offset warning, tokens log, feedback send and migrate jira-attach.

kendo-pm 0.7.0: the manifest version and the README rows.

skills/kendo-mcp, skills/kendo-cli (catalog copies)

• These stopped changing on 2026-09-02. They now carry the plugin's content.
• They keep the catalog's own conventions:
  • the {{ISSUE_KEY_PREFIX}} placeholders
  • bare skill names
  • no .claude/project-context.md reads
  • no agent-ready.md, because nothing in the catalog reads it
• The root README rows are updated.

Out of scope

• The four repo copies (lokalekeuze, scripthub, crit, kendo-HQ). They are skipped on purpose.
• The personal /write-epic and /orchestrate changes. They are dotfiles DOT-0064.
• triage-reports setting a goal on a cluster epic.

Test plan

• MCP tools: all 46 classes in backend/app/Mcp/Tools/ at kendo 9d85455f04 are named in the skill.
• MCP parameters: every parameter the skill names is in its tool's schema. checks and wishes come through HandlesEpicLists, the comment subject through ResolvesCommentSubject.
• CLI commands: every one of the 82 commands in kendo commands --json (CLI 0.16.0) is in the kendo-cli skill. The four exceptions need nothing: epic update-comment, epic delete-comment and epic untick are covered in prose, and help needs no entry. The flags were read from the same output.
• Behaviour text: checked against site/docs/mcp/*.md, site/docs/cli/index.md and site/docs/api/{sprints,time-entries,reports}.md at the same sha.
• Catalog copies: diff between the catalog and plugin copies shows only the catalog conventions.
• Manifest: plugin.json parses.
• CI green. It runs only shell checks, and no shell file changed.

🤖 Generated with Claude Code