executing-plans

Executes written implementation plans task-by-task with review checkpoints and per-task commits.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/marcocpt/trae_skills --skill executing-plans-marcocpt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/marcocpt/trae_skills/tree/main/executing-plans
Command: npx skills add https://github.com/marcocpt/trae_skills --skill executing-plans-marcocpt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written implementation plan into working code often goes wrong: steps get skipped, vague verification criteria slip through, and errors compound silently. This Skill enforces a disciplined execution loop—critically review the plan, execute each task with verification, commit per task, and stop to ask when blocked. ## Core Features & Use Cases - Critical Plan Review: Checks for missing dependencies between steps, vague verification conditions, and unstated environment assumptions before writing any code. - Structured Task Execution: Tracks progress with a todo list, runs the required tests for each task, and commits changes individually with task-referenced commit messages. - Exception Handling: Distinguishes implementation bugs from broken tests or flawed plans, and stops to consult the user instead of guessing when instructions are unclear. - Use Case: You have a 5-task plan in docs/plan.md for adding user validation to an API. The Skill reviews the plan, flags an ambiguous verification step, then implements, tests, and commits each task in sequence, ending with a full execution report. ## Quick Start Ask the AI to execute the implementation plan in docs/plan.md using the executing-plans skill, reviewing it first and committing after each task.

Frequently Asked Questions about executing-plans

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

FAQPage Schema
How do I execute an implementation plan with an AI coding assistant?

Load the plan file, have the assistant critically review it for dependency ordering and clear verification criteria, then execute tasks one by one. Each task should be tested, committed separately with a task-referenced message, and marked complete before moving on.

What should I check before executing a written development plan?

Check for missing dependencies between steps, vague verification conditions like "confirm it works", and unstated environment assumptions such as runtime versions or API keys. Raise any concerns with your collaborator before starting implementation.

What should I do when tests fail during plan execution?

Read the error to determine whether it is an implementation bug, a broken test, or a flawed plan. Fix implementation bugs and rerun; fix broken tests and inform your collaborator; stop and report if the plan itself is wrong.

When should plan execution stop instead of continuing?

Stop immediately when blocked by missing dependencies, repeatedly failing tests, or unclear instructions. Do not guess intent or push through blockers—list your understanding and wait for clarification before continuing.

Should each task in a plan be committed separately?

Yes. Commit after each completed task with a message referencing the task number, such as "feat: add user input validation (task 2/5)". This creates a clean history and makes it easy to trace or revert individual changes.