execute

Implements an approved plan and verifies the result against its contracts and repo standards.

Updated May 13, 2026
One-click install
npx skills add https://github.com/andrewcodesit/skills --skill execute-andrewcodesit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: execute
Source: https://github.com/andrewcodesit/skills/tree/main/skills/engineering/execute
Command: npx skills add https://github.com/andrewcodesit/skills --skill execute-andrewcodesit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Plans get written and then quietly ignored during implementation, and green tests do not prove the plan's contracts survived. This Skill runs an approved plan end to end, then verifies the code against the plan's spec, repo standards, and named contracts so drift gets caught instead of shipped. ## Core Features & Use Cases - Wave-based execution: Groups plan tasks into parallel or sequential waves, assigns each a capability tier (routine, standard, deep), and delegates to subagents with scoped briefing packs. - Plan verification: Checks spec compliance, repo standards from AGENTS.md and CLAUDE.md, and every contract and failure mode the plan named, reading the actual code rather than trusting subagent reports. - Structured reporting: Produces verification findings with a resolution gate, marks the plan file as EXECUTED, and offers follow-ups like code-review, cleanup, or publishing a draft branch. - Use Case: After approving an implementation plan, tell the agent to execute it; it dispatches the tasks, verifies the result against the plan, and reports any gaps before you commit. ## Quick Start Approve the plan I just showed you and execute it, verifying the implementation against the plan when finished.

Frequently Asked Questions about execute

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

FAQPage Schema
How do I execute an approved implementation plan with an AI agent?▼

Invoke the execute skill after approving a plan in a prior turn. It loads the latest plan from the plans directory, groups tasks into waves, delegates or runs them inline, then verifies the code against the plan before reporting completion.

How does the execute skill verify code against a plan?▼

It reads every changed file and checks three things: spec compliance with the plan's requirements, repo standards from AGENTS.md and CLAUDE.md, and each contract or failure mode the plan explicitly named. It never trusts subagent DONE reports as proof.

Can the execute skill run tasks in parallel with subagents?▼

Yes, when the environment supports delegation. Tasks are grouped into waves based on file ownership and dependencies, each assigned a capability tier, and independent tasks in a wave are dispatched concurrently with scoped briefing packs.

When should I not run the execute skill?▼

Do not run it before the user has seen and approved the plan in a later turn; a plan file on disk is not authorization. It also deliberately skips design-level code review, which is left to a separate independent review pass.

What happens when verification finds gaps in the implementation?▼

The skill reports findings grouped as spec gaps, standards violations, and broken contracts, then offers a resolution gate. Architectural or multi-file findings are routed back through the planning skill rather than patched inline.