skills.rest
cpp-for-everything
cpp-for-everythingOFFICIAL
Explore all skills by this author →
GitHub

executing-plans

Execute written plans sequentially with review checkpoints and blocker escalation.

1|Updated Mar 8, 2024
Search Tags:#workflow#planning#verification#subagents#review#plan-execution#development-branch
One-click install
npx skills add https://github.com/cpp-for-everything/ORM --skill executing-plans-cpp-for-everything
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/cpp-for-everything/ORM/tree/main/.windsurf/skills/executing-plans
Command: npx skills add https://github.com/cpp-for-everything/ORM --skill executing-plans-cpp-for-everything

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to executing a written plan in a controlled session, ensuring deliberate review and checkpointed task progress.

Core Features & Use Cases

  • Load a plan, review it critically, and decide whether to proceed.
  • Execute tasks in a defined sequence with per-task status tracking and verifications.
  • Integrate with related subskills (such as finishing a development branch) to complete work and report outcomes.
  • Stop or escalate when blockers are encountered to avoid undefined states or drift.

Quick Start

Load the plan file, review it for questions, and begin executing tasks exactly as written.

Frequently Asked Questions about executing-plans

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

FAQPage Schema
What is review-driven plan execution for development tasks?▼

Plan execution handles blockers by stopping or escalating them immediately, preventing undefined states or drift. This ensures the review-driven workflow pauses task progress until the blocking issue is resolved.

How do I execute a written development plan step by step?▼

Git worktrees provide an isolated development branch for plan execution, allowing sequential task completion and verifications without impacting the main branch until the finishing subskill integrates the work.

How does this workflow handle blockers during task execution?▼

Plan execution handles blockers by stopping or escalating them immediately, preventing undefined states or drift. This ensures the review-driven workflow pauses task progress until the blocking issue is resolved.

Do I need a written plan file before starting development branch execution?▼

Yes, a written plan file is required to begin. The workflow loads the plan document, reviews it critically to decide whether to proceed, and uses it as the source of truth for sequential task execution and verification.

When should I use a structured plan execution workflow instead of direct coding?▼

Use structured plan execution for development tasks requiring sequential execution, critical review checkpoints, and per-task status tracking to prevent drift, rather than ad-hoc coding without defined verification steps.

Related Skills

Explore More Software Engineering Skills→
atxinskyatxinsky
4

executing-plans

Execute plan files in sequential batches with per-batch verification and human feedback between runs.

Community
Basic
otrebuotrebu
4

finish-feature

Merge a feature branch into main with conflict handling and push.

Community
Basic
SungmasterSungmaster

executing-plans

Execute multi-step development plans with iterative task management and verification checkpoints.

Community
Advanced
greglambgreglamb
1

executing-plans

Execute written implementation plans with structured review, task tracking, and verification.

Community
Intermediate