implement

Automate GitHub Issue implementation with TDD, worktrees, and pull requests.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/takemo101/compose-workflow --skill implement-takemo101
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/takemo101/compose-workflow/tree/main/.pi/skills/implement
Command: npx skills add https://github.com/takemo101/compose-workflow --skill implement-takemo101

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the entire process of implementing GitHub Issues, from initial analysis and environment setup to code implementation, quality assurance, and pull request creation.

Core Features & Use Cases

  • Automated Issue Analysis: Checks issue granularity and decomposes complex tasks.
  • Worktree Environment: Creates isolated environments for safe and efficient coding.
  • TDD & Quality Assurance: Enforces Test-Driven Development and automated quality checks.
  • Automated PR & Merging: Handles pull request creation, CI monitoring, and automatic merging upon success.
  • Use Case: A developer receives a GitHub issue. They can invoke this skill to automatically set up a coding environment, write tests, implement the code, ensure it passes all quality checks, and create a pull request ready for review and merging.

Quick Start

Use the implement skill to start working on issue ID 123 with the branch name 'feature-xyz'.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I automate GitHub Issues implementation from start to finish?

To automate GitHub Issues implementation end-to-end, this skill decomposes subtasks, sets up isolated worktree environments, executes TDD cycles, and creates pull requests. It manages the entire workflow from issue analysis to CI monitoring and automatic merging.

Can I use TDD cycles and automated quality checks for pull requests?

Yes, TDD cycles and automated quality checks are enforced during implementation to ensure code quality before pull request creation. The workflow monitors CI pipelines and handles automatic merging upon success.

What is the best way to decompose complex GitHub Issues into subtasks?

Decomposing complex GitHub Issues into subtasks is handled through automated issue analysis, which checks issue granularity and breaks down tasks. This creates manageable units for isolated worktree environment setup and coding.

Does automated pull request creation work with CI/CD pipelines?

Automated pull request creation works directly with CI/CD pipelines by monitoring CI status after PR submission. It ensures all quality checks pass before handling automatic merging to maintain code quality.

How do I set up an isolated worktree environment for feature development?

Setting up an isolated worktree environment for feature development is automated by this skill. It creates a safe coding space separated from your main branch, allowing efficient implementation of GitHub Issues without conflicts.

When should I not use automated end-to-end implementation for GitHub Issues?

Automated end-to-end implementation for GitHub Issues may not suit tasks requiring manual architectural decisions or highly subjective design choices, as the workflow enforces strict TDD cycles and automated quality checks before pull request merging.