executing-plans

Name: executing-plans
Availability: InStock
Author: ClyptAI

Execute written implementation plans with review checkpoints in separate sessions.

Updated Mar 8, 2026

Search Tags:#development #verification #plan #workflows #git-worktrees #execute

Ready to run

npx skills add https://github.com/ClyptAI/Clypt-Backend --skill executing-plans-clyptai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/ClyptAI/Clypt-Backend/tree/main/.agents/skills/superpowers/skills/executing-plans
Command: npx skills add https://github.com/ClyptAI/Clypt-Backend --skill executing-plans-clyptai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages the execution of a written implementation plan by running in a separate session with review checkpoints, ensuring critical evaluation before action.

Core Features & Use Cases

Load plan, review critically, create a TodoWrite, and proceed
Execute each task with in_progress status, follow plan steps exactly, and perform verifications
Complete development by triggering appropriate sub-skills (such as finishing-a-development-branch) and presenting options after verification

Quick Start

Load the plan file, review it critically, and start executing all tasks.

Frequently Asked Questions about executing-plans

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

FAQPage Schema

How do I execute an implementation plan with review checkpoints during development?▼

To execute an implementation plan with review checkpoints, load your plan file into a separate session and critically review it before proceeding through each task. The system creates a TodoWrite list, executes steps exactly as defined, and performs verifications at each gated development phase.

What is plan-driven development execution in an isolated workspace?▼

Plan-driven development execution in an isolated workspace runs written implementation tasks in a separate session using git-worktrees. This ensures critical evaluation happens before action, applying gating conditions across development phases while keeping the main branch protected.

Do I need a written plan file to start executing development tasks?▼

Yes, you need a written plan file to start executing development tasks. The execution requires a plan file containing defined steps, verifications, and gating conditions, along with an isolated workspace setup using git-worktrees to separate the work.

How do I verify tasks when executing a development plan?▼

You verify tasks when executing a development plan by following the plan steps exactly and performing the verifications defined within the plan file. Each task is tracked with in_progress status, ensuring verifications are met before moving to the next development phase.

What happens after completing all tasks in an implementation plan?▼

After completing all tasks and verifications in an implementation plan, the system triggers sub-skills like finishing-a-development-branch to complete the development process. It then presents options for finalizing the work in your isolated workspace.

Can I use git-worktrees to isolate plan execution from my main branch?▼

Yes, you can use git-worktrees to isolate plan execution from your main branch. The execution requires an isolated workspace, integrating with the using-git-worktrees sub-skill to ensure plan-driven development tasks with gating conditions run separately.