executing-plans

Executes written implementation plans in reviewed batches with functional testing until completion.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Coral5644/NekansModPack --skill executing-plans-coral5644
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/Coral5644/NekansModPack/tree/main/.cursor/skills/executing-plans
Command: npx skills add https://github.com/Coral5644/NekansModPack --skill executing-plans-coral5644

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns a written implementation plan into verified working code by executing tasks in small batches, reviewing each batch immediately, and continuing through functional testing instead of leaving verification to the end. ## Core Features & Use Cases - Batched Execution with Checkpoints: Implements 1-3 tasks per batch, then reviews and fixes issues within that batch before moving on. - Work Mode Awareness: Distinguishes main-workspace mode from feature-workspace mode, using mcdev-tools direct testing in feature workspaces. - Failure Containment: When a batch fails, it fixes only that batch's problems and never carries failures forward; outdated plans are sent back to planning. - Use Case: You have a multi-step plan for a NetEase Minecraft mod feature. This Skill implements it batch by batch, runs Python 2.7 and code-quality reviews after each batch, then restarts the game via mcdk to verify the feature works before declaring completion. ## Quick Start Use the executing-plans skill to execute the implementation plan in docs/feature-plan.md and verify it with functional testing.

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 multi-step implementation plan with an AI assistant?▼

Load the plan file, confirm the work mode (main workspace or feature workspace), then implement 1-3 tasks per batch. After each batch, run immediate reviews and fix issues before proceeding to the next batch.

How to test Minecraft mod changes in a feature workspace?▼

Point .mcdev.json included_mod_dirs at the feature workspace, restart the game via mcdk, and run the test checklist directly against the feature workspace code. Fixes are applied in the feature workspace without any git operations.

What should I do when a batch of planned tasks fails?▼

Classify the failure as a code issue, review issue, uncertain engine behavior, or test failure, then fix only the current batch's problems. Do not advance to the next batch until the failing batch passes review.

When should plan execution stop and return to planning?▼

Stop when the plan is incomplete, conflicts with current code reality, misses critical steps, or when API existence is unverified. Return to the project-planner skill to revise the plan before resuming execution.

Does this workflow support Python 2.7 mod development?▼

Yes, it includes a pre-execution review for Python 2.7, threading, and module dependency rules, plus a python27-syntax-reviewer check after key changes in each batch.