Agent skill · operations · sickn33
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Why this skill is useful
Codifies a structured approach to executing implementation plans with checkpoints, reducing ambiguity for the AI.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Executing Plans Overview Load plan, review critically, execute tasks in batches, report for review between batches. Core principle: Batch execution with checkpoints for architect review. Announce at start: "I'm using the executing-plans skill to implement this plan." The Process Step 1: Load and Review Plan 1. Read plan file 2. Review critically - identify any questions or concerns about the plan 3. If concerns: Raise them with your human partner before starting 4. If no concerns: use the project’s existing task/todo mechanism and proceed; TodoWrite is a host-specific tool, not a universally installed command Step 2: Execute Batch Batch size follows the user’s explicit instruction or project contract; otherwise choose a practical reviewable group For each task: 1. Mark as inprogress 2. Follow each step exactly (plan has bite-sized steps) 3. Run verifications as specified 4. Mark as completed Step 3: Report When batch complete: Show what was implemented Show verification output Continue to the next authorized batch unless the user explicitly requested a checkpoint; provide concise progress without ending the task unnecessarily. Step 4: Continue Based on feedback: Apply changes if needed Execute next batch Repeat until complete Step 5: Complete Development After all tasks complete and verified: Announce: "I'm using the finishing-a-development-branch skill to complete this work." Use the actually available finishing-a-development-branch skill only when appropriate; repository-specific maintainer/merge workflows take precedence. Do not invent a superpowers plugin dependency. Follow that skill to verify tests, present options, execute choice When to Stop and Ask for Help Pause only the dependent step when an indispensable input/authorization or unresolved external blocker prevents it; preserve independent work. Repair ordinary failures autonomously. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/executing-plans--6ea54d