implement
The implement skill orchestrates software development by reading a plan file, delegating implementation tasks to parallel subagents, and verifying git branch state throughout execution. Use this skill when you have a structured plan document outlining features or fixes that need coordinated implementation across multiple concurrent tasks, particularly in environments with Agent tools or task management capabilities.
git clone --depth 1 https://github.com/posit-dev/skills /tmp/implement && cp -r /tmp/implement/posit-dev/implement ~/.claude/skills/implementSKILL.md
# Implementation Orchestrator Plan file: `$path` Read your instructions from the appropriate reference file before proceeding: - If you have access to Agent, TaskCreate, TaskUpdate, TaskList tools: Read `references/claude-code.md` - Else if you have access to task and read_agent tools: Read `references/copilot-cli.md` - Otherwise: Read `references/generic.md`
>
Create and use brand.yml files for consistent branding across Shiny apps and Quarto documents. Covers: (1) Creating new _brand.yml files, (2) Applying to Shiny (R and Python), (3) Using in Quarto, (4) Modifying existing files, and (5) Troubleshooting. Includes complete specifications and integration guides.
Write ggsql queries — a grammar of graphics for SQL. Use when the user wants to create, modify, or understand a ggsql visualization query.
Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes. Activate when the user says "create pr", "make a pr", "open pull request", "submit pr", "pr for these changes", or wants to get their current work into a reviewable PR. Assumes the project uses git, is hosted on GitHub, and has GitHub Actions CI with automated checks (lint, build, tests, etc.). Does NOT merge - stops when CI passes and provides the PR link.
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.
Bulk resolve unresolved PR review threads on the current branch’s PR — typically after threads have been addressed manually or via /pr-threads-address
>
Guide for drafting issue closure and decline responses as an open-source package maintainer. Use when helping compose a reply that says \"no\" to a feature request, closes an issue as won't-fix, redirects a user to a different package, explains why a design choice is intentional, or otherwise declines or closes a community contribution. Also use when the maintainer needs to explain a deprecation, point out a user misunderstanding, or communicate an effort/scope tradeoff to a contributor.