TDD task breakdown and TASKS.md management. Use when planning a new feature, breaking down work into implementation tasks, creating or updating TASKS.md, estimating effort, or organizing multi-step work into phases. Also use when translating a plan document (like docs/plans/*.md) into TASKS.md — includes systematic extraction checklist to ensure nothing is missed. Trigger on: feature breakdown, task planning, "write tasks for", "create TASKS.md", plan-to-tasks conversion, sprint planning, implementation ordering, or when the user mentions wanting to organize implementation steps for a feature.
MCP integration for kendo project management. Use when creating, updating, moving, or searching issues via MCP tools. Also use when writing user stories, logging time, managing epics, linking branches to issues, or triaging reports (bug reports, feedback). Provides access to projects, issues, lanes, sprints, epics, reports, and teams through MCP resources and tools.
Triage incoming reports (bug reports, feedback, feature requests) from the Kendo report queue. Fetches pending reports via MCP, cross-references with existing open issues to find overlaps, then walks the user through each report one-by-one using AskUserQuestion for a verdict: promote to issue, dismiss, or combine with another report. Promoted reports get proper user stories or bug reports following project conventions. Use this skill whenever the user mentions "triage", "triage reports", "check reports", "process feedback", "review reports", "incoming reports", "report queue", "what reports do we have", or any variant of wanting to process the Kendo report queue. Also trigger when the user asks about unprocessed feedback or pending bug reports.
Prepare a kendo issue for development: assign to current user, create a feature branch, link it, move to In Progress, and optionally check out in a worktree with full setup. Usage: /prepare-issue <issue_key_or_id> [N]. Use whenever the user wants to start working on an issue, prepare an issue, pick up an issue, or says "prepare issue", "start issue", "work on issue". Also trigger when combining issue assignment with branch creation, or when the user wants to set up a worktree for an issue.
Load the full context of the current branch and check alignment with the base: git diff summary, commit history, plan/task files, decisions, and (if the project has an issue-tracker skill) the upstream issue details. Reports how far behind the base the branch is and offers to merge on confirmation. Resolves merge conflicts intelligently (auto-resolves obvious ones, asks on ambiguous ones). Use this skill whenever the user wants to understand what the current branch is about, needs context after a /clear, starts a new session, says "what am I working on", "load context", "catch me up", "branch context", "where was I", "summarize this branch", "catchup", "sync my branch", "align with base", "update branch", or any variant of wanting to understand or sync the current state of work. Also use when the user just passes a branch name or issue key and expects you to load its context. Trigger on session start when the branch is not the default branch and the user's first message implies they want to resume work.
Synchronize the kendo board with GitHub branch and PR status. Use this skill whenever the user wants to check board alignment, sync the board, see what issues are stale, find merged PRs that haven't been moved to Done, or get an overview of branch status for open issues. Trigger on phrases like "sync board", "check board", "board status", "align board", "update board", "which issues are done", or "check branches".
Structured bug-fix workflow: identify the issue, reproduce the defect, confirm it isn't already fixed on the base branch, capture the investigation in docs/bugs/<slug>/BUG.md, propose the fix and wait for developer approval, implement it, and gate on the bug-fix-verifier agent before PR. Use whenever the user wants to fix a bug, says "fix bug", "bug fix", "debug this issue", "work on bug <key>", "/fix-bug", or is picking up a bug-type issue. Prefer this over /plan-feature for bugs — bugs don't have wireframes or acceptance criteria, they have "does the defect still reproduce?". This skill is the bug-side analogue of /plan-feature + /implement-plan collapsed into one lighter flow.
Create a pull request for the current branch, with optional issue feedback (when the branch links to a tracked issue) and optional review handoff (when a fresh review file exists in the plan directory). Use this skill whenever the user wants to create a PR, open a pull request, submit their work for review, or is done with a feature/fix branch. Also triggers on phrases like "make a PR", "open PR", "create pull request", "submit for review", "I'm done with this branch", or "push and PR".