executing-plans

Execute development plans in controlled batches with code-review gates.

3|Updated Nov 19, 2025

Search Tags:#automation #workflow #development #project management #code review #execution #plans

Ready to run

npx skills add https://github.com/seanGSISG/crispy-claude --skill executing-plans-seangsisg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/seanGSISG/crispy-claude/tree/main/.claude/skills/executing-plans
Command: npx skills add https://github.com/seanGSISG/crispy-claude --skill executing-plans-seangsisg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementing complex development plans can be error-prone and difficult to track, especially without clear checkpoints. This skill provides a structured approach to execute plans in controlled batches with mandatory review gates.

Core Features & Use Cases

Batch Execution: Executes implementation tasks in small, manageable batches (default 3 tasks), with a code review after each batch.
Parallelization Detection: Automatically detects if a plan is decomposed into a manifest, enabling parallel execution for faster completion.
Critical Review Gates: Enforces stopping and asking for help when blockers are encountered, preventing guessing and rework.

Quick Start

Use the executing-plans skill to implement the 'user-profile-management' plan from 'docs/plans/2025-01-18-user-profile-management.md'.

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 development plan with review checkpoints?▼

Executing plans with review checkpoints involves breaking implementation into controlled batches with mandatory code reviews after each batch. This skill executes tasks sequentially or in parallel—depending on whether a manifest.json exists—and stops for review gates between batches to catch blockers early and prevent rework.

Can I run development tasks in parallel during plan execution?▼

Parallel execution is automatically enabled when your plan includes a manifest.json file decomposing tasks into parallel-executable units. Plans without a manifest execute sequentially. This parallelization detection lets you accelerate completion on complex multi-task plans without manual coordination overhead.

What's the best way to track task progress and status through a large implementation plan?▼

Batch execution with per-task status tracking provides visibility into progress. Each task is logged and verified individually, with code review gates inserted after every batch. This structure prevents silent failures and ensures blockers surface immediately rather than compounding through later stages.

How do I prevent errors and rework when executing complex development plans?▼

Critical review gates enforce stopping to ask for help when blockers are encountered, eliminating guessing that causes rework. Combining batch execution, per-task verification, and mandatory code reviews creates checkpoints that catch issues before they propagate downstream.

Do I need a manifest file to execute my development plan?▼

A manifest.json is optional. Plans with 4+ tasks benefit from manifest-driven parallel execution for speed, but simple 1–3 task plans execute successfully without one, running sequentially instead. The skill adapts its execution strategy to your plan's structure.

What happens after a development plan finishes executing?▼

Plan execution concludes with a completion announcement and requires finishing-a-development-branch as the final step, ensuring your implementation branch is properly closed out and integrated into your workflow.