develop

Drive a pull request all the way to merged — not just check whether it is. Use this skill whenever the user wants a PR finished, says "get this PR done", "babysit this until it merges", "see this through", "make sure PROJ-123 ships", "push this over the line", or shares a PR they want completed. Built for the common case of an agent-drafted PR that needs the last mile: resolve review comments, fix the lint/type/test failures the drafting agent missed, rebase if it won't merge cleanly, mark it ready, request the right reviewer, keep the description honest, and merge once it's approved and green. It reads the PR state deterministically to decide what's blocking, then does every mechanical fix it safely can, escalating only genuine judgment calls. Never uses admin override or auto-merge. Automates as much as possible unattended; pair with `/loop` to keep driving across CI runs and review waits.

Fetch and display a quick summary of all your active issues across every board and project. Use this skill whenever the user wants a personal kanban overview, asks what they're currently assigned to, wants to know what's on their plate, or needs a cross-project status check. Trigger on phrases like: "show my issues", "what am I working on", "what's on my plate", "board summary", "active tickets", "show my issues", "what's assigned to me", "give me a status overview", "where are my tickets", "summarise my work", or any request to see a personal view across one or more boards. Don't wait for the user to name a specific tool — if they want an overview of their current work items, this skill applies.

Turn an approved spec into a terse, well-structured implementation plan that says exactly how the work will be built. Use this skill whenever the user wants an implementation plan, a technical approach, or a breakdown of how to build something they've already specced. Also trigger when the user says things like "plan out how to build this", "how should we implement X?", "write the implementation plan", "what's the technical approach?", "break down the work on PROJ-123", "turn this spec into a plan", or "how do we actually do this?". This is the step *after* the spec — where the spec captures what and why solution-agnostically, the plan owns the how. Use it even from rough notes or a bare ticket; you can read the codebase and shape a plan, asking the user any blocking questions before you write.

Triage a GitHub pull request to decide whether it's ready for human review. Use this skill whenever the user shares a PR link, asks you to check if a PR is ready, wants to triage their review queue, or mentions a pull request that needs evaluating. Also trigger when the user says things like "should I review this?", "is this PR ready?", "check this PR for me", "triage my PRs", or gives you a GitHub PR URL. If the user is an engineering lead dealing with incoming PRs from reports, this skill decides whether the PR deserves their attention right now or whether the author needs to do more work first.

Craft and send beautifully formatted Slack messages using the Slack MCP. Use this skill whenever the user wants to send a Slack message of any kind — replying to a technical question in a thread, notifying a teammate about PRs or code changes, explaining how a system works, or any communication that should look polished and professional. If the user mentions Slack, a colleague they want to message, a thread they want to reply to, or a PR they want to share — use this skill. Don't wait for the user to ask explicitly for "Slack formatting" — if they're composing a message for Slack, this skill applies.