implement

Name: implement
Availability: InStock
Author: lioartoil

Coordinates planning, implementation, testing and review to deliver a merged pull request from a ticket ID.

Updated Apr 4, 2026

Search Tags:#tdd #end-to-end #code-review #production-grade #feature-implementation #pr-automation #ticket-to-merge

Ready to run

npx skills add https://github.com/lioartoil/claude-code-handbook --skill implement-lioartoil

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/lioartoil/claude-code-handbook/tree/main/skills/implement
Command: npx skills add https://github.com/lioartoil/claude-code-handbook --skill implement-lioartoil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates end-to-end feature delivery from ticket to merged PR, unifying brainstorming, API research, pattern scanning, TDD, code review, and verification to remove handoffs and reduce rework.

Core Features & Use Cases

End-to-end feature orchestration: from ticket intake through PR to merge, including plan, implementation, tests, and review.
Guardrails and repeatable workflow: ensures production-grade quality with built-in checks and standards.

Quick Start

Provide a ticket ID to start the end-to-end implementation workflow.

Frequently Asked Questions about implement

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

FAQPage Schema

How do I automate end-to-end feature implementation from a ticket to a merged PR?▼

End-to-end feature implementation is automated by orchestrating planning, research, design, TDD, code review, and verification to produce a ready-to-merge change set in a single pass. You simply provide a ticket ID to initiate the delivery workflow.

What is the best way to ship production-grade code without manual handoffs or rework?▼

Shipping production-grade code without rework requires unifying brainstorming, API research, pattern scanning, and TDD into a repeatable workflow with built-in guardrails. This ensures organizational standards are met before the final pull request is merged.

Can I adjust the scope or bypass code review steps during automated ticket-to-merge delivery?▼

Automated ticket-to-merge delivery supports optional flags to adjust scope or bypass review steps. This allows you to tailor the end-to-end workflow while maintaining phase alignment and guardrails for production-grade output.

Does end-to-end feature delivery apply test-driven development and automated code review checks?▼

End-to-end feature delivery integrates test-driven development and automated code review as core phases. These checks ensure the implementation meets production-grade quality standards before the pull request is prepared for merging.

When do I need an automated ticket-to-merge orchestration workflow for feature implementation?▼

An automated ticket-to-merge orchestration workflow is needed for projects requiring production-grade code delivered in a single pass. It eliminates phase misalignment by coordinating planning, implementation, testing, and review sequentially.