pi-my-rifle-ext

Create detailed implementation plans via taskwarrior. Use when the user wants to create a detailed implementation plan, spec, or technical specification. Trigger on mentions of "create plan", "implementation plan", "write a plan", "spec", "create plan from jira", "plan from ticket", a Jira ID (e.g. IMP-7070, DP-92) alongside a plan request, or a local feature request with no Jira ID (e.g. "plan a feature", "spec a feature", "I want to add/build X"). Jira ID is optional — without one, the skill interviews the user and creates a local `+feature` taskwarrior ticket.

Search local markdown knowledge bases, notes, docs, and wikis with QMD. Use when users ask to find notes, retrieve documents, inspect a wiki, answer from indexed markdown, or set up QMD access.

Generate comprehensive PR descriptions following repository templates. Use when the user wants to create or update a PR description. Trigger on mentions of "PR description", "describe PR", "generate PR", or "pr desc".

Iterate on existing implementation specs with thorough research and updates. Use when the user wants to modify, update, or refine an existing spec. Trigger on mentions of "update plan", "iterate plan", "modify plan", "change plan", "update spec", "iterate spec", or "modify spec".

Execute an approved implementation spec by driving the work from taskwarrior. Given a Jira ID, locate the spec task, parse its annotation for the spec file, then walk the phase tasks (+phase tag) and their subtask trees (depends:) in order. Use when the user says "implement DP-121", "start work on IMP-7070", "continue the spec for <JIRA-ID>", "resume implementing <JIRA-ID>", or names a Jira ticket that has an approved spec. Do NOT use to author new specs — route those to create-plan.

Guide for using the `devctl` CLI to manage the SalaryHero local Kubernetes development environment (minikube-based). Use this skill whenever someone asks about: starting or stopping services locally, bootstrapping the dev environment, rebuilding a service image, watching for code changes, streaming pod logs, shelling into a pod, checking deployed image tags, managing /etc/hosts entries, running database migrations locally, or syncing/cloning all SalaryHero GitHub repositories. Also use it when someone asks "how do I deploy X locally", "why is my service not updating", "how do I get the local env running", or "how do I clone all repos". Covers first-time setup through day-to-day workflows.

Bootstrap a debugging session for issues encountered during manual testing or implementation. Investigates logs (minikube pods), database state (PostgreSQL nonprod), and git history without editing files. Use when something is broken, unexpected behavior occurs, or you need to trace an issue. Trigger on 'debug', 'something's broken', 'help me debug', 'what's wrong', 'investigate issue', or when invoked with 'start: Debug'.

Use this skill whenever the user describes a feature, change, or improvement they want to build in one of their personal projects — e.g. "I want to add save functionality to my app", "let's add dark mode", "implement X", "build a feature that does Y", or "I need to refactor Z". The skill interviews the user to flesh out a vague idea into enough detail to actually implement, then records it as a Taskwarrior ticket. Trigger it even when the user doesn't mention Taskwarrior or the word "ticket" — any "I want to add/build/implement ..." for one of their projects is the cue.

Fetch unresolved PR review comments from GitHub, assess each as VALID or INVALID, auto-resolve INVALID threads, and produce a resolution plan for VALID ones. Use when the user asks about unresolved PR comments, wants to triage review feedback, resolve stale threads, or assess what still needs action on a PR. Also trigger on "unresolved comments", "open review threads", "pending reviews", "triage PR feedback".

Discovers relevant documents in a project's notes/ directory. Use when you need to find specs, tickets, research docs, PR descriptions, or any written context related to your current task. Supports both repo-local notes/ and a centralized notes root via $LLM_NOTES_ROOT. Trigger this skill whenever someone asks to "find notes", "check specs", "look up tickets", "search research docs", or wants to know what written context exists for a topic.

Send a PR review request notification to a Microsoft Teams channel via a Power Automate flow. Posts an Adaptive Card with the PR title, key facts (number, repo, base branch, Jira ticket), a short summary, and action buttons. Trigger when the user says "notify teams", "send PR to teams", "share PR in teams", "post PR review to teams", "tell teams about this PR", or similar. Works for any PR the user has just created or wants to surface for review.

Use Worktrunk for git worktree workflows and configuration whenever working in a git repository. Prefer `wt` over manual branch/worktree lifecycle commands; use it for switching, creating task worktrees, merging, removing, hooks, aliases, approvals, LLM commit generation, and troubleshooting.

Reference guide for the Atlassian CLI (acli) - a command-line tool for interacting with Jira Cloud and Atlassian organization administration. Use this skill when the user wants to perform Jira operations (create/edit/search/transition work items, manage projects, boards, sprints, filters, dashboards), administer Atlassian organizations (manage users, authentication), or automate Atlassian workflows from the terminal. Covers all acli commands including: jira workitem (create, edit, search, assign, transition, comment, clone, link, archive), jira project (create, list, update, archive), jira board/sprint, jira filter/dashboard, admin user management, and rovodev (Rovo Dev AI agent). Requires an authenticated acli binary already installed on the system.