executing-plans

Execute written implementation plans with task tracking and review checkpoints.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/lapaixkemsdortshlee-svg/AyitiMarket --skill executing-plans-lapaixkemsdortshlee-svg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/lapaixkemsdortshlee-svg/AyitiMarket/tree/main/.claude/skills/executing-plans
Command: npx skills add https://github.com/lapaixkemsdortshlee-svg/AyitiMarket --skill executing-plans-lapaixkemsdortshlee-svg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you carry out a written implementation plan without losing track of steps, checks, or completion criteria, so planned work gets executed consistently in a separate session.

Core Features & Use Cases

  • Plan Review First: Reads the plan critically before starting and raises concerns when instructions are unclear or incomplete.
  • Stepwise Execution: Breaks the work into tracked tasks, follows each step in order, and verifies each result before moving on.
  • Blocker Handling: Stops and asks for clarification when dependencies are missing, tests fail repeatedly, or the plan has gaps.
  • Use Case: A teammate gives you a development plan for a feature branch, and you use this Skill to execute the tasks, verify the outcome, and report when the work is complete.

Quick Start

Use the executing-plans skill to review this implementation plan, execute each task with checkpoints, and report back when the work is complete.

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 written software implementation plan without losing track of steps?

To execute an implementation plan safely, the work is broken into tracked tasks that follow each step sequentially, verifying results at structured checkpoints before moving on to ensure consistent software delivery.

What happens if a development plan has unclear instructions or missing dependencies?

When a plan has unclear instructions or missing dependencies, execution stops and raises concerns. Blocker handling triggers clarification requests when tests fail repeatedly or gaps are detected during plan review.

Can I use task tracking for multi-step feature development in an isolated workflow?

Yes, task tracking applies to isolated development workflows and multi-step implementation tasks. Sequential execution with verification checkpoints ensures planned feature work gets completed consistently in separate sessions.

When do I need critical plan review before starting software delivery?

Critical plan review is needed before starting software delivery when executing written implementation plans. Reading the plan first raises concerns about incomplete instructions, ensuring task tracking and verification proceed without blockers.

How does stepwise execution verify task completion for planned work?

Stepwise execution verifies task completion by following each step in order and checking the result before advancing. Completion handoff provides clear reporting once all tracked tasks and checkpoints pass verification.