kendo.dev

Appearance

MCP Workflows ​

These workflows combine multiple MCP tools and resources to accomplish common project management tasks. Use them as natural language prompts with your AI assistant.

Plan a Sprint ​

Set up a new sprint and populate it with issues from the backlog.

Steps:

  1. Read the backlog — kendo://projects/{id}/issues to see all issues
  2. Read lanes — kendo://projects/{id}/lanes to identify the backlog lane
  3. Search for candidates — search-issues filtered by lane, priority, or epic
  4. Create the sprint — create-sprint with title and date range
  5. Assign issues — update-issue on each issue to set sprint_id
  6. Activate — update-sprint to set status to 1 (Active)

Example prompt:

Look at the kendo backlog and create a two-week sprint starting next Monday. Pick the highest-priority bugs and the top 5 features, assign them to the sprint, and activate it.

Triage New Bugs ​

Review unassigned bugs, set priorities, assign team members, and move them to the right lane.

Steps:

  1. Search unassigned bugs — search-issues with type: 1 (Bug) and no assignee_id
  2. Read members — kendo://projects/{id}/members to see who's available
  3. Prioritize — update-issue to set priority on each bug
  4. Assign — update-issue to set assignee_id
  5. Move to lane — update-issue with lane_id to move from Backlog to the appropriate lane

Example prompt:

Find all unassigned bugs in the kendo project. Show me their descriptions, then assign them to the right team members. Move anything high-priority to "In Progress".

Log Time After Coding ​

Record how long you spent on an issue after finishing your work.

Steps:

  1. Find the issue — search-issues or kendo://issues/{id} to confirm the right issue
  2. Log time — create-time-entry with minutes and a note
  3. Optionally move the issue — update-issue with lane_id if work is complete

Example prompt:

I just spent 2 hours fixing the email validation bug. Log the time with a note about what I did and move it to "Review".

Set Up Blocking Dependencies ​

Create related issues and link them with blocking relationships.

Steps:

  1. Create issues — create-issue for each piece of work
  2. Link blockers — update-issue on the dependent issue with blocked_by_ids
  3. Optionally add to epic — update-epic with issue_ids to group them

Example prompt:

Create three issues in the kendo project: "Design database schema" (highest priority), "Implement API endpoints" (high), and "Build frontend form" (medium). The API depends on the schema, and the frontend depends on the API. Group all three in the "Auth Overhaul" epic.

End-of-Sprint Review ​

Review sprint progress, complete the sprint, and prepare the next one.

Steps:

  1. Read sprint state — kendo://projects/{id}/sprints to find the active sprint
  2. Check sprint issues — search-issues filtered by sprint_id to see what's done and what's not
  3. Review time spent — get-time-entries grouped by issue for the sprint date range
  4. Add comments — add-comment on incomplete issues explaining the status
  5. Complete sprint — complete-sprint with a target sprint for incomplete issues
  6. Create next sprint — create-sprint if needed

Example prompt:

Review the current sprint in the kendo project. Show me what's done and what's still open, how much time was logged per issue, then wrap up the sprint. Move anything incomplete into the next one.

Quick Issue from Context ​

Create a well-structured issue from context you already have in your coding session.

Steps:

  1. Read the project — kendo://projects/{id} for context
  2. Read members — kendo://projects/{id}/members for assignment
  3. Create the issue — create-issue with full details
  4. Link branch — link-branch if you already have a branch
  5. Log initial time — create-time-entry if you've already started working

Example prompt:

I just found a bug where the login form rejects email addresses with plus signs. Create a high-priority bug in kendo, assign it to me, link my current branch, and log the 30 minutes I've already spent investigating.

See Also ​