implement

Generate a GitHub Issue and linked pull request closing it with Closes #N.

11|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/pillip/claude-dev-kit --skill implement-pillip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/pillip/claude-dev-kit/tree/main/skills/implement
Command: npx skills add https://github.com/pillip/claude-dev-kit --skill implement-pillip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end implementation of a single issue by generating a GitHub Issue and a linked pull request that closes the issue with a Closes #N statement. This skill applies to sprint workflows where every issue maps to a PR, including creating issue content, the PR body, and linking with the registry. It requires gh authentication, reads/writes to registry files (issues.md and STATUS.md), manages worktrees, and follows the checkpoint-driven workflow with tests.

Core Features & Use Cases

  • Auto-create GitHub Issue and PR for a given issue number and link with Closes #N.
  • Update sprint registry files (issues.md, STATUS.md) and manage git worktrees as part of the workflow.
  • Use case: manage end-to-end implementation of a single issue from planning to PR merge within a sprint lifecycle.

Quick Start

Provide the target issue number and run the implement skill to generate a linked GitHub Issue and PR that closes the issue.

Frequently Asked Questions about implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically create a GitHub issue and linked pull request for a sprint task?

To automatically create a GitHub issue and linked pull request, provide a target issue number to run the implement skill. It generates the PR body and closes the issue using a Closes #N statement.

What is the best way to manage git worktrees during issue implementation?

Managing git worktrees during issue implementation is handled automatically by the skill as part of its checkpoint-driven workflow. It creates and manages worktrees while updating sprint registry files like issues.md and STATUS.md.

Do I need gh authentication to automate pull request generation from issues?

Yes, gh authentication is required to automate pull request generation from issues. The skill relies on the GitHub CLI to create issues, manage pull requests, and link them with the Closes #N statement.

How does a checkpoint-driven workflow handle tests when implementing an issue?

A checkpoint-driven workflow handles tests by integrating them into the end-to-end implementation process. The skill follows this workflow to ensure tests are run and validated before the linked pull request is generated.

Can I update sprint registry files like issues.md and STATUS.md automatically?

Yes, you can update sprint registry files automatically. The skill reads and writes to issues.md and STATUS.md during the issue implementation process, keeping the sprint registry synchronized with the new pull request.

Why does my automated PR not close the linked GitHub issue?

An automated PR might not close the linked GitHub issue if the Closes #N statement is missing or incorrectly formatted in the PR body. The skill ensures this statement is properly included to close the issue upon merge.