implement

$npx mdskill add posit-dev/skills/implement

Orchestrates parallel implementation of a plan file using subagents.

  • Solves the need to execute a multi-step plan efficiently and reliably.
  • Depends on subagent tools and optionally a model override flag.
  • Reads plan file and reference instructions to determine execution strategy.
  • Delegates work to subagents in parallel, tracking progress and verifying quality.

SKILL.md

.github/skills/implementView on GitHub ↗
---
name: implement
description: "Orchestrates implementation of a plan file by delegating work to subagents in parallel. Verifies git branch state, tracks progress, and ensures high-quality implementation. Invoke with a plan file path and optional model override: /implement plans/my-plan.md [--model sonnet]"
disable-model-invocation: true
arguments: [path]
argument-hint: "[plan-file-path] [--model sonnet|haiku|opus]"
metadata:
  author: Garrick Aden-Buie (@gadenbuie)
  version: "2.0"
license: MIT
---

# 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`

More from posit-dev/skills

SkillDescription
alt-text>
brand-ymlCreate 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.
cli>
cran-extrachecks>
create-release-checklist>
critical-code-reviewerConduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
describe-designResearch a codebase and create architectural documentation describing how features or systems work. Use when the user asks to: (1) Document how a feature works, (2) Create an architecture overview, (3) Explain code structure for onboarding or knowledge transfer, (4) Research and describe a system's design. Produces markdown documents with Mermaid diagrams and stable code references suitable for humans and AI agents.
ggsqlWrite ggsql queries — a grammar of graphics for SQL. Use when the user wants to create, modify, or understand a ggsql visualization query.
lifecycleGuidance for managing R package lifecycle according to tidyverse principles using the lifecycle package. Use when: (1) Setting up lifecycle infrastructure in a package, (2) Deprecating functions or arguments, (3) Renaming functions or arguments, (4) Superseding functions, (5) Marking functions as experimental, (6) Understanding lifecycle stages (stable, experimental, deprecated, superseded), or (7) Writing deprecation helpers for complex scenarios.
maintainer-declineGuide 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.