executing-plans

Execute implementation plans with checkpointed tasks and verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps turn a written implementation plan into completed work by reviewing the plan first, spotting gaps, and executing tasks in a controlled sequence.

Core Features & Use Cases

  • Plan Review: Critically checks dependencies, validation criteria, and environment assumptions before work begins.
  • Task Execution: Drives each task through implementation, verification, and progress tracking with clear checkpoints.
  • Failure Handling: Stops on blockers, ambiguities, or repeated test failures and escalates them instead of guessing.
  • Use Case: Use it when a project has a documented roadmap, a branch of work, and a need for disciplined step-by-step delivery.

Quick Start

Use the executing-plans skill to read the plan, review it critically, and carry out each task with validation checkpoints.

Frequently Asked Questions about executing-plans

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

FAQPage Schema
How do I execute a software implementation plan with task checkpoints and validation?▼

Executing a software implementation plan with checkpoints requires reviewing dependencies first, then driving each task through implementation, verification, and progress tracking using TodoWrite to ensure controlled step-by-step delivery.

What is the best way to track multi-step development branch tasks with progress control?▼

Tracking multi-step development branch tasks requires per-task validation, clear acceptance criteria, and TodoWrite progress tracking, stopping to escalate blockers or ambiguities instead of guessing when failures occur.

How do I review a project roadmap for gaps before starting development work?▼

Reviewing a project roadmap for gaps involves critically checking dependencies, validation criteria, and environment assumptions before work begins, ensuring the documented plan has clear acceptance criteria for each task.

Can I use plan execution workflows for multi-step software work with dependency checking?▼

Plan execution workflows suit multi-step software work requiring dependency checking, branching discipline, and task-by-task progress control, applying to projects with documented roadmaps and disciplined step-by-step delivery needs.

Why does plan execution stop on repeated test failures or ambiguous requirements?▼

Plan execution stops on repeated test failures or ambiguities to escalate blockers rather than guessing, ensuring critical plan review and per-task validation maintain quality throughout the development branch workflow.

Do I need documented acceptance criteria to use task-by-task plan execution?▼

Task-by-task plan execution requires clear acceptance criteria, a documented roadmap, and a development branch, applying dependency checking and branching discipline to ensure controlled delivery of multi-step software work.