ac-execute

Execute approved codebase changes with minimal verification checks.

6|2|Updated Jan 9, 2026

Search Tags:#verification #safety #review #plan #lint #execute #code-delivery

Ready to run

npx skills add https://github.com/yz0812/ai-dev-toolkit --skill ac-execute

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ac-execute
Source: https://github.com/yz0812/ai-dev-toolkit/tree/main/skills/ac-execute
Command: npx skills add https://github.com/yz0812/ai-dev-toolkit --skill ac-execute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ac-execute ensures changes are implemented strictly according to an approved plan and completed with minimal verification overhead, enabling reliable delivery.

Core Features & Use Cases

Plan-driven execution: apply only approved changes to the targeted codebase.
Minimal verification: run lightweight checks to validate changes before delivery.
Safe orchestration: if plan details are missing, prompt for confirmation before proceeding.

Quick Start

Apply the latest approved plan to the repository and run the minimal verification workflow.

Frequently Asked Questions about ac-execute

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

FAQPage Schema

How do I execute approved changes on a codebase with minimal verification?▼

Plan-driven execution applies only approved changes to the target codebase, utilizing lightweight lint and type checks to verify changes before delivery for reliable code implementation.

What is plan-driven development execution for code delivery?▼

Plan-driven development execution for code delivery is a process that applies approved changes across modules strictly following a plan, performing minimal verification to ensure reliable implementation.

How do I apply an approved plan to a repository and run verification checks?▼

Apply the latest approved plan to the target repository to execute changes, then run lightweight lint and type checks to validate the modifications prior to delivery.

Do I need an approved plan before executing code changes across modules?▼

Yes, an approved plan is required before executing code changes. If plan details are missing, the safe orchestration mechanism prompts for confirmation before proceeding with the implementation.

What's the best way to verify code changes before delivery in plan-driven development?▼

The best way to verify code changes before delivery is by running lightweight lint and type checks, optionally utilizing read-only subagent reviews to validate modifications applied from the approved plan.

What happens if plan details are missing during code execution?▼

If plan details are missing during code execution, the safe orchestration feature pauses and prompts for confirmation before proceeding, ensuring changes are not applied without explicit approval.