executing-plans

Execute written implementation plans with stepwise task verification and blocker escalation.

2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/LisztVan/subcli-cpp --skill executing-plans-lisztvan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/LisztVan/subcli-cpp/tree/main/.pi/skills/superpowers/skills/executing-plans
Command: npx skills add https://github.com/LisztVan/subcli-cpp --skill executing-plans-lisztvan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps an AI safely execute a written implementation plan by reviewing it first, following it step by step, and stopping when a blocker or ambiguity appears.

Core Features & Use Cases

  • Critical plan review: Checks a plan for gaps, risks, missing dependencies, and unclear instructions before work begins.
  • Stepwise execution with checkpoints: Carries out each task in order, verifies progress after every step, and keeps work aligned with the plan.
  • Blocker handling and handoff: Stops and asks for clarification when instructions fail, then completes final verification and branch-finishing workflow when the work is done.

Quick Start

Provide the plan you want executed and ask the AI to review it critically, carry out each task in order, verify the results, and report 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 implementation plan step by step?

To execute an implementation plan step by step, the AI reviews it critically for risks, carries out each task sequentially, verifies progress after every step, and stops to escalate when blockers or ambiguity appear.

What is the best way to handle blockers during task execution?

Handling blockers during task execution requires stopping the workflow immediately and asking for clarification when instructions fail, ensuring work resumes only after resolving the ambiguity or missing dependency.

How do I verify progress after each step of a software delivery plan?

Verifying progress after each step of a software delivery plan involves applying review checkpoints that confirm task completion and alignment with the plan before proceeding to the next task.

Can I use this workflow across separate work sessions?

Yes, this workflow supports software delivery across separate work sessions by applying structured task tracking and progress reporting to maintain continuity between execution intervals.

What should a plan include before starting stepwise task execution?

Before starting stepwise task execution, a plan should include clear dependencies, risk assessments, and unambiguous instructions, as critical plan review checks for gaps and missing elements before work begins.

When should I escalate a blocker during implementation plan execution?

You should escalate a blocker during implementation plan execution when instructions fail or ambiguity prevents progress, stopping work immediately to request clarification and avoid deviating from the plan.