implement

Execute approved development plan phases with Codex-reviewed corrections and verification.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/KMakayee/playbook --skill implement-kmakayee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/KMakayee/playbook/tree/main/.claude/skills/implement
Command: npx skills add https://github.com/KMakayee/playbook --skill implement-kmakayee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents slow, error-prone implementation by enforcing phase-by-phase execution, post-phase verification, and Codex-assisted correction aligned to the approved plan.

Core Features & Use Cases

  • Phase-driven implementation: Executes the changes specified in tasks/plan.md while reading all relevant files before editing.
  • Mismatch handling with safety gates: Detects structural mismatches, triggers targeted re-research, and stops when the plan premise is invalidated or when recovery attempts exceed limits.
  • Independent Codex code review and triaged fixes: Runs a Codex review, triages findings into fixes vs developer flags, applies fixes via a child process, and performs a final test/lint verification.
  • Commit-per-phase traceability: Creates separate commits for each phase to keep reviews and rollbacks manageable.

Quick Start

Use the implement skill when you already have tasks/plan.md and tasks/research-codebase.md prepared, so it can execute the approved phases, run Codex review, apply fixes, and leave the repo in a verified state.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I execute a development plan phase-by-phase with automated verification?

Phase-by-phase implementation reads your approved plan, applies specified changes sequentially, runs Codex review, and applies triaged fixes to meet success criteria. It ensures strict adherence to the plan and performs final automated verification.

What is the best way to handle structural mismatches found during plan implementation?

Handling structural mismatches during implementation triggers targeted re-research and stops execution when the plan premise is invalidated or recovery attempts exceed limits. This safety gate prevents error-prone implementation.

How do I generate git commits for each phase of a software engineering implementation workflow?

Commit-per-phase traceability creates separate git commits with conventional messages for each phase of your implementation workflow. This keeps code reviews and rollbacks manageable throughout the development plan execution.

Can I use Codex review to apply automated fixes during plan implementation?

Codex review runs in a read-only sandbox to evaluate your implementation, triages findings into fixes versus developer flags, and applies fixes via a child process. It then performs final test and lint verification.

Do I need tasks/plan.md prepared before starting phase-based implementation?

You need tasks/plan.md and tasks/research-codebase.md prepared before starting. The implementation skill executes approved phases, runs Codex review, applies fixes, and leaves the repository in a verified state.

Why does phase-based implementation stop when plan premise is invalidated?

Phase-based implementation stops when the plan premise is invalidated to prevent slow, error-prone implementation. This safety mechanism enforces strict adherence to the approved plan and triggers structural-mismatch re-research.