Skills executing-plans
📋

executing-plans

Safe 🌐 Network access

Execute Development Plans with Checkpoints

Also available from: Cycleaddict,davila7,Cygnusfear,DYAI2025,DMJGilbert,Doyajin174,CodingCossack

Complex multi-step implementations are challenging to manage safely. This skill breaks development plans into manageable batches with review checkpoints, ensuring quality and catching issues early.

Supports: Claude Codex Code(CC)
📊 70 Adequate
1

Download the skill ZIP

2

Upload in Claude

Go to Settings → Capabilities → Skills → Upload skill

3

Toggle on and start using

Test it

Using "executing-plans". Execute the plan in 'user-dashboard-plan.md'

Expected outcome:

  • Loaded plan with 12 tasks total
  • First batch: Completed tasks 1-3 (database schema, API endpoints, tests)
  • Verification: All tests passing, schema migration successful
  • Ready for feedback before continuing

Using "executing-plans". Review and execute 'payment-integration-plan.md'

Expected outcome:

  • Plan review: Found unclear error handling in step 7
  • Clarified with team: Use custom exceptions for payment failures
  • Executing batch 1: Payment gateway setup and configuration
  • Completed with verification: Gateway connection test passed

Security Audit

Safe
v5 • 1/17/2026

Evaluated all 10 static findings. All are false positives. The skill is pure documentation containing implementation guidelines. Hardcoded URL is legitimate GitHub source metadata. SHA256 hash is content integrity verification. C2 keywords and weak crypto flags are pattern matching errors on documentation text like 'execute', 'critically', and 'hash' field names. No executable code, network operations, or cryptographic code exists.

2
Files scanned
263
Lines analyzed
1
findings
5
Total audits

Risk Factors

🌐 Network access (1)
Audited by: claude View Audit History →

Quality Score

38
Architecture
100
Maintainability
87
Content
22
Community
100
Security
91
Spec Compliance

What You Can Build

Implement Complex Features Safely

Break down large features into planned steps with quality checkpoints between implementation batches.

Standardize Implementation Process

Ensure consistent execution of technical plans with built-in review cycles and verification steps.

Learn Structured Development

Follow proven patterns for implementing complex tasks with proper verification and feedback loops.

Try These Prompts

Basic Plan Execution
I have a plan file called 'feature-plan.md'. Please use the executing-plans skill to implement it step by step.
Large Feature Implementation
Execute the plan in 'auth-system-plan.md' but be extra careful with the database migration steps. Check with me after each batch.
Team Collaboration
Review and execute the plan in 'api-redesign.md'. I wrote it based on our architecture discussion - flag any issues you see.
Custom Batch Size
Load the plan from 'microservice-plan.md' and execute only 2 tasks per batch. This is critical infrastructure, so go slow.

Best Practices

  • Always review the entire plan critically before starting execution
  • Stop immediately when hitting blockers rather than making assumptions
  • Run all verification steps exactly as specified in the plan

Avoid

  • Do not skip the initial plan review step - critical issues may be missed
  • Never guess or improvise when instructions are unclear - always ask
  • Do not proceed to next batch without explicit feedback or approval

Frequently Asked Questions

What happens if I hit a blocker during execution?
Stop immediately and ask for clarification. Do not guess or work around the issue.
Can I change the batch size?
Yes, the default is 3 tasks but you can specify any number based on complexity and risk.
Do I need to use TodoWrite?
Yes, the skill automatically creates and manages tasks using TodoWrite for proper tracking.
What if the plan has fundamental flaws?
Raise concerns during the initial review step before any execution begins.
How do I handle verification failures?
Stop the batch, report the failure, and wait for guidance before proceeding.
Can I execute plans out of order?
No, follow the plan sequence exactly as written to maintain dependencies.

Developer Details

File structure

📄 SKILL.md