implement

Name: implement
Availability: InStock
Author: donygeorge

Execute multi-milestone implementation plans with per-milestone QA and codex review.

2|Updated Feb 16, 2026

Search Tags:#automation #git #planning #qa #orchestration #milestones #code-review

Ready to run

npx skills add https://github.com/donygeorge/claude-toolkit --skill implement-donygeorge

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Long-running implementation plans often stall without a structured, auditable execution framework. This Skill coordinates plan execution with milestone orchestration, enabling safe, resumable work over hours and days.

Core Features & Use Cases

Two-tier orchestration: a Plan Executor and fresh Milestone Orchestrators ensure context isolation and long-running sessions.
Strict guardrails: per-milestone QA, codex reviews, and one commit per milestone to support traceability and rollback.
Resume and recovery: state files enable crash-safe restarts and resumed progress across milestones.
Clear exit criteria and documentation updates required per milestone.

Quick Start

Supply an approved plan file to start orchestrating milestones end-to-end with per-milestone QA, codex review, and one commit per milestone.

Frequently Asked Questions about implement

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

FAQPage Schema

How do I execute long-running implementation plans without losing progress?▼

You can execute long-running implementation plans safely by using milestone orchestration with state files, enabling crash-safe restarts and resumed progress across milestones over hours or days without losing completed work.

What is the best way to ensure one commit per milestone during plan execution?▼

The best way to enforce one commit per milestone is using a two-tier plan executor with strict guardrails, applying per-milestone QA, codex reviews, and versioning to support full traceability and safe rollback.

How do I orchestrate multi-milestone work with strict guardrails and code reviews?▼

You orchestrate multi-milestone work by coordinating a Plan Executor with fresh Milestone Orchestrators that ensure context isolation, applying strict guardrails including per-milestone QA, codex reviews, and clear exit criteria.

Do I need an approved plan file to start milestone orchestration?▼

Yes, you need to supply an approved plan file to start orchestrating milestones end-to-end, which triggers the guided execution workflow applying per-milestone QA, codex review, and one commit per milestone.

Why does multi-milestone implementation work require two-tier orchestration?▼

Multi-milestone implementation work requires two-tier orchestration because a Plan Executor and fresh Milestone Orchestrators ensure context isolation, preventing session bloat and enabling safe, resumable work over long periods.

Can I resume plan execution if a milestone fails QA or codex review?▼

Yes, you can resume plan execution after a milestone fails QA or codex review because state files enable crash-safe restarts, allowing you to address issues and resume progress across milestones without restarting the entire plan.