Turns a design decision (with its context, options, and consequences) into a complete Architecture Decision Record (ADR) and saves it under docs/ADRs/ -- never makes the decision itself, only records one already made or being made. Use when the user asks to write/draft an ADR, record a design/architecture decision, or…
Blocking status and reasons for one Jira issue (status flags, unresolved "blocked by" links, flagged comments). Use for "what's blocking PAY-123" or "is PAY-123 blocked".
What's happening on my board right now -- the active sprint if this is a Scrum project, or the column/status breakdown if it's Kanban. Auto-detects which one applies, so you don't need to know in advance. Use for "what's going on with my board", "what's the current sprint", "how's the board looking" when you're not…
Creates a new Jira issue -- a parent work item (Story/Bug/Task/Epic) or a subtask under one. Use for "create a bug for X", "add a frontend subtask under PAY-100". This is a write operation gated behind explicit user confirmation.
Updates fields (summary, description, labels, assignee, priority, components) on an existing Jira issue or subtask. Use for "rename PAY-123", "reassign PAY-123 to John", "add the Backend label to PAY-101". This is a write operation gated behind explicit user confirmation. For moving an issue between statuses, use…
Full context for one Jira issue: fields, comments, worklogs, changelog, and links, as one document. Use for "summarize PAY-123" or "what's the status of PAY-123".
Runs an arbitrary JQL search against Jira and returns structured issue results. Use for "find issues where...", "which of my tickets haven't been updated recently", or any query not covered by a more specific Jira skill.
Column breakdown and per-column issue counts for a kanban board. Use for "what's on the board", "how many tickets are in review", or any "current sprint" question that turns out to be about a kanban project (no sprints) instead.
Single entry point for worklog actions on a Jira issue -- logging new time, fixing an existing entry's duration/description/date, or deleting one. Routes to the right underlying action based on what's being asked. Use for "log 2h on PAY-123", "fix that worklog, wrong day", "delete that worklog I logged by mistake".…
Lists unresolved Jira issues assigned to the current user, ordered by priority and recency. Use for "what should I work on next", "what are my open tickets", "summarize my tickets".
Looks up Jira users by name/email fragment and returns their accountid. Use to resolve a person's name (e.g. "John") into the accountid JQL and createissue/editissue need for assignee filters/fields -- never guess or invent an accountid.
Moves a Jira issue to a new status. Use for "move PAY-123 to Review" or "close PAY-123". This is a write operation gated behind explicit user confirmation.
Tracks what you're working on as the day goes, then turns it into Jira worklogs. Use when someone narrates their work rather than naming one ticket -- "I'm starting on X now", "two bugs came in, took me an hour", "after that I spent 3h on Y", "log my day", "what have I worked on today". Finds the matching issues…
Groups unresolved Jira stories/bugs/tasks with their labeled subtasks to determine which ones need frontend work, backend work, or design/Figma readiness, and which ones haven't been broken into subtasks yet and need manual triage. Use for "which tasks have no subtasks yet", "which need frontend vs backend", "which…
Permanently deletes a Jira worklog entry. Use for "delete that worklog", "remove the time I logged on PAY-123 by mistake". This is a destructive write operation gated behind explicit user confirmation.
Updates an existing Jira worklog entry's duration, description, or date. Use for "fix that worklog", "I logged the wrong date, change it to Tuesday", "change the description on that time log". This is a write operation gated behind explicit user confirmation.
Aggregate the current user's logged Jira time over a date range, compared against each touched issue's original estimate. Use for "how many hours did I log this week", "how much more than estimated did I work", "what did I get stuck on recently".
Logs time against a Jira issue. Use for "log 2h on PAY-123" or "I spent 30 minutes on PAY-123 today". This is a write operation gated behind explicit user confirmation.
High-level Jira assistant. Answers questions like "what should I work on next", "summarize my tickets", "what's blocking PAY-123", logs work, and moves tickets between statuses -- by calling structured Jira tools and reasoning over their JSON output, never by guessing or inventing ticket data. Use whenever the user…
Changes the tone/style the agent uses for the rest of the conversation -- neutral, alpha, angry, sarcastic, flatterer, or too-kind. Invoke as "/mood " or in plain language ("be angrier", "roast me", "be an alpha about this", "tone it down", "go back to normal"). Affects delivery only, never substance: never skips a…
Turns a feature brief into a complete Product Requirement Document (PRD) and saves it under docs/PRDs/ -- never implements the request, only documents it. Also maintains CURRENTSTATE.md, a minimal navigation map of PRD implementation status. Use when the user asks to write/draft a PRD, spec out a feature, or turn a…
Turns a proposed technical/architecture change (with its problem statement, goals, proposed design, alternatives, risks, and rollout plan) into a complete Request for Comments (RFC) and saves it under docs/RFCs/ -- never implements the proposal itself, only documents it and opens it for review. Use when the user asks…
Reads, searches, and sends Telegram messages on the user's personal account via Telethon -- strictly scoped to chatids already present in TELEGRAMALLOWEDCHATS, with every single action (reads included) gated behind explicit confirmation. Use when the user asks to check, read, search, reply to, forward, or send…
★not rated 2 5d agoA100 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: