plan-execute

Generate explicit YAML plans for complex code changes with approval gates.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/doctorduke/seashells --skill plan-execute
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-execute
Source: https://github.com/doctorduke/seashells/tree/main/.claude/skills/plan-execute
Command: npx skills add https://github.com/doctorduke/seashells --skill plan-execute

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes templates (resource) components.

What problem does it solve?

This Skill eliminates the high risk and potential for costly mistakes associated with complex code changes by enforcing a structured, two-phase planning and execution workflow. It provides explicit approval gates and rollback capabilities, ensuring safe and auditable refactoring.

Core Features & Use Cases

  • Explicit YAML Plans: Generates a detailed, human-reviewable YAML plan outlining all steps, dependencies, and risks before any code is touched.
  • Approval Gates & Checkpointing: Requires user confirmation for high-risk steps and creates Git checkpoints, allowing for instant rollback if issues arise.
  • 90% First-Pass Success: Achieves a significantly higher success rate for complex tasks compared to ad-hoc changes, reducing debugging time.
  • Use Case: Refactor a critical authentication module to use JWT, involving multiple file changes and potential breaking points. The skill will generate a plan, ask for approval at each sensitive step, and create checkpoints, ensuring a safe and auditable transition.

Quick Start

User initiates a complex refactoring task

User: Use Plan-Execute: Refactor authentication to use JWT instead of sessions

Agent generates a detailed YAML plan for review

(User reviews and approves)

Agent executes step-by-step with checkpoints and approvals

Agent: ✓ Step 1 (analyze): Found 8 files using sessions Agent: → Step 3 (refactor-login): APPROVAL REQUIRED Agent: Will modify: src/routes/auth/login.js (critical auth logic) Agent: Proceed? (y/n/skip)

Frequently Asked Questions about plan-execute

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

FAQPage Schema
How do I safely plan and execute complex code changes with git?

Plan-execute generates a detailed YAML plan before making changes, requiring approval at each step and creating git checkpoints for instant rollback. This two-phase workflow prevents bugs in multi-file refactors, migrations, and API changes by enforcing review gates and maintaining an audit trail.

What's the best way to refactor code across multiple files without breaking things?

Plan-execute maps all dependencies and risks upfront, checkpointing your git state before each modification. You approve high-risk steps individually, catching issues early and rolling back safely if needed—achieving 90% first-pass success on complex refactors.

Can I use plan-execute for authentication module changes or API migrations?

Yes. Plan-execute handles authentication refactors, API changes, and any scenario with breaking points across files. It identifies affected code, sequences changes safely, and gates approval on critical steps like modifying auth logic or breaking endpoints.

Do I need git to use the planning and execution workflow?

Yes, git is required. Plan-execute creates checkpoints by committing to git at each phase, enabling rollback and maintaining an audit trail of all changes during execution.

How does plan-execute reduce debugging time on refactoring tasks?

By generating and reviewing explicit plans before execution, catching dependency issues and breaking points upfront, and checkpointing with git at each step, plan-execute prevents most mistakes before they occur—cutting debugging cycles significantly.

What happens if a code change fails during execution?

Plan-execute creates git checkpoints before each high-risk step, so you can instantly rollback to a known good state. The audit trail shows exactly which step failed and what was attempted, aiding diagnosis.