ducky

Weekly backlog audit — field completeness, staleness tiers, and duplicate detection. Run during grooming to clean up the backlog.

Creates a JIRA Bug with steps to reproduce, expected/actual behavior, and fix criteria. Activates when users ask to create a bug report, file a bug, or report an issue.

Creates a JIRA Epic with scope, success criteria, and child story breakdown. Activates when users ask to create an epic.

Creates a JIRA Story with user story format, acceptance criteria, and technical notes. Activates when users ask to create a story or user story.

Creates a JIRA Task for tech debt, infrastructure, documentation, or spike work. Activates when users ask to create a task, spike, tech debt ticket, or infrastructure work.

Daily briefing — sprint progress, new tickets, and recent comments in one report. Run this to get oriented at the start of the day.

Validate JIRA ticket fields and quality standards. Run on a single ticket or bulk-audit all sprint tickets. Activates when users ask to "check hygiene", "validate fields", or "audit sprint tickets".

Show current sprint and your assigned tasks

List all your assigned JIRA tasks in the current project

Release readiness report — progress, risks, remaining work, and priorities by Fix Version. Activates when users ask about release status, what's left for a release, or release readiness.

Sprint planning prep — backlog candidates, stale items, release priorities, capacity analysis, and pull suggestions. Run before sprint planning to prepare.

Sprint health report — progress, burn rate, blockers, at-risk tickets, carry-over risk, and team workload.

Pre-sprint readiness check — validate committed items, flag risks, check capacity, and surface anything that might have been missed. Run after sprint planning, before the sprint starts.

Estimates story points for JIRA tickets by analyzing complexity, scope, and comparing to historical team data. Activates when users ask to estimate, point, or size a ticket, or ask "how many points should this be?"

Interactive triage session - collaboratively assess a ticket's validity, completeness, and sprint-readiness. Activates when users ask to "triage a ticket", "is this ticket ready?", or "walk me through this ticket".

Summarize your last session log into a standup-ready recap, grouped by project. Run this before standup to get oriented on what you did.

Read today's daily note from Obsidian — surface todos, context, and session history. Use this to get oriented at the start of a session.

Append a structured session summary to today's daily note under the Log section. Run this at the end of a session to capture what was done.

Manage todos in today's daily note — add items, mark them done, or pick one to focus on.

Webby Vanderquack second brain persona — curious, meticulous, and always connecting the dots. Defines behavioral patterns for all Obsidian vault operations.

Pick a todo from today's daily note and start working on it with Claude.

Creates a JIRA Feature with problem statement, benefit hypothesis, and child epic breakdown. Activates when users ask to create a feature or initiative.

Scrooge McDuck project management persona — meticulous, detail-oriented, and allergic to waste. Defines behavioral patterns for all JIRA operations.

Sets or changes the Activity Type on an existing JIRA ticket for capacity planning. Activates when users ask to set, change, or add activity type to a ticket.

Log activity to a kanban task note — capture progress, decisions, and status updates for the active task.

Manage kanban board tasks — add cards, move between columns, mark done, list, and reorder.

Gather open review feedback on a PR you own and step through each thread interactively, fixing code or replying as you go. Activates when users ask to "address feedback", "work through PR comments", or "resolve PR feedback".

Routes to the correct JIRA ticket creator based on type. Activates when users ask to "create a ticket" or "file a ticket" without specifying a type (bug, story, task, epic, or feature).

Search the Obsidian vault for relevant context on a topic. Returns synthesized findings with wiki-links.

File new knowledge into the Obsidian vault at the correct location with proper frontmatter and wiki-links.

One-time setup to configure MCPVault for cross-project Obsidian vault access. Run this once per machine.

Darkwing Duck code ops persona — vigilant code guardian who catches problems before production. Defines behavioral patterns for all GitHub operations.

Applies a personal writing style to any generated text including PR reviews, code comments, technical feedback, and project updates. Activates when asked to write in my style, in my voice, on my behalf, or when any other skill or command needs output matching personal tone.

GitHub issue management - create, search, comment, close, view

Create a PR with a well-structured description in your writing style

Check status of a PR - CI, reviews, merge readiness

Review Round 3 - Detailed line-by-line code review for bugs, security, tests, and performance

Review Round 2 - Top-down architecture and design assessment of a PR before detailed code review

Review Round 1 - Check CI/CD status, automated checks, and existing reviewer comments before diving into code

Review a PR using a structured multi-pass approach with feedback in your personal writing style