Verified:GitHub

implement

Execute approved implementation plans phase by phase with validation checkpoints.

Updated Aug 23, 2026

Search Tags:#workflow #validation #implementation #human-in-the-loop #software-engineering #plan-execution #phase-tracking

Ready to run

npx skills add https://github.com/ncy08/clear-claude-code --skill implement-ncy08

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating the end-to-end execution of approved implementation plans across software and business domains, ensuring changes are made in dependency order with validation checkpoints and explicit human verification between phases.

Core Features & Use Cases

Phase-by-phase plan execution: reads an approved plan and enacts file changes in dependency order with validation.
Supports both software engineering plans (create/modify files with validation) and business execution plans (document creation, Drive operations, meetings).
Progress tracking with checkboxes and pauses for human verification between phases.
Explicit user invocation required to trigger actions.

Quick Start

Provide an approved plan path (e.g., thoughts/shared/plans/plan.md) to start, and I will execute it phase by phase.

Frequently Asked Questions about implement

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

FAQPage Schema

How do I execute an approved software implementation plan phase by phase?▼

Executing an approved software implementation plan phase by phase requires providing a plan file path, which the system reads to order file changes by dependency and perform gated validations between phases.

What is human-in-the-loop validation during plan execution?▼

Human-in-the-loop validation during plan execution pauses stepwise progress after each phase, requiring explicit user invocation and verification before triggering the next set of actions.

Can I use plan execution for business tasks like document creation and Drive operations?▼

Plan execution supports business execution plans including document creation and Drive operations, coordinating dependencies and checkpoints to ensure stepwise execution across non-software domains.

How do I start phase tracking with an approved plan?▼

Starting phase tracking requires providing an approved plan path like thoughts/shared/plans/plan.md, which triggers the system to begin reading steps and enforcing stepwise execution with progress tracking.

Does plan execution support progress tracking with checkboxes?▼

Plan execution provides progress tracking with checkboxes to mark completed phases, pausing between phases for human verification and explicit user invocation before triggering subsequent actions.

What are the limitations of stepwise execution for plan implementation?▼

A key limitation of stepwise execution is the requirement for explicit user invocation to trigger actions, pausing phase tracking and dependency ordering until human verification is provided at each gated validation checkpoint.