implement

Automate end-to-end software delivery from ticket intake to PR publication.

1|Updated Mar 24, 2026

Search Tags:#planning #github #qa #implementation #pipeline #pr #planner

Ready to run

npx skills add https://github.com/matteobortolazzo/claude-tools --skill implement-matteobortolazzo

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill automates the full implementation pipeline, coordinating planning, execution, and delivery from ticket intake to PR creation.

Core Features & Use Cases

Plan and organize work from ticket-based or ticketless inputs.
Execute a deterministic, multi-phase pipeline including planning, implementing, testing, reviewing, and PR creation.
Read design specs when present, manage attachments, and enforce pre-flight checks before work begins.

Quick Start

Provide a ticket or task description to initiate the end-to-end implementation pipeline.

Frequently Asked Questions about implement

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

FAQPage Schema

How do I automate the entire coding pipeline from ticket intake to PR publication?▼

You can automate the coding pipeline from ticket intake to PR publication by running a deterministic, multi-phase workflow that orchestrates planning, implementation, testing, and review. It processes both ticketed and ticketless tasks directly into published pull requests.

What is the best way to implement code changes from a GitHub ticket without manual step-by-step intervention?▼

The best way to implement code changes from a GitHub ticket without manual intervention uses an automated pipeline that reads design specs, enforces pre-flight checks, and coordinates the implementation. It gates execution safely with user prompts before finalizing the review.

Can I use plan files to guide an end-to-end software implementation workflow?▼

Yes, you can use plan files to guide an end-to-end software implementation workflow. The pipeline reads available plan files and design specs to organize work, enforce pre-flight checks, and execute the nine pipeline phases from planning to PR.

Does the implementation pipeline support ticketless tasks and ad-hoc coding requests?▼

Yes, the implementation pipeline supports ticketless tasks and ad-hoc coding requests. It handles both ticketed work and ticketless inputs, allowing you to provide a direct task description to initiate the end-to-end delivery process.

How does pre-flight checking work before executing code changes and reviews?▼

Pre-flight checking works by validating the environment and reading available design specs or plan files before executing code changes. It ensures safe execution by gating the nine pipeline phases with user prompts prior to implementation and PR creation.

What are the limitations of automating software delivery from ticket intake to pull request creation?▼

Limitations of automating software delivery from ticket intake to pull request creation include strict reliance on pre-flight checks and user prompt gating for safe execution. It requires GitHub integration and available plan files for optimal phase orchestration.